GNOME Bugzilla – Bug 132221
After Dist-Upgrade in unstable branch, existing user gnome2 configuration crashes gnome2-panel at startup
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: normal Version: GNOME2.4.1 unspecified Gnome-Distributor: Debian Synopsis: After Dist-Upgrade in unstable branch, existing user gnome2 configuration crashes gnome2-panel at startup Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Gnome 2 session configuration crashes the panel at startup. So far, have been unable to identify the configuration issue. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Every time with existing configuration, not with a new user. Additional Information: Not critical (as I can re-create that user), but significant in terms of ensuring future upgrades work well 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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New Thread 1086319328 (LWP 3740)] (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)...0x409463ee in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 43423
Thread 1 (Thread 1086319328 (LWP 3740))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-22 12:41 ------- The original reporter (roger.barrett@intuwave.com) 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.
Unfortunately, this stack trace is not very useful. However, we appreciate the effort. Thanks, and please do submit another trace if you find another crash
reopening to mark as dup of bug 111147
*** This bug has been marked as a duplicate of 111147 ***