Ubuntu
gnome-keyring package

gnome-keyring-daemon stalls after upgrading to jaunty beta

Bug #352269 reported by Björn Röder
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GNOME Keyring
Invalid
High
gnome-keyring (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-keyring

After upgrading to jaunty gnome-keyring-daemon wound not run. Trying to save any passwords (e.g. mail-notification) it would say it could not save any. When I followed the instructions in another forum saying one should remove ~/.gnome2/keyrings folder and restart, it firstly went well letting gnome-keyring-daemon come up again and save passwords. After another update (uptodate version from ubuntu repositories) it, however, started stalling again after I logged into my account. Now, even the solution mentioned above does not work anymore.

Starting gnome-keyring-daemon from console shows the following error message:

** 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-2cOEK8/socket
SSH_AUTH_SOCK=/tmp/keyring-2cOEK8/socket.ssh
GNOME_KEYRING_PID=5785

I started this bug report using apport ('ubuntu-bug gnome-keyring'). Hopefully, the report is attached to this entry.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: gnome-keyring 2.26.0-0ubuntu3
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-keyring
Uname: Linux 2.6.28-11-generic i686

Revision history for this message
Björn Röder (overgee) 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 try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-keyring (Ubuntu):
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

you might want to send the bug on bugzilla.gnome.org too where the people writting the code will read it they will have a better idea about the issue

Revision history for this message
Björn Röder (overgee) wrote :

I hope this is the right report.

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

there is no crash in this log

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

The bug is also on http://bugzilla.gnome.org/show_bug.cgi?id=577587

Changed in gnome-keyring (Ubuntu):
status: Incomplete → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gnome-keyring:
status: Unknown → New
Revision history for this message
bassam (bkurdali) wrote :

I have the same problem since the most recent update to the gnome-keyring package (2.26.0-0ubuntu4) - now the gnome-keyring-daemon is not started when I log in. however, if I run it from the terminal I get the message:

** Message: couldn't set environment variable in session: Setenv interface is only available during the Initialization phase
GNOME_KEYRING_SOCKET=/tmp/keyring-mrB9LY/socket
SSH_AUTH_SOCK=/tmp/keyring-mrB9LY/socket.ssh
GNOME_KEYRING_PID=5788

and then the gnome keyring daemon runs (doesn't crash) and all is well (e.g. empathy and evolution remember my passwords)
so for some reason, it is not starting at session start (it is still in Startup Application Preferences with the command gnome-keyring-daemon --start ). There is no crash report, no idea if it is crashing on startup, not being started, or exiting.

Revision history for this message
Jeremy Nickurak (nickurak) wrote :

Upstream's marked this as a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=575247 , which is marked as fixed. I'm still seeing a lot of crashes from gnome-keyring 2.26.0-0ubuntu7 .

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

will be fixed with the 2.16.1 update once accepted today

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.26.1-0ubuntu1

---------------
gnome-keyring (2.26.1-0ubuntu1) jaunty; urgency=low

  * New upstream version:
    - Fix many problems with the new secure memory allocator.
      (lp: #328167, #338158, #352269)
    - DBus now automatically starts the gnome-keyring service properly.
      (lp: #344444)
    - When auto activating the gnome-keyring DBus service, check for an
      already running daemon.
    - Don't print critical warnings when registering with DBus fails.
    - Bump glib dependency.
    - Add DBus method for getting the gnome-keyring environment variables.
      (lp: #345496)
    - Fix crash when prompting to unlock the keyring.
    - Initialize daemon with LOGNAME and USERNAME environment variables.
    - Build fixes
  * debian/patches/03_secure-mem_crash.patch:
    - the change is in the new version

 -- Sebastien Bacher <email address hidden> Mon, 13 Apr 2009 11:00:28 +0200

Changed in gnome-keyring (Ubuntu):
status: Fix Committed → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in gnome-keyring:
status: New → Invalid
Revision history for this message
bassam (bkurdali) wrote :

thanks! works great now :)

Bug Watch Updater (bug-watch-updater)
Changed in gnome-keyring:
importance: Unknown → High
status: Invalid → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in gnome-keyring:
status: Unknown → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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