GNOME Bugzilla – Bug 159450
notification of failure when I open ed fedora immediately upon login as user
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: notification of failure when I open ed fedora immediately upon login as user Bugzilla-Product: gnome-utils Bugzilla-Component: gdict Bugzilla-Version: 0.17 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: received notification of crash in window, followed instructions on reporting Steps to reproduce the crash: 1. happened upon boot, no user commands given before it happened 2. 3. Expected Results: How often does this happen? first 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 -151112000 (LWP 3033)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x003387a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52649
Thread 1 (Thread -151112000 (LWP 3033))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-25 10:00 ------- 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 rcswitzer@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 158683 ***