Although eliminating the desktop icons makes a nice looking blank space, whether to leave it that way is a matter of opinion. It is also not answer the OP’s question. The way to restore the icons is to install either the the Desktop Icons or Desktop Chaos (for more sorting options) extension (or possibly another) from GNOME extensions (Many extensions provide features removed from GNOME).
@joekamprad OK, here is the link to the Wiki article I created: https://antergos.com/wiki/system-admin/package-management/antergos-wont-update-due-to-broken-signing-system-keyring-refresh-doesnt-work/
@joekamprad Today I was not blocked from editing my original post to correct the typo sudo /etc/pacman.conf to sudo nano /etc/pacman.conf (an error I corrected on the wiki entry). However, if I try to post the full wiki link, I am still blocked by Akismet.
@Keegan I quoted ghostdawg at the beginning of my post–did you mean my method? I thought fixing the signing would be better than a workaround which ignores signing, so I kept trying until I fixed it, despite all other posted methods on various forums not working. I posted it here: antergos wiki system-admin package-management antergos-wont-update-due-to-broken-signing-system-keyring-refresh-doesnt-work/ (I can’t post full link, Akismet is still blocking everything)
What worked for me editing /etc/pacman.conf with:
SigLevel = Never
Adding SigLevel = Never, in place of the original option. I forgot what it was.
To avoid using this workaround and leaving signing broken, I devised some steps below that I combined from several solutions from various forum posts, after trying many methods alone, none of which worked.
First, to understand and prevent this problem in the future, take a look at this really interesting comment from 3 months ago by ropid on reddit .com/r/archlinux/comments/6a4qh5/arch_completely_broken_due_to_missing_libssl_and/
(I had to mangle all URLs [space before top-level domain] in this post because Akismet was marking this as SPAM incorrectly)
" gathered there was a short time window where people could get hit by this because pacman’s new package and the library’s new package weren’t showing up at the exact same time. This weren’t a lot of people. Then next, there are a lot of people that run “pacman -Sy” instead of “-S” or “-Syu”. That was then the main round of people that had their system break.
People do this “-Sy” stuff because it’s occasionally getting recommended by someone, so this idea never dies. It’s getting recommended when people ask why they get an error when they try to install a package with “-S name”. The error comes from their local database being older than what’s in the repos and meanwhile the package they try to install had a newer version. The “-Sy name” fixes it because the database gets synced, and they are happy that the package gets installed."
I think I broke my signing by using pacman -Sy (as per bad advice online) when -Syu didn’t work (due to temporary problem with signing keys on upstream arch a few months ago).
Here are the usual fixes which worked for people where their system wasn’t as broken as mine (as per forum.antergos. com/topic/7300/pacman-invalid-or-corrupted-packages/5):
sudo pacman-key --init sudo pacman-key --populate archlinux antergos sudo pacman-key --refresh-keys sudo pacman -Syyu
or more drastic fixes at:
I recommend only doing the steps below if the above did not work.
These steps I gathered, as a whole, provides the most destructive method (without reinstalling as some people actually suggested), but is the only way that worked for me:
First, lower SigLevels (temporarily) as root with your favorite text editor such as nano
sudo nano /etc/pacman.conf
Change (comment out old line so you can restore them later) the two variables below to:
#SigLevel = Required DatabaseOptional SigLevel = Never #LocalFileSigLevel = Optional LocalFileSigLevel = Optional TrustAll
For each NON-essential package which still gives you a key-error during
pacman -Syu, remove it:
sudo pacman -R BROKEN-UNECESSARY-PACKAGE
(replace BROKEN-UNECESSARY-PACKAGE in the command above with something with key error but not important such as
gitkrakenin my case; keep a list for yourself for reinstalling them later after getting everything working)
For any remaining package which is more important but also gives you a key error, do not remove it, but ignore to force the update to work:
sudo pacman -Syu --ignore BROKEN-NECESSARY-PACKAGE
(replace BROKEN-NECESSARY-PACKAGE in the command above with something important with key error such as
pamacin my case)
which results in a successful system upgrade (if you removed enough packages by repeating the -R step for each package that has a key error other than your ignored one).
Stop gpg-agent and dirmngr processes as per wiki.archlinux. org/index.php/GnuPG#gpg:WARNING:server.27gpg-agent.27_is_older_than_us.28x_.3C_y.29 (since trying to do anything further will otherwise result in ‘gpg: WARNING: server ‘gpg-agent’ is older than us’–the error says to run gpgconf with --kill all option but that doesn’t resolve error):
sudo killall gpg-agent dirmngr
Now you can reinitialize pacman-key without warnings (but may be useless since we’ll recreate it below, but may as well since it may help us install other things before that):
sudo pacman-key --init
The refresh keys command is now broken, so:
sudo pacman -R antergos-keyring
Move and remake gnupg as per antergos. com/wiki/uncategorized/update-error-involving-keyrings/ (since otherwise, if you continue you’ll get dirmanager error as seen at bbs.archlinux. org/viewtopic.php?id=190380):
sudo mv /etc/pacman.d/gnupg /etc/pacman.d/gnupg.old pacman-key --init
Now as your system is at this point, you can’t populate keys yet without keyring, and can’t get keyring via pacman’s internal mechanisms without gnupg (may have something do do with RemoteFileSigLevel in pacman.conf but not sure), so to avoid this double bind, manually load the package from the URL:
sudo pacman -U http://repo.antergos.info/antergos/x86\_64/antergos-keyring-20170524-1-any.pkg.tar.xz
where 20170524-1 is latest version shown at the repo’s html page repo.antergos. info/antergos/x86_64/ (change the command above to match the actual filename of the latest version)
now you can continue:
sudo pacman-key --populate archlinux antergos pacman -Syu pacman -Syu pamac
then restore the SigLevels such as via
sudo nano /etc/pacman.confagain (uncomment the original values if you commented them as I suggested, otherwise see my comments in that step above–you can keep the lines you added as but comment those instead, in case you have a similar problem another time)
(I also restarted my system at this point just because I’m not sure of what running process may be affected)
In my case, this is the only method that works. Now pacman -Syyu works without errors the next time updates become available (even while pacman.conf has default SigLevels)–to be sure, I waited to post this until the next round of updates became available.
@kostas.mitropoulos Could you provide a link to that issue on here? I couldn’t find the issue on the forum or the github repo for antergos-packages or Cnchi. I am looking forward to a distro that is good for end users and has ZFS on root filesystem during install.