Bug 587206

Summary: [abrt] crash in upower-0.9.2-1.fc13: Process /usr/libexec/upowerd was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: libusb1Assignee: Jindrich Novy <jnovy>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jnovy, jturner, pknirsch, rhbugs, rhughes, richard
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:11cafa1ab193886edcc3470378fe9662f124dec5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-18 13:08:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description James Laska 2010-04-29 11:34:27 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/upowerd
comment: Sometimes whene booting my system, it does not detect a battery.  I've not figured out how to reproduce, but 1 of every 2 boots seems to cause upowerd to fail and I don't see any battery icons.
component: upower
executable: /usr/libexec/upowerd
global_uuid: 11cafa1ab193886edcc3470378fe9662f124dec5
kernel: 2.6.33.2-57.fc13.x86_64
package: upower-0.9.2-1.fc13
rating: 4
reason: Process /usr/libexec/upowerd was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Boot system
Comment 1 James Laska 2010-04-29 11:34:29 UTC 
Created attachment 410068 [details]
File: backtrace
Comment 2 Richard Hughes 2010-04-29 11:59:27 UTC 
Looks like libusb exploding.
Comment 3 James Laska 2010-05-18 13:08:55 UTC 

*** This bug has been marked as a duplicate of bug 580570 ***