You are not logged in.
I use Evolution as a frontend to Gmail. I set this up at work today, and it worked fine after installing gnome-keyring (which really should be flagged as a dependency), but after returning home (and by extension rebooting), I get the following message:
Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reachedIt appears at the top of the client after a few seconds of attempting to access the server.
It's Google's server, so there's no reason why it shouldn't be able to connect. Looks like it's trying to start some service and failing, but the message is cryptic to me.
Any advice?
Offline
I have the same problem since upgrading to Gnome 3.12 some hours ago. All of my five email adresses of different providers are affected, so this probably is not a server-side problem. Hopefully someone will find a solution soon.
Offline
I had the same issue, and solved by disabling auto login:
Offline
Thank you, this workaround did the trick for me too! Still hoping that some speedy patch will solve the root of the problem. But for the time being this will do.
Offline
Filed a bug in Gnome's Bugzilla: https://bugzilla.gnome.org/show_bug.cgi?id=728469
If possible, please confirm the bug.
Offline
I have a similar problem. Actually, Gnome-Keyring will not open the usual pop-up asking for my master password, in order to unlock every other password. Therefore, of course Evolution cannot access my e-mail account, it does not have access to the password of those accounts !
I notice that at every start-up, I have two differents gnome-keyring processes, and killing the oldest solve the problem.
oxayotl@Mahomet> ps aux | grep keyring
oxayotl 386 0.0 0.0 206312 3484 ? Sl 13:40 0:00 /usr/bin/gnome-keyring-daemon --daemonize
oxayotl 674 0.0 0.0 49524 2220 ? S 13:40 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secretsOf course the process numbers change a little bit each time, but it is always similar to that example. Simply typing “kill 386” (adjusting the number, of course), and then asking Evolution to try again gets me the pop-up for the master password, and then everything works fine. No new gnome-keyring process are launched.
Offline
Interesting; thank you for your input. So the problem obviously isn't with Evolution. I will add this information to the filed bug.
Last edited by Sir Sure E. Nuff (2014-04-18 08:06:05)
Offline
Apparently, the second gnome-keyring (the one that would work if the first one was not launched) is launched by the dbus “secret” interface :
oxayotl@Mahomet> cat /usr/share/dbus-1/services/org.freedesktop.secrets.service ~
[D-BUS Service]
Name=org.freedesktop.secrets
Exec=/usr/bin/gnome-keyring-daemon --start --foreground --components=secretsNow, I need to find out what starts the first one !
Offline
For reference, when booting without autologin :
oxayotl@Mahomet> ps aux | grep keyring ~
oxayotl 661 0.2 0.0 281972 4256 ? Sl 11:11 0:00 /usr/bin/gnome-keyring-daemon --daemonize --loginSo, it is yet another command that is launching gnome-keyring-daemon.
Offline
This boot, everything worked fine. Maybe an upgrade fixed it? Is it solved for you too ?
Offline
Yes, after reconfiguring GDM to auto-login, it is now working again :-)
Thank you to whomever resolved this problem!
Offline
Hi, I have the same problem with lxdm, can you explain me how you did?
Thanks
Offline
Now works editing:
/etc/pam.d/lxdm
comment
# -session optional pam_gnome_keyring.so auto_start
Offline
Similarly, for SLiM, I edited /etc/pam.d/slim to comment out this line:
#-session optional pam_gnome_keyring.so auto_startand that seems to have done the trick.
Offline
I know this is a forum for Arch Linux, but I have this very same problem on a Gentoo Linux system and I don't know how to fix it. How did you enable/disable autologin? Which file should I edit?
grep "pam_gnome_keyring.so auto_start" /etc/pam.d/*
/etc/pam.d/gdm-autologin:-session optional pam_gnome_keyring.so auto_start
/etc/pam.d/gdm-fingerprint:session optional pam_gnome_keyring.so auto_start
/etc/pam.d/gdm-password:session optional pam_gnome_keyring.so auto_start
/etc/pam.d/gdm-pin:session optional pam_gnome_keyring.so auto_start
/etc/pam.d/gdm-smartcard:-session optional pam_gnome_keyring.so auto_start
/etc/pam.d/system-login:session optional pam_gnome_keyring.so auto_startOffline
The problem was due to the fact that gnome-keyring-daemon processes were running as root on my system because /usr/bin/gnome-keyring-daemon had the setuid bit enabled. See Gentoo bug 513870 (https://bugs.gentoo.org/show_bug.cgi?id=513870) for more details. No need to edit any file in /etc/pam.d/.
Offline