upowerd crashed with SIGSEGV in vfprintf()

Bug #651671 reported by enb
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upower (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: upower

NA

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: upower 0.9.5-3
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Wed Sep 29 18:13:18 2010
ExecutablePath: /usr/lib/upower/upowerd
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
ProcCmdline: /usr/lib/upower/upowerd
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7f245cbeb7aa <vfprintf+16746>: repnz scas %es:(%rdi),%al
 PC (0x7f245cbeb7aa) ok
 source "%es:(%rdi)" (0x8246c8b48d88948) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: upower
StacktraceTop:
 vfprintf () from /lib/libc.so.6
 __vasprintf_chk () from /lib/libc.so.6
 g_vasprintf () from /lib/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/libglib-2.0.so.0
 g_error_new_valist () from /lib/libglib-2.0.so.0
Title: upowerd crashed with SIGSEGV in vfprintf()
UserGroups:

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

StacktraceTop:
 _IO_vfprintf_internal (s=0x7fffc8724650,
 *__GI___vasprintf_chk (result_ptr=0x7fffc87247a8,
 g_vasprintf () from /lib/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/libglib-2.0.so.0
 g_error_new_valist () 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-amd64-retrace
Revision history for this message
MarcRandolph (mrand) wrote :

Oops, wrong one

visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in upower (Ubuntu):
status: New → Confirmed
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.