Bug 556125 - [abrt] crash in gnome-panel-2.28.0-15.fc12
Summary: [abrt] crash in gnome-panel-2.28.0-15.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 550784
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:34b17185c63662c0c9e561132af...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-16 17:20 UTC by Ulrich Hobelmann
Modified: 2010-03-02 10:12 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-24 16:54:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.01 KB, text/plain)
2010-01-16 17:20 UTC, Ulrich Hobelmann 		no flags Details
View All

Description Ulrich Hobelmann 2010-01-16 17:20:39 UTC 
abrt 1.0.3 detected a crash.

Comment
-----
I have a laptop with an external display, external USB mouse+keyboard.
The display is configured (via GNOME) to be active, while the laptop display is off.

My computer froze after reconnecting the USB keyboard, so I rebooted it. Right when I logged in, GNOME crashed (but only the first time, second login worked).

I'm thinking there might be some "panel jumping" between the two displays (maybe the laptop display isnt turned off right away).

Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
executable: /usr/bin/gnome-panel
kernel: 2.6.31.9-174.fc12.i686
package: gnome-panel-2.28.0-15.fc12
rating: 4
reason: Process was terminated by signal 6 (Aborted)
Comment 1 Ulrich Hobelmann 2010-01-16 17:20:41 UTC 
Created attachment 384823 [details]
File: backtrace
Comment 2 Karel Klíč 2010-02-24 16:54:06 UTC 

*** This bug has been marked as a duplicate of bug 550784 ***
Comment 3 Karel Klíč 2010-02-24 16:54:06 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 #550784.

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