Bug 675578

Summary: [abrt] gnome-panel-2.32.0.2-2.fc14: : Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: DAKSH <abhijit4daksh>
Component: 0xFFFFAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dwmw2, elad, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-04 17:08:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description DAKSH 2011-02-06 19:45:24 UTC 
abrt version: 1.1.14
architecture: x86_64
cmdline: gnome-panel
comment: Nver happend this kind of problem and never hard of
component: gnome-panel
executable: /usr/bin/gnome-panel
kernel: 2.6.35.10-74.fc14.x86_64
package: gnome-panel-2.32.0.2-2.fc14
reason: Process /usr/bin/gnome-panel was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297018718
uid: 500

How to reproduce
-----
1.I just tried to open a 450 kb jpeg file with gimp
2.gimp crases twice and after that gnome panel disappeared and all icons on desktop started to bounce frequently. Unable to see andy menu option.
3.and not pad is always opening automatically. I closed it so many times by pressing escape but after closing it's appearing and opening again. 
4. tried to recover os but nothing happend
Comment 1 DAKSH 2011-02-06 19:58:01 UTC 
I'm sorry but I reported the bug twice dont' know my bug reporting tool showing bug is not submitted so I did it twice. you can close this bug report 675580
Comment 2 Elad Alfassa 2011-05-04 17:08:20 UTC 
Closing



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

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