upowerd crashed with SIGSEGV in idevice_get_uuid()

Bug #605794 reported by Boden Matthews
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: upower

I was just browsing the internet, and then GDM crashed to terminal, displaying "checking battery state", and froze there. I had to perform a hard reboot to get back into GDM. I am on Ubuntu 10.10 Developmental Release, on a Toshiba Tecra A7.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-1
ProcVersionSignature: Ubuntu 2.6.35-7.12-generic 2.6.35-rc4
Uname: Linux 2.6.35-7-generic i686
Architecture: i386
Date: Thu Jul 15 18:18:43 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x1154cb <idevice_get_uuid+43>: mov %eax,(%edx)
 PC (0x001154cb) ok
 source "%eax" ok
 destination "(%edx)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 idevice_get_uuid () from /usr/lib/libimobiledevice.so.1
 lockdownd_client_new_with_handshake ()
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
Title: upowerd crashed with SIGSEGV in idevice_get_uuid()
UserGroups:

visibility: private → public
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 #604809, 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.

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.