upowerd crashed with SIGSEGV in up_history_item_to_string()

Bug #683777 reported by Loïc Alejandro
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: upower

Didn't do anything special. Just noticed the apport report icon.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-4
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Wed Dec 1 18:17:46 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7ff803f10396 <up_history_item_to_string+22>: cmp (%rdx),%rax
 PC (0x7ff803f10396) ok
 source "(%rdx)" (0xff000000ff000000) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 up_history_item_to_string () from /usr/lib/libupower-glib.so.1
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
Title: upowerd crashed with SIGSEGV in up_history_item_to_string()
UserGroups:

Revision history for this message
Loïc Alejandro (loic-alejandro) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 up_history_item_to_string (history_item=0x1a76300)
 up_history_array_to_file (list=0x1a38b20,
 up_history_save_data (history=0x1a38090)
 up_history_schedule_save_cb (history=0x7ff804117368)
 g_timeout_dispatch (source=0x1a78f80, callback=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-amd64-retrace
information type: 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.