GNOME Bugzilla – Bug 159235
Crash during login process
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: eggcups Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Crash during login process Bugzilla-Product: eggcups Bugzilla-Component: notification Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: After loging into the system notification of eggcups crash pops-up Steps to reproduce the crash: 1. Keep for 12 hours the loggin screen without activity 2. Loging 3. Expected Results: How often does this happen? Once 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 -151120192 (LWP 3293)] [New Thread 35646384 (LWP 3295)] [Thread debugging using libthread_db enabled] [New Thread -151120192 (LWP 3293)] [New Thread 35646384 (LWP 3295)] (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151120192 (LWP 3293)] [New Thread 35646384 (LWP 3295)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x0066e7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 52534
Thread 1 (Thread -151120192 (LWP 3293))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-11-23 14:35 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "eggcups". 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 david.colomer@kohlerphils.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.
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 ***