GNOME Bugzilla – Bug 323825
gnome-panel crashes unconditionally
Last modified: 2005-12-14 22:13:55 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: critical Version: GNOME2.10.2 2.10.x Gnome-Distributor: Debian Synopsis: gnome-panel crashes unconditionally Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: I simply start GNOME and it says the the panel died unexpectedly. Steps to reproduce the crash: 1. Get to gdm login screen 2. log in to gnome with my user Expected Results: When loading the environment, gnome2 just says that the panel crashed unexpectedly. How often does this happen? Always. Additional Information: I have tried everything from removing the entire ~/.gnome2 directory to .gconf and .gconfd to no avail. It always crashes with my user. If I instead create a new user and log in, the environment works. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (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) [Thread debugging using libthread_db enabled] [New Thread -1222297920 (LWP 15323)] [New Thread -1225163856 (LWP 15445)] (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) (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) 0xb7a34231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 64544
Thread 1 (Thread -1222297920 (LWP 15323))
------- Bug moved to this database by unknown@gnome.bugs 2005-12-11 22:01 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was linuxfud@gmail.com.
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. As a workaround, remove ~/.recently-files *** This bug has been marked as a duplicate of 172587 ***