g-k-d hangs, consumes CPU then segfaults

Bug #338158 reported by Chris Jones
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Keyring
Invalid
Critical
gnome-keyring (Ubuntu)
Fix Released
High
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-keyring

Machine upgraded from Intrepid to Jaunty

I have a keyring that should be unlocked at login. Attempting to use it (e.g. for ssh) causes me to be prompted for the keyring password, then the key password. It then provides authentication for a few ssh sessions, but after a while hits 100% CPU. Trying to use it after that causes it to segfault.

Attaching some output from running it with gdb and debugging symbols installed. I have stripped my key/passphrase.

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

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=574247

Changed in gnome-keyring:
assignee: nobody → desktop-bugs
importance: Undecided → High
status: New → Triaged
Changed in gnome-keyring:
status: Unknown → New
Revision history for this message
atreju (atreju-tauschinsky) wrote :

There is a patch available upstream which I have applied and built in my ppa:
https://launchpad.net/~atreju-tauschinsky/+archive/ppa
Could someone test if this fixes the bug?

Revision history for this message
atreju (atreju-tauschinsky) wrote :

Also adding a .diff.gz based on upstream patch at http://bugzilla.gnome.org/show_bug.cgi?id=575247.
This is the first time I'm doing this, (after the packaging training session by dholbach yesterday) so please review and let me know if it is all kibosh...

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

could you add a debdiff rather than a diff.gz? it's much easier to review

Revision history for this message
atreju (atreju-tauschinsky) wrote :

Sure, here it is.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.26.0-0ubuntu4

---------------
gnome-keyring (2.26.0-0ubuntu4) jaunty; urgency=low

  * egg/egg-secure-memory.c: apply upstream patch from
    http://bugzilla.gnome.org/attachment.cgi?id=131888&action=view
    to fix LP: #338158

 -- Atreju Tauschinsky <email address hidden> Sat, 04 Apr 2009 08:04:51 +0200

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Released
Changed in gnome-keyring:
status: New → Invalid
Revision history for this message
Chris Jones (cmsj) wrote :

Apologies for the lateness, this does appear to fix the bug, I have been running with my old keyring fine. Thanks!

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

the change lead to frequent crashes, I've dropped it in jaunty now

Changed in gnome-keyring (Ubuntu):
milestone: none → ubuntu-9.04
status: Fix Released → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-keyring - 2.26.0-0ubuntu6

---------------
gnome-keyring (2.26.0-0ubuntu6) jaunty; urgency=low

  * debian/patches/03_secure-mem_crash.patch:
    - use svn version of the crasher fix change (lp: #338158)

 -- Sebastien Bacher <email address hidden> Wed, 08 Apr 2009 16:08:39 +0200

Changed in gnome-keyring (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Teemu Kiviniemi (teemuki) wrote :

I upgraded gnome-keyring from 2.26.0-0ubuntu4 to 2.26.0-0ubuntu6, and the problem with gnome-keyring is back. When I ssh to another server, gnome-keyring-daemon starts using 100% CPU and the ssh client hangs. Finally, gnome-keyring-daemon dies. 2.26.0-0ubuntu4 fixed this problem, but it reappeared in 2.26.0-0ubuntu6.

Revision history for this message
Jerone Young (jerone) wrote :

It appears this bug is not fully fixed yet.

Changed in gnome-keyring (Ubuntu):
status: Fix Released → Confirmed
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: Confirmed → 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
Changed in gnome-keyring:
importance: Unknown → Critical
status: Invalid → Unknown
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.

Other bug subscribers

Remote bug watches

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