Bug 587206 - [abrt] crash in upower-0.9.2-1.fc13: Process /usr/libexec/upowerd was killed by signal 11 (SIGSEGV)
[abrt] crash in upower-0.9.2-1.fc13: Process /usr/libexec/upowerd was killed ...
Status: CLOSED DUPLICATE of bug 580570
Product: Fedora
Classification: Fedora
Component: libusb1 (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Jindrich Novy
Fedora Extras Quality Assurance
abrt_hash:11cafa1ab193886edcc3470378f...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-04-29 07:34 EDT by James Laska
Modified: 2013-09-02 02:48 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-18 09:08:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (12.24 KB, text/plain)
2010-04-29 07:34 EDT, James Laska
no flags Details

  None (edit)
Description James Laska 2010-04-29 07:34:27 EDT
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 07:34:29 EDT
Created attachment 410068 [details]
File: backtrace
Comment 2 Richard Hughes 2010-04-29 07:59:27 EDT
Looks like libusb exploding.
Comment 3 James Laska 2010-05-18 09:08:55 EDT

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

Note You need to log in before you can comment on or make changes to this bug.