upowerd crashed with SIGSEGV in idevice_get_uuid()

Bug #648237 reported by javalove93
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: upower

ran into this crash right after resume my laptop(x201s) from suspended status.
I couldn't notice any specific problem, but just crash icon appear at status bar.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4
Uname: Linux 2.6.35-22-generic-pae i686
Architecture: i386
CrashCounter: 1
Date: Mon Sep 27 00:33:50 2010
ExecutablePath: /usr/lib/upower/upowerd
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0xb75434cb <idevice_get_uuid+43>: mov %eax,(%edx)
 PC (0xb75434cb) 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 /usr/lib/libimobiledevice.so.1
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
Title: upowerd crashed with SIGSEGV in idevice_get_uuid()
UserGroups:

Revision history for this message
javalove93 (javalove93) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 idevice_get_uuid () from /usr/lib/libimobiledevice.so.1
 lockdownd_client_new_with_handshake ()
 up_device_idevice_refresh (device=0x95c48e0)
 up_device_idevice_coldplug (device=0x95c48e0)
 ?? () from /lib/libglib-2.0.so.0

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
MarcRandolph (mrand)
visibility: private → public
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.