Bug 644670 - [abrt] gnome-panel-2.30.0-4.fc13: listener_popup_handle_lock: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.30.0-4.fc13: listener_popup_handle_lock: Process /usr/bi...
Keywords:
Status: CLOSED DUPLICATE of bug 606503
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:f155413bed323860e594b321b5f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-19 22:00 UTC by Sam Varshavchik
Modified: 2010-11-08 18:16 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:16:11 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (20.41 KB, text/plain)
2010-10-19 22:00 UTC, Sam Varshavchik 		no flags Details
View All

Description Sam Varshavchik 2010-10-19 22:00:04 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
crash_function: listener_popup_handle_lock
executable: /usr/bin/gnome-panel
kernel: 2.6.34.7-56.fc13.x86_64
package: gnome-panel-2.30.0-4.fc13
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1287525357
uid: 500

How to reproduce
-----
1. Attempt to add the clock applet to the panel
2. Nothing apparently happened when I clicked add
3. Right-clicked near the left corner of a horizontal panel
4. Noticed the "remove from panel" option. Something invisible as there
5. Selected "remove from panel"
6. Crash.
Comment 1 Sam Varshavchik 2010-10-19 22:00:06 UTC 
Created attachment 454457 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:16:11 UTC 

*** This bug has been marked as a duplicate of bug 606503 ***
Comment 3 Karel Klíč 2010-11-08 18:16:11 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 #606503.

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