upowerd crashed with SIGSEGV in dbus_connection_send()

Bug #635645 reported by wylow
This bug report is a duplicate of:  Bug #629842: Crash notification after login. Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: upower

crash; 2.6.35-20 kernel ; video mode VESA.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic i686
Architecture: i386
Date: Sat Sep 11 12:00:13 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100822)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x6e3ed8 <dbus_connection_send+40>: mov 0x4(%esi),%eax
 PC (0x006e3ed8) ok
 source "0x4(%esi)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 dbus_connection_send () from /lib/libdbus-1.so.3
 dbus_g_method_return () from /usr/lib/libdbus-glib-1.so.2
 ?? ()
 g_cclosure_marshal_VOID__POINTER () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: upowerd crashed with SIGSEGV in dbus_connection_send()
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #629842, so 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.

visibility: private → public
tags: removed: need-i386-retrace
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.