dbus-daemon crashed with SIGSEGV

Bug #602639 reported by Jānis Kangarooo
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: dbus

dont know what made it crash and dont know this programm

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: dbus 1.2.16-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-generic i686
Architecture: i386
Date: Tue Jul 6 23:32:11 2010
ExecutablePath: /bin/dbus-daemon
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /bin/dbus-daemon --fork --print-pid 5 --print-address 9 --session
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x22da4a: mov 0x4(%eax),%edx
 PC (0x0022da4a) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: dbus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: dbus-daemon crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Jānis Kangarooo (kangarooo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _dbus_list_unlink (list=0xbf81bb60, link=0x0) at dbus-list.c:509
 _dbus_message_remove_size_counter (message=0xbf81bb08,
 _dbus_connection_message_sent (connection=0x20e63cd8,
 ?? ()
 _dbus_connection_send_preallocated_and_unlock (

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in dbus (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 596309, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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