Bug 751121 - [abrt] xfce4-power-manager-0.8.5-1.fc14: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Summary: [abrt] xfce4-power-manager-0.8.5-1.fc14: Process /usr/bin/xfce4-power-manager...
Keywords:
Status: CLOSED DUPLICATE of bug 806600
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-power-manager
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4b9bf0c3370b47f4b909e7f58e7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-03 15:22 UTC by Martin Nyhus
Modified: 2012-03-30 12:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:18:02 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (16.22 KB, text/plain)
2011-11-03 15:22 UTC, Martin Nyhus
no flags Details

Description Martin Nyhus 2011-11-03 15:22:39 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 16605 bytes
cmdline: xfce4-power-manager --restart --sm-client-id 276765fd2-a532-4727-aa81-cb945d026ce8
component: xfce4-power-manager
Attached file: coredump, 3239936 bytes
crash_function: xfpm_battery_get_message_from_battery_state
executable: /usr/bin/xfce4-power-manager
kernel: 3.1.0-08907-g43672a0
package: xfce4-power-manager-0.8.5-1.fc14
rating: 4
reason: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: The crash happens seemingly at random, but always after resuming from suspend
time: 1320333619
uid: 500

Comment 1 Martin Nyhus 2011-11-03 15:22:42 UTC
Created attachment 531584 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 12:18:02 UTC
Backtrace analysis found this bug to be similar to bug #806600, closing as duplicate.

This comment is automatically generated.

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


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