GNOME Bugzilla – Bug 164912
Eggcups crashes on login or restart
Last modified: 2005-01-22 15:48:47 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gnome-utils Severity: normal Version: GNOME2.8.0 0.17 Gnome-Distributor: Red Hat, Inc Synopsis: Eggcups crashes on login or restart Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: After updating Fedore Core 3, the current version of eggcups "quits unexpectedly". Steps to reproduce the crash: 1. Log in with Gnome UI 2. Read popup "eggcups" has quit unexpectedly 3. Expected Results: Normal login How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/eggcups' (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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1208154432 (LWP 5433)] [New Thread -1220768848 (LWP 5437)] [Thread debugging using libthread_db enabled] [New Thread -1208154432 (LWP 5433)] [New Thread -1220768848 (LWP 5437)] (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 -1208154432 (LWP 5433)] [New Thread -1220768848 (LWP 5437)] (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)...0x0020d7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 54807
Thread 1 (Thread -1208154432 (LWP 5433))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-22 10:16 ------- Unknown version 0.17 in product gnome-utils. Setting version to "unspecified". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-utils". Setting to default milestone for this product, '---' 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. Note that installing the prelink update from Fedora should fix this problem for you (as should waiting a day or so for the prelink cronjob to run...) *** This bug has been marked as a duplicate of 160111 ***