GNOME Bugzilla – Bug 112562
gnome panel crashed suddenly
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.2.0.1 Synopsis: gnome panel crashed suddenly Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Bug-buddy popped up on my screen. Steps to reproduce the problem: 1. unsure. I had accidentally called up help for some program and had closed the window before it had rendered. 2. 3. Actual Results: crash & bug buddy appearing Expected Results: no bug buddy. How often does this happen? first time Additional Information: Debugging Information: 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)...[New Thread 1086430112 (LWP 14469)] (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)...0xffffe002 in ?? ()
+ Trace 36683
Thread 1 (Thread 1086430112 (LWP 14469))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-08 05:50 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Looks like bug 107007 (gnome-panel), bug 110379 (gnome-terminal), and bug 111980 (nautilus). I'm pretty sure this (like the other bugs) is related to bug 105745, but in any event, we need a better stack trace. Can you get us one? [If you're using RedHat 9, you can do so with the following easy method; otherwise this will require recompiling from source: Install http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm and if the problem occurs again, submit the backtrace you get. Installing the debuginfo package will make the backtrace much more useful.] I am adding myself to the cc and marking as needinfo for now.
I have installed the gtk2-debuginfo package. We'll see if the bug occurs again.
Thanks. Note that you may have to wait quite a while--the consensus seems to be that this is a really rare bug. I'm just hoping that at least one person can duplicate this again after installing the debuginfo package.
wtanaka@yahoo.com: I'm going to mark this as a duplicate of bug 107007 for now, but if you can get a stack trace with debugging symbols, we'd still greatly appreciate seeing it. I realize that this is rare and that there's no way of predicting when you might get this again (if ever).
*** This bug has been marked as a duplicate of 107007 ***
Elijah, Seems fine to me. I'll probably just click through on the bug-buddy dialog box if it happens again. But hopefully this time the debugging symbols will be there.