Bug 650035 - [abrt] gnome-panel-2.32.0.2-2.fc14: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: Process /usr/bin/gnome-panel was killed b...
Keywords:
Status: CLOSED DUPLICATE of bug 646539
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-panel
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6b89e3464b7f6d4c78141c3df8f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-05 03:39 UTC by Greg
Modified: 2010-11-08 07:40 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 07:40:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (29.76 KB, text/plain)
2010-11-05 03:39 UTC, Greg
no flags Details

Description Greg 2010-11-05 03:39:47 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gnome-panel
comment: Simple boot of system.
component: gnome-panel
crash_function: _panel_applet_frame_update_flags
executable: /usr/bin/gnome-panel
kernel: 2.6.35.6-48.fc14.i686
package: gnome-panel-2.32.0.2-2.fc14
rating: 4
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Nothing happened out of the ordinry except a report of failure. The panel started. 
time: 1288928074
uid: 500

Comment 1 Greg 2010-11-05 03:39:50 UTC
Created attachment 457996 [details]
File: backtrace

Comment 2 Andrew Kornak 2010-11-05 08:03:05 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Added Window Switcher Applet to Lower Panel
2. Crash...Crash...Crash
3. System kept flasing for 30 seconds until it settled down

Comment 3 Jeff Raber 2010-11-08 07:40:57 UTC

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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


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