Skip to content

Instantly share code, notes, and snippets.

@Tknott95
Last active May 13, 2019 07:16
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Tknott95/a1442b35ec359d49f3b716affc33501b to your computer and use it in GitHub Desktop.
Save Tknott95/a1442b35ec359d49f3b716affc33501b to your computer and use it in GitHub Desktop.
Random FIX for Errors Regarding unpopulated keyring | installing<PKG-HERE> breaks dependency <PKG-HERE> |

ARCH LINUX - POPULATING A KEYRING

FIX for errors regarding

| unpopulated keyring |

alt text

IN CLI/SHELL ENTER:

    sudo pacman -Sy archlinux-keyring
    sudo pacman-key --populate archlinux
    sudo pacman-key --refresh-keys

one error you are possibly getting

installing<PKG-HERE> breaks dependency <PKG-HERE>
ERROR MSG EXAMPLE IF KEYRING UNPOPULATED

ERROR FIX FOR:

: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: nvidia: installing nvidia-utils (390.42-1) breaks dependency 'nvidia-utils=390.25'
@Tknott95
Copy link
Author

sudo pacman -Syyuu --ignore nvidia-utils # How I upgrade sys argv[1] after ignore ignores upgrading that dependency if their new release breAKS AS DID NVIDIA HERE

@Tknott95
Copy link
Author

#!/bin/bash

Upg Ignore Shell Script || flag 1

sudo pacman -Syyuu --ignore $1

yaourt -Syyuu --ignore $1

@Tknott95
Copy link
Author

Boot time increasing over time

After using systemd-analyze a number of users have noticed that their boot time has increased significantly in comparison with what it used to be. After using systemd-analyze blame NetworkManager is being reported as taking an unusually large amount of time to start.

The problem for some users has been due to /var/log/journal becoming too large. This may have other impacts on performance, such as for systemctl status or journalctl. As such the solution is to remove every file within the folder (ideally making a backup of it somewhere, at least temporarily) and then setting a journal file size limit as described in #Journal size limit.

@Tknott95
Copy link
Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment