GNOME Bugzilla – Bug 111663
Intermittent crashes for no apparent reason
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: critical Version: 2.2.0.1 Synopsis: Intermittent crashes for no apparent reason Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: gnome-panel just crashes from time to time on RH9 Workstation install with all fixes from RHN Steps to reproduce the problem: 1. boot 2. use 3. crash after some time Actual Results: crash Expected Results: rock-bottom-solid software ;-) How often does this happen? approx. every 3hrs (?) Additional Information: added wireless and battery applets, else standard config 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 1086397344 (LWP 2627)] (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 36306
Thread 1 (Thread 1086397344 (LWP 2627))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-26 16:39 ------- The original reporter (cipher@bluewin.ch) 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.
cipher@bluewin.ch: There's been a number of duplicates with the same stack trace, but apparently it's not enough info for the developers to go on. If you can duplicate this, can you try getting a better stacktrace? Owen posted the following comment in one of the duplicates on how to do so: Could you 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'm adding myself to the cc list so that I can catch any extra info attached and forward it to where-ever it needs to end up. *** This bug has been marked as a duplicate of 107498 ***