GNOME Bugzilla – Bug 149980
gnome-panel segfault when clicking redhat menu icon
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 1 (Yarrow) Package: gnome-panel Severity: normal Version: GNOME2.4.0 unspecified Gnome-Distributor: GNOME.Org Synopsis: gnome-panel segfault when clicking redhat menu icon Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: The gnome-panel crashes when I click on the redhat (start/launcher) menu. Only for one user. Login as root and there's no problem. Steps to reproduce the crash: 1. Login as non-root user 2. Click redhat menu 3. Expected Results: How often does this happen? Every time. Started happening after I inserted a mac-formatted cd into cd-rom drive. CD has long since been ejected and the system rebooted several times. Additional Information: 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)... (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 -1085104000 (LWP 1563)] (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)...0x008f1c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 49290
Thread 1 (Thread -1085104000 (LWP 1563))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-08-12 14:00 ------- 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 tsw@berkeley.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 bug has been marked as a duplicate of 134395 ***
Try deleting or renaming the file .recently-used to fix the problem.
*** Bug 150204 has been marked as a duplicate of this bug. ***