(In reply to S. B. from comment #6) > > Since downgrading gnome-keyring to the original version does *not* fix the > bug, I'm thinking it must be due to some unique combination of packages that > I have installed, or maybe I'm missing a commonly installed package that > Gnome is looking for, since this system has installation of recommended > packages disabled by default. What combination of packages do you have? These messages in your log look alarming: May 07 14:20:58 linux.suse gnome-keyring-daemon[1776]: couldn't access con trol socket: /run/user/1000/keyring/control: No such file or directory May 07 14:20:58 linux.suse gnome-session[1717]: ** Message: couldn't access cont rol socket: /run/user/1000/keyring/control: No such file or directory May 07 14:20:58 linux.suse gnome-keyring-daemon[1781]: couldn't access con trol socket: /run/user/1000/keyring/control: No such file or directory May 07 14:20:58 linux.suse gnome-session[1717]: ** Message: couldn't access cont rol socket: /run/user/1000/keyring/control: No such file or directory Do you not have the /run/user/1000/keyring/ dirs on your system? systemd installed? Could you also check if the following pkgs are all installed: i | gpg2 | GnuPG 2 | package i | gpg2-lang | Languages for package gpg2 | package i | gpgme | A Library Designed to Give Applications Easy Access to GnuPG | package i | libgpg-error0 | Library That Defines Common Error Values for All GnuPG Components | package i | libgpg-error0-32bit | Library That Defines Common Error Values for All GnuPG Components | package i | libgpgme11 | A Library Designed to give Applications easy Access to GnuPG | package Also please note that running a system without the recommended packages is uh... not recommended ;) Could you try installing the recommended and see if the bug persists? Try sudo zypper inr