GNOME Bugzilla – Bug 160300
EGGCUPS Fail when the computer start...
Last modified: 2004-12-22 21:47:04 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 Fail when the computer start... Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: EGGCUPS Crash at startup.... Steps to reproduce the crash: 1. Run yum update 2. reboot the machine 3. Expected Results: No Startup Errors How often does this happen? Everytime the system start... 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 -151148864 (LWP 2593)] [New Thread 157998000 (LWP 2600)] [Thread debugging using libthread_db enabled] [New Thread -151148864 (LWP 2593)] [New Thread 157998000 (LWP 2600)] [Thread debugging using libthread_db enabled] [New Thread -151148864 (LWP 2593)] [New Thread 157998000 (LWP 2600)] (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)...0x002e77a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 53107
Thread 1 (Thread -151148864 (LWP 2593))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-12-03 01:29 ------- 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, '---' 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 bernardino_lopez@yahoo.com. 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 151307 ***