GNOME Bugzilla – Bug 170763
Crash on login with dirty 2.8 profile and 2.10 binaries
Last modified: 2005-03-18 15:39:26 UTC
Distribution: Debian 3.1 Package: gnome-panel Severity: critical Version: GNOME2.10.0 2.10.x Gnome-Distributor: JHBuild Synopsis: Crash on login with dirty 2.8 profile and 2.10 binaries Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.10.x BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: After login the gnome-panel repeatedly crashes and refuses to allow me to run. This is using a jhbuild gnome-2.10 on a debian testing box with 2.8.x installed and thus a gnome profile and settings pre-existing with 2.8.x values Steps to reproduce the crash: 1. login 2. 3. Expected Results: Successful login and gnome-panel runs How often does this happen? Every login Additional Information: Debugging Information: Backtrace was generated from '/home/portman/gnome-2.10/bin/gnome-panel' Using host libthread_db library "/lib/tls/libthread_db.so.1". `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. [Thread debugging using libthread_db enabled] [New Thread -1223554592 (LWP 29244)] [New Thread -1225581648 (LWP 29275)] 0xb73d7511 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 57015
Thread 1 (Thread -1223554592 (LWP 29244))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-18 02:22 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-panel". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was portman@uidaho.edu. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
This looks like the stack traces in bug 165127 and bug 160818 which have been marked as duplicates of bug 148719. It appears that the fix is to kill gnome-vfs-daemon so that a new one (i.e. the newer version will start). *** This bug has been marked as a duplicate of 148719 ***