Bug 688576

Summary: [abrt] xfce4-power-manager-1.0.3-1.fc15: g_type_check_instance_is_a: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: xfce4-power-managerAssignee: Christoph Wickert <cwickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: cwickert, maxamillion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:aa4579490915273c3548883d7fec0ff9faee286e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-06 21:12:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Horst H. von Brand 2011-03-17 11:55:29 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 17377 bytes
cmdline: xfce4-power-manager
component: xfce4-power-manager
Attached file: coredump, 12017664 bytes
crash_function: g_type_check_instance_is_a
executable: /usr/bin/xfce4-power-manager
kernel: 2.6.38-1.fc15.x86_64
package: xfce4-power-manager-1.0.3-1.fc15
rating: 4
reason: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
time: 1300362312
uid: 500

How to reproduce
-----
1. Started my XFCE session, after removing the intel_ips kernel module from tty2
2.
3.
Comment 1 Horst H. von Brand 2011-03-17 11:55:32 UTC 
Created attachment 485990 [details]
File: backtrace
Comment 2 Christoph Wickert 2011-03-25 00:01:18 UTC 
Can you reproduce this crash or is it random?
Comment 3 Christoph Wickert 2011-06-11 22:51:41 UTC 
Hi Horst, any news here? Does xfce4-power-manager crash every time you remove the kernel module?
Comment 4 Christoph Wickert 2011-10-06 21:12:19 UTC 
No feedback. Closing as duplicate because we have more info in bug 714519.

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