GNOME Bugzilla – Bug 728469
Fails to connect to libsecret (Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached)
Last modified: 2015-03-06 06:06:44 UTC
After upgrading to Gnome 3.12 in Arch Linux, I get the following error message when trying to retrieve my emails in Evolution: "Error while Fetching mail from 'ibes@riseup.net'. Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached" There is a workaround that consists in disabling auto-login in the installed display manager (GDM in my case). Source: https://bbs.archlinux.org/viewtopic.php?pid=1405329#p1405329
A user on the Arch Linux Forums pointed out that the problem does not seem to be with Evolution itself but with Gnome Keyring: https://bbs.archlinux.org/viewtopic.php?pid=1405842#p1405842
I also have this problem. Gentoo Linux and GNOME 3.10 here. > Failed to open folder. > The reported error was "Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached". I also have the GDM display manager, but I never used autologin (https://wiki.archlinux.org/index.php/GDM#Automatic_login), so I can't use this workaround.
I upgraded to GNOME 3.12, but Evolution still exhibits this problem. I also tried commenting the following line in /etc/pam.d/gdm_{autologin,fingerprint,password,pin,smartcard} and /etc/pam.d/system-login, without success: > session optional pam_gnome_keyring.so auto_start
My 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.
I'm seeing this too. I notice that passwords are no longer listed by Seahorse, though system certs/ssh keys/pgp keys are still there.
Thanks for a bug report. This looks like a distribution specific issue. As the Seahorse cannot access passwords too, then the issue is surely out of evolution. I agree with the above suggestion, thus I move this to libsecret.
Stef, are you sure this is NotGNOME? Do you have any explanation for this resolution? Personally, "Timeout was reached" means for me that the service was found and was made an attempt to run it, but it failed to respond in the given time frame, thus the D-Bus call failed. One of the reasons can be that the libsecret service (whichever executable it is) is stuck in the main thread and cannot react on D-Bus requests. A guide how to debug this will be helpful.
gnome-keyring-daemin is the libsecret service. https://wiki.gnome.org/Projects/GnomeKeyring/RunningDaemon To diagnose this issue, you can use tactics like: * d-feet * the journal * gnome-keyring-daemon --foreground