GNOME Bugzilla – Bug 124308
gnome panel menubar causing panel crash
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Red Hat Linux release 9 (Shrike) Package: gnome-panel Severity: critical Version: GNOME2.4.0 2.4.x Gnome-Distributor: GNOME.Org Synopsis: gnome panel menubar causing panel crash Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: 2.4.x BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: Both menu types on the gnome panel fail to work. The gnome menu bar does not display when added and causes a crash No menus can open from the menu once it has crashed. There is a short period before the crash where right-click menus work ( the menu buttons and menubar still dont ) a new panel can be created. but quickly both panels fail to work again Steps to reproduce the crash: 1. 2. 3. Expected Results: panel would work as it has for weeks in the past How often does this happen? every time the panel is loaded Additional Information: 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)...[New Thread 1084165568 (LWP 19808)] 0xffffe002 in ?? ()
+ Trace 40759
Thread 1 (Thread 1084165568 (LWP 19808))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-10 14:07 ------- The original reporter (andrewf1@fitzsimon.com.au) 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.
*** This bug has been marked as a duplicate of 124299 ***