Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#11878 - gnome-keyring-daemon does not function properly/crashing

Attached to Project: Arch Linux
Opened by Viliam Šimovič (siigot) - Saturday, 25 October 2008, 12:19 GMT
Last edited by Aaron Griffin (phrakture) - Sunday, 09 November 2008, 05:27 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity High
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After update to GNOME 2.24 applications which use gnome-keyring-daemon do not function properly (cannot retrieve passwords).
It seems that they're not able to connect to daemon.

I don't know how it function in detail, but it seems that gnome-keyring-daemon is still crashing/restarting, and creates new socket every time.

Some observed information:

$ export
...
declare -x GNOME_KEYRING_PID="3134"
declare -x GNOME_KEYRING_SOCKET="/tmp/keyring-rnatfi/socket"
...

$ ps -ef
...
3868 3136 0 13:46 ? 00:00:00 /usr/lib/gnome-session/helpers/gnome-keyring-daemon-wrapper
3871 1 0 13:46 ? 00:00:00 /usr/bin/gnome-keyring-daemon
...

$ ls /tmp
...
keyring-3noF9l keyring-JXcMQa keyring-V4FH0i keyring-rnatfi
keyring-5zIFsl keyring-U1oGP7 keyring-ohIQhN
...

The PID is not the same. the SOCKET is not the one to which actual daemon is connected.
There are many sockets created in /tmp, due to daemon crashes.

Maybe the problem is also in gnome-keyring-daemon-wrapper.

Additional info:

* gnome-keyring 2.24.1-1
* seahorse 2.24.1-1
* evolution-data-server 2.24.1-1
* mail-notification 5.4-1
* gnome-desktop 2.24.0-2

Steps to reproduce:
- Open mail-notification or evolution with passwords stored in keyring.
- Try to change password, or add new keyring in seahorse.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Sunday, 09 November 2008, 05:27 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Saturday, 25 October 2008, 16:24 GMT
How do you start GNOME? Do you gave a dbus session bus running (not the one from DAEMONS in rc.conf, that's the system bus).
Comment by Viliam Šimovič (siigot) - Saturday, 25 October 2008, 16:31 GMT
GNOME is started from gdm, DBUS session bus is running...

3136 3102 0 12:04 ? 00:00:00 /usr/lib/gnome-session/gnome-session
3158 1 0 12:04 ? 00:00:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
3159 1 0 12:04 ? 00:00:03 /usr/bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
Comment by Viliam Šimovič (siigot) - Thursday, 06 November 2008, 13:29 GMT
Today I have recompiled gnome-keyring with ABS, and it works now!

Maybe the problem was only with my system. (but i didn't make any custom changes to the system, so it's only updated pure Arch (but 1 year+ old installation)).

Loading...