upowerd crashed with SIGSEGV in free()

Bug #541490 reported by Lafa
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: upower

running on MacBook Pro 32bit pae did a suspend, and woke up from suspend.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Mar 18 10:20:42 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia wl
Package: upower 0.9.1-1
ProcCmdline: /usr/lib/upower/upowerd
ProcCwd: /
ProcEnviron:

ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
SegvAnalysis:
 Segfault happened at: 0xb7517ef1 <free+49>: mov 0x4(%edx),%eax
 PC (0xb7517ef1) ok
 source "0x4(%edx)" (0x0000002d) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 free () from /lib/tls/i686/cmov/libc.so.6
 usb_destroy_configuration () from /lib/libusb-0.1.so.4
 usb_free_dev () from /lib/libusb-0.1.so.4
 usb_find_devices () from /lib/libusb-0.1.so.4
 ?? ()
Title: upowerd crashed with SIGSEGV in free()
Uname: Linux 2.6.32-16-generic-pae i686
UserGroups:

Revision history for this message
Lafa (luis-alves) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 memmem (haystack_start=0x1, haystack_len=20,
 usb_destroy_configuration (dev=0x8531000)
 usb_free_dev (dev=0x8531000) at ../usb.c:293
 usb_find_devices () at ../usb.c:121
 up_device_csr_init (csr=0x857aaf0) at up-device-csr.c:289

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 upower (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Alex Murray (alexmurray) wrote :

Looks like a dupe of bug #526895

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.