The problem occurs when GDM autologin is enabled.
I changed the description.
Few hours before, it was working smoothly (with previous version).
** Summary changed:
- gnome-keyring-daemon does not start (jaunty)
+ gnome-keyring-daemon fails to start with autologin enabled
** Description changed:
Binary package hint: gnome-keyring
- With last Jaunty update, the gnome-keyring-daemon does not start
- automatically.
+ With last Jaunty update, the gnome-keyring-daemon fails to start if you
+ enable the GDM autologin feature.
gnome-keyring 2.26.0-0ubuntu2
+ gdm 2.20.9-0ubuntu1
- This is probably due to a typo in the "desktop" file:
- --- a/etc/xdg/autostart/gnome-keyring-daemon.desktop Mon Mar 16 15:18:28
2009 +0100
- +++ b/etc/xdg/autostart/gnome-keyring-daemon.desktop Tue Mar 17 02:09:19
2009 +0100
- @@ -1,7 +1,7 @@
- [Desktop Entry]
- Type=Application
- Name=GNOME Keyring Daemon
- -Exec=gnome-keyring-daemon --start
- +Exec= gnome-keyring-daemon --start
- OnlyShowIn=GNOME;
- X-GNOME-Autostart-Phase=Initialization
- X-GNOME-AutoRestart=false
+ flor...@jaunty:~$ grep keyring .xsession_errors
+ Failed to run gnome-keyring-daemon: Failed to start child process «
gnome-keyring-daemon » (No such file or directory)
+ ** (nm-applet:3970): WARNING **: couldn't communicate with gnome keyring
daemon via dbus: Failed to execute program gnome-keyring-daemon: Success
+ ** (nm-applet:3970): WARNING **: couldn't communicate with gnome keyring
daemon via dbus: Failed to execute program gnome-keyring-daemon: Success
** Changed in: gnome-keyring (Ubuntu)
Assignee: Florent Xicluna (florent.x) => (unassigned)
Status: Incomplete => New
--
gnome-keyring-daemon fails to start with autologin enabled
https://bugs.launchpad.net/bugs/344014
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
