gnome-keyring-daemon crashed with SIGSEGV in dbus_connection_dispatch()

Bug #234728 reported by Laurent Bonnaud
14
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-keyring

I am not using gnome-keyring-daemon directly therefore I do not know exactly what happened. It is probably started on my system because I use KDE and evolution.

ProblemType: Crash
Architecture: i386
Date: Sun May 25 00:57:22 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-keyring-daemon
NonfreeKernelModules: fglrx
Package: gnome-keyring 2.22.1-1ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/gnome-keyring-daemon --foreground --components=keyring
Signal: 11
SourcePackage: gnome-keyring
StacktraceTop:
 ?? ()
 dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3
 ?? ()
 ?? ()
 __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0
Title: gnome-keyring-daemon crashed with SIGSEGV in dbus_connection_dispatch()
Uname: Linux 2.6.24-17-rt i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse kvm lpadmin plugdev scanner staff video

Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3
message_queue_dispatch (source=0x80fad58, callback=0,
IA__g_main_context_dispatch (context=0x80a73b0)
g_main_context_iterate (context=0x80a73b0, block=1,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in gnome-keyring:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Laurent Bonnaud (laurent-bonnaud) wrote : Re: [Bug 234728] Re: gnome-keyring-daemon crashed with SIGSEGV in dbus_connection_dispatch()

> Please try to obtain a backtrace

The Apport retracing service already did that:

  http://launchpadlibrarian.net/14724121/ThreadStacktrace.txt

Therefore I do not see what installing -dbgsym packages would add to
this.

Changed in gnome-keyring:
status: Incomplete → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in gnome-keyring:
status: New → Invalid
Revision history for this message
Muelli (ubuntu-bugs-auftrags-killer) wrote :

Reopened, as there seems to be no need for installing dbgsym as the reporter mentioned.

Changed in gnome-keyring:
status: Invalid → New
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Unfortunately the stack trace isn't complete, so I'll have to mark this bug as Invalid. Should you get another crash, please do use apport to file that as a new bug - hopefully we'll get a better crash report from it.

(It's possible this bug has been fixed, you see - but I can't tell for sure)

Changed in dbus (Ubuntu):
status: New → 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.