gnome-keyring Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached



Hello. I use GNOME 3.12 on a Gentoo Linux system. I cannot access my
e-mail account with Evolution and I also cannot connect to my VPN with
Network Manager. In both cases I get the following error message in
journalctl:

Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached

I reported two bugs on GNOME bugzilla, one for Evolution and the other
one for Network Manager:

- https://bugzilla.gnome.org/show_bug.cgi?id=728469
- https://bugzilla.gnome.org/show_bug.cgi?id=731372

In #gnome-hackers on GimpNet one person told me the cause could be that
I'm running GNOME Keyring as root:

$ ps aux | grep gnome-keyring-daemon
root      7476  0.0  0.0 359888  4724 ?        Sl   18:53   0:00
/usr/bin/gnome-keyring-daemon --start --components=ssh
root      7485  0.0  0.0 359884  4736 ?        Sl   18:53   0:00
/usr/bin/gnome-keyring-daemon --start --components=pkcs11
root      7492  0.0  0.0 359888  4720 ?        Sl   18:53   0:00
/usr/bin/gnome-keyring-daemon --start --components=secrets
root      7498  0.0  0.0 294352  4704 ?        Sl   18:53   0:00
/usr/bin/gnome-keyring-daemon --start --components=gpg

/run/user/1000/keyring and /home/fturco/.local/share/keyrings are both
owned by root:

$ ls -ld /run/user/1000/keyring
drwx------ 2 root fturco 120 Jun  9 18:53 /run/user/1000/keyring
$ ls -ld /home/fturco/.local/share/keyrings
drwx------ 2 root fturco 4096 Jun  9 18:53
/home/fturco/.local/share/keyrings

User with id 1000 is "fturco".

I don't know if it's relevant, but the gnome-keyring-daemon executable
has the setuid bit set:

$ ls -l /usr/bin/gnome-keyring-daemon 
-rws--x--x 1 root root 940184 Jun  8 16:18 /usr/bin/gnome-keyring-daemon

I also tried commenting out all keyring-related lines in /etc/pam.d
configuration files, with no success:

$ grep keyring /etc/pam.d/*
/etc/pam.d/gdm-autologin:#-auth       optional    pam_gnome_keyring.so
/etc/pam.d/gdm-autologin:#-session    optional    pam_gnome_keyring.so
auto_start
/etc/pam.d/gdm-fingerprint:#auth     optional pam_gnome_keyring.so
/etc/pam.d/gdm-fingerprint:#session  optional pam_gnome_keyring.so
auto_start
/etc/pam.d/gdm-password:#auth     optional pam_gnome_keyring.so
/etc/pam.d/gdm-password:#session  optional pam_gnome_keyring.so
auto_start
/etc/pam.d/gdm-pin:#auth     optional pam_gnome_keyring.so
/etc/pam.d/gdm-pin:#session  optional pam_gnome_keyring.so auto_start
/etc/pam.d/gdm-smartcard:#-auth       optional    pam_gnome_keyring.so
/etc/pam.d/gdm-smartcard:#-session    optional    pam_gnome_keyring.so
auto_start
/etc/pam.d/system-login:#auth           optional       
pam_gnome_keyring.so
/etc/pam.d/system-login:#password       optional       
pam_gnome_keyring.so
/etc/pam.d/system-login:#session                optional       
pam_gnome_keyring.so auto_start

How can I fix this problem? Please tell me if you need any other
informations. Thank you.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]