GNOME Bugzilla – Bug 112219
gnome-panel crashed when removing default panel due to a fatal error. Application "gnome-panel" (process 12662) has crashed due to a fatal error. (Segmentation fault)
Last modified: 2004-12-22 21:47:04 UTC
Description of Problem: While removing the default top panel in Gnome 2.2 it will crash and reload both panels top and bottom. Steps to reproduce the problem: 1. Righ click on top panel 2. Delete this panel 3. Actual Results: Crashes Expected Results: Able to remove the panel How often does this happen? Everytime Additional Information:
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused the crash. Please see http://bugzilla.gnome.org/getting-traces.cgi for more information about getting a useful stack trace. I'm replacing the summary from info in the description and changing GNOMEVER2.0->GNOMEVER2.2 while I'm at it. Marking as NEEDINFO until we get a stack trace.
I have the same problem. Here is a trace: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 3685)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x40b82299 in wait4 () from /lib/libc.so.6
+ Trace 37185
Thread 1 (Thread 16384 (LWP 3685))
Thanks for providing the stack trace (I used it to find which one this was a duplicate of). This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Reopening so that I can mark as a duplicate...
*** This bug has been marked as a duplicate of 108603 ***