Bug 607849

Summary: [abrt] gnome-panel-2.31.2-4.fc14: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Kurt Driver <kurtdriver>
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: 14CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:163f127c943f25f4de13c37630e7ffa534b41328
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:55:49 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 Kurt Driver 2010-06-25 02:34:55 UTC
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: gnome-panel
component: gnome-panel
executable: /usr/bin/gnome-panel
global_uuid: 163f127c943f25f4de13c37630e7ffa534b41328
kernel: 2.6.35-0.2.rc3.git0.fc14.x86_64
package: gnome-panel-2.31.2-4.fc14
rating: 0
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1277425212
uid: 500

How to reproduce
-----
1.I was unaware of this until I read in in abrt.
2.
3.

Comment 1 Kurt Driver 2010-06-25 02:34:59 UTC
Created attachment 426749 [details]
File: backtrace

Comment 2 Bug Zapper 2010-07-30 12:13:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 abrt-bot 2012-03-21 14:55:49 UTC
Backtrace analysis found this bug to be similar to bug #609111, closing as duplicate.

Bugs which were found to be similar to this bug: bug #600133, bug #609111

This comment is automatically generated.

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