GNOME Bugzilla – Bug 300941
gnome-panel error and panels have been modified
Last modified: 2005-04-18 05:15:26 UTC
Distribution: Debian testing/unstable Package: gnome-panel Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: gnome-panel error and panels have been modified Bugzilla-Product: gnome-panel Bugzilla-Component: help-docs Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Error window appears "The Application "gnome-panel" has quit unexpectedly." Both top and bottom panels have been modified. Unsure how it happened. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Everytime I Login Additional Information: Everytime I try to restart the application or close the window the error reappears. Both the top and bottom panels settings are different from those I applied. All the things I attached to the panel no longer appear. Right clicking on the panel does nothing. Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 1087399872 (LWP 4578)] (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)...0xffffe410 in __kernel_vsyscall ()
+ Trace 58293
Thread 1 (Thread 1087399872 (LWP 4578))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-17 09:11 ------- 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 stewart.faville@gmail.com. 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.
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. Matches the stack trace in bug 167262, which has been marked as a duplicate of 157723. *** This bug has been marked as a duplicate of 157723 ***