GNOME Bugzilla – Bug 158785
Error message appears when logging on to Gnome session
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: eggcups Severity: major Version: GNOME2.8.0 0.10 Gnome-Distributor: Red Hat, Inc Synopsis: Error message appears when logging on to Gnome session Bugzilla-Product: eggcups Bugzilla-Component: notification Bugzilla-Version: 0.10 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Logged on to Gome desktop. Eggcups reported fatal error. PC hangs Steps to reproduce the crash: 1. Log on to desktop 2. 3. Expected Results: How often does this happen? Every time Additional Information: Failsafe terminal and statrt eggcups from command line reports failure to locate message bus 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 -151148256 (LWP 3654)] [New Thread 105135024 (LWP 3656)] [Thread debugging using libthread_db enabled] [New Thread -151148256 (LWP 3654)] [New Thread 105135024 (LWP 3656)] [Thread debugging using libthread_db enabled] [New Thread -151148256 (LWP 3654)] [New Thread 105135024 (LWP 3656)] (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)...0x00ba47a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52254
Thread 1 (Thread -151148256 (LWP 3654))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-20 00:28 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "eggcups". 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. *** This bug has been marked as a duplicate of 151307 ***