GNOME Bugzilla – Bug 113570
The panel crashes upon start of session repeatedly, then disappears and does not come back even after rebooting.
Last modified: 2004-12-22 21:47:04 UTC
Package: gnome-panel Severity: major Version: 2.0.6 Synopsis: The panel crashes upon start of session repeatedly, then disappears and does not come back even after rebooting. Bugzilla-Product: gnome-panel Bugzilla-Component: Panel BugBuddy-GnomeVersion: 2.0 (2.0.3) Description: Description of Problem: The panel crashes upon start of session repeatedly, then disappears and does not come back even after rebooting. Steps to reproduce the problem: 1. start Redhat 8 -- log in as regular user 2. unplug usual USB mouse and try to use laptop trackpad -- cursor messes up GNOME panel by showing/hiding rapidly as the cursor jumps around 3. next login, the panel appears in minimized position and immediately crashes several times. Each time the crash dialog is OK'd, it immediately crashes again. 4. finally the panel just vanishes and does not come back, even with repeated logins. 5. I renamed the ~/.gnome and ~/.gnome2 directories to hide them (hoping GNOME would revert to safe defaults) and rebooted. The panel appeared minimized and immediately crashed as in 3. above Actual Results: Expected Results: How often does this happen? It is still happening after 5 reboots Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 1001)] 0x408437f7 in waitpid () from /lib/i686/libpthread.so.0
+ Trace 37141
Thread 1 (Thread 16384 (LWP 1001))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-05-22 22:15 ------- Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. This particular bug has long since been fixed and workarounds as well as links to fixed packages can be found in bug report #94625. *** This bug has been marked as a duplicate of 94625 ***