registry team mailing list archive

[HP <hph@xxxxxx>]

I ran into this problem yesterday. I usually don't lock off and put my Laptop into standby. So I can't tell when and what patch caused the problem. I do see the same effect that gkd is running but I cannot communicate with it.
As a workaround for now I made a script that kills the old daemon and starts a new one using the normal autostart.

Script gkd_helper.sh:
#!/bin/sh
killall gnome-keyring-daemon
/usr/bin/gnome-keyring-daemon --daemonize

Don't forget to chmod +x the file and put it somewhere. I have all my
scripts in .bin but everyone has it's own philosophy.

Autostart .config/autostart/gkd_helper.sh.desktop:
[Desktop Entry]
Type=Application
Exec=<path_to_helper_script>/gkd_helper.sh
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=GKD Helper
Comment=Gnome Keyring Helper Script

Adjust the <path_to_helper_script> to your path.

HTH someone,
HP

-- 
gnome-keyring-daemon fails to start
https://bugs.launchpad.net/bugs/573387
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for NULL Project.