http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c1 --- Comment #1 from S. B. --- Here are a few other details: * I can reproduce the bug with a pristine user account. * I can reproduce the bug on SuseStudio. * Downgrading `gnome-keyring*` packages to the originally released version does ***not*** fix the bug. * The bug exists with or without 3rd party OBS and/or Packman repos enabled. It happens with just the Leap 42.1 OSS and Updates repos enabled. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c2 Atri Bhattacharya changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |badshah400@gmail.com, | |sb56637@gmail.com Flags| |needinfo?(sb56637@gmail.com | |) --- Comment #2 from Atri Bhattacharya --- I can't reproduce this on my system (Leap + Updates). Could you please attache the logs from journal after you see the problem occur: journalcl -b Thanks, -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c3 --- Comment #3 from S. B. --- Created attachment 676031 --> http://bugzilla.opensuse.org/attachment.cgi?id=676031&action=edit journalctl (fresh bootup and login with long 3 minute delay) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c5 --- Comment #5 from Atri Bhattacharya --- (In reply to S. B. from comment #4)

Thanks a lot Atri for taking a look. I attached the log.

No problem, happy to help out. From the log, it does look like gnome-keyring runs into a lot of issues at the start. I will take a look at what exactly this means.

I suspect that it's a side-effect of some specific combination of packages that I have installed, because nobody else is complaining about this major issue. If you need to see it happening, I can give you a link to my SuseStudio appliance, both before and after the bug appeared, where it is behaving the same way despite being a fresh virtualized environment. Just let me know.

Can you, in the meanwhile, tell us exactly what package updates lead you to run into this problem? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c7 --- Comment #7 from Atri Bhattacharya --- (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 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c9 --- Comment #9 from S. B. ---

Well, it says "Nothing to do", so it looks like I'm not missing any recommends.

OK, two discoveries: First of all, `zypper inr` does *not* override `solver.onlyRequires = true` in /etc/zypp/zypp.conf as I had expected. So I removed `solver.onlyRequires = true` and ran it again. This time it found a whopping 725 new packages to install, 1.3 GiB on the disk. I think I feel justified in not installing recommends. :-P The second discovery is that fixed the problem. So it is indeed due to a missing dependency that is probably listed somewhere as a soft recommend that should actually be a hard dependency. But which is it? I really don't want to add all that unnecessary bloat to my systems and my SuseStudio appliances. I'm attaching the entire list of installed recommends. Thanks for the help! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=978289 http://bugzilla.opensuse.org/show_bug.cgi?id=978289#c11 Atri Bhattacharya changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #11 from Atri Bhattacharya --- Recommended apps are not bloat. They are recommended for a reason. Once you start disabling them, you are on your own. Fwiw, that your system still worked, showed that whatever this app was, it wasn't and should not be a hard requirement. -- You are receiving this mail because: You are on the CC list for the bug.