Bug 597498

Summary: [abrt] crash in gnome-panel-2.30.0-1.fc13: raise: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: weinandt
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jeff.raber, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:e36377806ca62021e409591446ab22f0381f75b7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 17:46:46 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 weinandt 2010-05-29 08:19:48 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: raise
executable: /usr/bin/gnome-panel
global_uuid: e36377806ca62021e409591446ab22f0381f75b7
kernel: 2.6.33.4-95.fc13.i686.PAE
package: gnome-panel-2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

comment
-----
1. Hibernate
2. close lid
3. open lid
4. had to "hard reset" to recover
5. had to delete the panel config of gnome in the users homedir

How to reproduce
-----
1. offensichtlich ein Problem nach Hibernate und "aufwecken" daraus - das Problem war bei mir nicht reproduzierbar
2.
3.
Comment 1 weinandt 2010-05-29 08:19:50 UTC 
Created attachment 417823 [details]
File: backtrace
Comment 2 Jeff Raber 2010-11-06 06:01:04 UTC 
Seems similar to (but not the same as) bug 597281.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Karel Klíč 2010-11-08 17:46:46 UTC 

*** This bug has been marked as a duplicate of bug 595584 ***
Comment 4 Karel Klíč 2010-11-08 17:46: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 #595584.

Sorry for the inconvenience.