gnome-keyring-daemon fails to start with autologin enabled

Wrong assumption. Need further review.

thank you for your bug report, I'm not confirming the issue

The problem occurs when GDM autologin is enabled.
I changed the description.

Few hours before, it was working smoothly (with previous version).

I can confirm this bug on my Jaunty system.
If I use gdm autologin gnome-keyring-daemon doesn't work and i get the same warnings.

Now it is confirmed.

Maybe reassess the bug importance to "Medium": this is annoying since the NetworkManager requires the keyring to unlock the wireless key.

there is also a post on jaunty forum about this issue:
http://ubuntuforums.org/showthread.php?t=1103184

This is a pretty major one for me.

Since gnome-keyring-daemon is started automatically, and appears to not like to be started manually, what's the best way to help produce more debugging information to help this get fixed?

And I should point out, i seem to be having this issue regardless of whether autologin is enabled. Is this bug description correct, or is this a much broader-hitting bug than described?

@Jeremy

I have autologin enabled. I confirm that the keyring does not start.

But if I logout, then logon again to the session, the gnome keyring is correctly started.

However, if you need to start it manually, the command is :
  gnome-keyring-daemon --start

It will complain, but it starts the process.

user@jaunty$ gnome-keyring-daemon --start
** Message: couldn't set environment variable in session: The name org.gnome.SessionManager was not provided by any .service files
GNOME_KEYRING_SOCKET=/tmp/keyring-GEkpjk/socket
SSH_AUTH_SOCK=/tmp/keyring-GEkpjk/socket.ssh
GNOME_KEYRING_PID=7979

user@jaunty$ ps 7979
  PID TTY STAT TIME COMMAND
 7979 pts/2 SL 0:00 gnome-keyring-daemon --start

Okay, thanks. I'm looking at a different issue then. I'll look elsewhere.

I also get this problem with autologin NOT enabled - I opened bug #356703 earlier before I saw this one. But if this bug is only for when autologin is enabled, mine is not a duplicate.

I also found a reference to the daemon not working at http://<email address hidden>/msg632785.html.

Actually, PAM is in charge of spawning gnome-keyring-daemon.

I applied the instructions here, and it works nicely:
/usr/share/doc/libpam-gnome-keyring/README.Debian

not sure that your change is correct, the pam integration is just useful to unlock the keyring when a password is entered, it's not required to get it started

the issue rather seems to be bug #344444

thank you for the details. I understand that gnome-keyring-daemon should be started "on-demand" using the DBus interface.

Incidentally I opened a bug because xfce4-session try (and fails) to run gnome-keyring-daemon. bug #357346