GNOME Bugzilla – Bug 113644
Gnome Panel crashed without any appearant reason
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: normal Version: 2.2.0.1 Synopsis: Gnome Panel crashed without any appearant reason Bugzilla-Product: gnome-panel Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: Gnome Panel crashed without any appearant reason Steps to reproduce the problem: 1. Work with computer 2. Nothing in particular 3. Between actions, a crash occurred Actual Results: Crash Expected Results: No crash How often does this happen? For the first time Additional Information: RedHat 9, on an athlon 700 machine with 128 mb RAM. Reasonably clean install (1 week old) from ISO images, installed everything. Possible memory leak?? 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 1086435744 (LWP 2113)] (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)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...0xffffe002 in ?? ()
+ Trace 37168
Thread 1 (Thread 1086435744 (LWP 2113))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-24 09:34 ------- The original reporter (mrjb@dnd.utwente.nl) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
This looks a lot like the mysterious gtk+ crash that is showing up everywhere [See specifically bug 105745 for more info]. The g_source_set_closure function in the stack trace is new, though. A number of people are getting this, but the stack traces are unfortunately useless and we don't know how to reproduce the problem. Can you get a stacktrace with symbols for us? Since you're using RedHat 9, you can do so with the following easy method: 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.
If you have any more useful information about these crashes, please post them in bug 105745. *** This bug has been marked as a duplicate of 105745 ***