GNOME Bugzilla – Bug 145857
error message will not go away
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: error message will not go away Bugzilla-Product: gnome-panel Bugzilla-Component: Panel Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: There is a permanent reoccuring error message. It seems to have started when I clicked the main menu in the lower left side of the panel. Steps to reproduce the crash: 1. Sorry, I can't tell you anything at all. 2. 3. Expected Results: How often does this happen? This is the first time. Additional Information: Not long ago the computer would find some file system inconsistencies while booting up. That might have something to do with it. 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 -1085239168 (LWP 4845)] (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)... 0x00960c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 47519
Thread 1 (Thread -1085239168 (LWP 4845))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-08 16:30 ------- 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 johnjeannette@earthlink.net. 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. *** This bug has been marked as a duplicate of 134395 ***