Bug 701989

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: Tim Storsved <storsved>
Component: gnome-panelAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: biergaizi2009, jmmckee, markandeya.janaswamy, mimustafa.dyab, onejoshd, rianby64, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b5456a9b6df76d94d49bc2add60b5095b1f077cc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 18:11:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Tim Storsved 2011-05-04 13:29:49 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 36840 bytes
cmdline: gnome-panel
comment: I logged in to my laptop with fedora 14 installed.
component: gnome-panel
Attached file: coredump, 40894464 bytes
crash_function: _panel_applet_frame_update_flags
executable: /usr/bin/gnome-panel
kernel: 2.6.35.12-90.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)
time: 1304514426
uid: 501

How to reproduce
-----
1.Log in to fedora 14 (gnome) - panel unceremoniously crashes
2.
3.

Comment 1 Tim Storsved 2011-05-04 13:29:51 UTC
Created attachment 496790 [details]
File: backtrace

Comment 2 biergaizi2009 2011-05-07 05:12:54 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.It crashed when I loggin to Gnome.

Comment 3 biergaizi2009 2011-05-07 05:36:57 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.It crashed when I loggin to Gnome.

Comment 4 Joshua 2011-05-08 09:06:23 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I reboot the machine
2.it comes everytime I login
3.i have only 5 panels
4. i have compiz as default
5. low graphic mode stops the error from occuring, but as it is inferior to compiz...

Comment
-----
It might be something another piece of software did, but it always happens with compiz and it doesn't happen at all in low-graphic mode, i do not use the 3.0 gnome preview at all

Comment 5 Mohamed Imustafa 2011-07-05 17:58:38 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.unkown
2.
3.

Comment 6 Andres Rios 2011-09-12 21:56:31 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Power up computer
2.Log in to my session...
3.Crash

Comment 7 Markandeya Janaswamy 2011-10-26 04:17:19 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i did nothing
2.just opened 1st time and bug appeared
3.thats it

Comment 8 John McKee 2011-10-29 04:49:29 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.
3.
I'm not sure what happened.  I was looking at aUSB drive when the X session ended.  What I had left was a console display showing the boot process.  Keyboard was unresposive.  I pressed reset button and system came up normally.  After I signed on, I saw the abort error.

Comment 9 Markandeya Janaswamy 2011-10-30 03:56:05 UTC
Package: gnome-panel-2.32.0.2-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i did nothing
2.just opened 1st time and bug appeared
3.thats it

Comment 10 abrt-bot 2012-03-20 18:11:17 UTC
Backtrace analysis found this bug to be similar to bug #657157, closing as duplicate.

Bugs which were found to be similar to this bug: bug #650035, bug #657157

This comment is automatically generated.

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