gnome-keyring-daemon: could not lookup ... (Intrepid)

Bug #296193 reported by dino99
12
Affects Status Importance Assigned to Milestone
GNOME Keyring
Fix Released
Medium
gnome-keyring (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-keyring

some messages from aut.log ( result of 8.04 upgraded to 8.10)

: gnome-keyring-daemon: couldn't lookup keyring component setting:. Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified
: Autolaunch error: X11 initialization failed.
: )gnome-keyring-daemon: couldn't lookup ssh component setting: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified
 Autolaunch error: X11 initialization failed.
 )gnome-keyring-daemon: couldn't lookup pkcs11 component setting: Failed to get connection to session: dbus-launch failed to autolaunch D-Bus session: No protocol specified
 Autolaunch error: X11 initialization failed.

Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
dino99 (9d9) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

 * Is this reproducible?
 * If so, what specific steps should we take to recreate this bug?

 This will help us to find and resolve the problem.

Changed in gnome-keyring:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in gnome-keyring:
status: Incomplete → Invalid
Revision history for this message
John McPherson (jrm+launchpadbugs) wrote :

since upgrading to 8.10, I get the gnome-keyring popup asking for my keyring passphrase the first time I run "ssh-add" after logging in. This happens every time I log in. I assume the problem is that my keyring is not being automatically unlocked by gdm with my login password.

I also have similar messages in auth.log. The one thing that the reporter missed out is that the auth.log messages are all coming from gdm.

The only non-standard thing that I can think about my setup is that pam tries to get userids from 'ldap' before falling back to 'unix'.

Let me know what else I can do to help debug this.

Changed in gnome-keyring:
status: Invalid → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you open the bug on bugzilla.gnome.org where the people writting the software will read it?

Revision history for this message
yamo (stephane-gregoire) wrote :

Hi,
Since I'm using Intrepid the gnome sessions doesn't work.

And today I read the auth.log!

I didn't found a bug on gnome.org :

http://bugzilla.gnome.org/buglist.cgi?cmdtype=runnamed&namedcmd=couldn%27t%20lookup%20keyring%20component%20setting

So I posted a new bug : http://bugzilla.gnome.org/show_bug.cgi?id=569788

You can add comment to clarify my bug (I often make mistake in English...)

Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue should be fixed in jaunty

Changed in gnome-keyring:
status: New → Fix Released
Changed in gnome-keyring:
status: Unknown → Fix Released
Changed in gnome-keyring:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.