Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 594751 - [abrt] crash in gnome-power-manager-2.30.1-1.fc13: __pthread_mutex_unlock_full: Process /usr/bin/gnome-power-preferences was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-power-manager-2.30.1-1.fc13: __pthread_mutex_unlock_ful...
Status: CLOSED DUPLICATE of bug 594748
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-power-manager
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:9fd7823983c95c07271f26e84b5...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-21 14:00 UTC by jeefoo
Modified: 2010-05-25 10:33 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-05-25 10:33:46 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-05-21 14:00 UTC, jeefoo
no flags Details

Description jeefoo 2010-05-21 14:00:44 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gnome-power-preferences
component: gnome-power-manager
crash_function: __pthread_mutex_unlock_full
executable: /usr/bin/gnome-power-preferences
global_uuid: 9fd7823983c95c07271f26e84b5874e8213e93f2
package: gnome-power-manager-2.30.1-1.fc13
rating: 4
reason: Process /usr/bin/gnome-power-preferences was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 jeefoo 2010-05-21 14:00:46 UTC
Created attachment 415689 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:33:46 UTC

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

Comment 3 Karel Klíč 2010-05-25 10:33:46 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #594748.

Sorry for the inconvenience.

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