GNOME Bugzilla – Bug 153886
eggcups crashed shortly after boot to multiuser runlevel 5
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2.91 (FC3 Test 2) Package: eggcups Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: eggcups crashed shortly after boot to multiuser runlevel 5 Bugzilla-Product: eggcups Bugzilla-Component: session-cupsd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Error! dialog box appeared on X11 screen of non-superuser. Bug Buddy covered up the Error box, and it does not redraw; but the message was something like "Application `eggcups' has crashed. You can tell the developers if you want." I'm blindly pushing what I think are the right buttons. Why doesn't Bug Buddy "know" it was eggcups, of desktop-printing-0.14.1-1 of FC3test2? Steps to reproduce the crash: 1. unknown 2. 3. Expected Results: no crash How often does this happen? first time in 6 days of Fedora Core 3 test 2. 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 -151121792 (LWP 3286)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x005f0782 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 50532
Thread 1 (Thread -151121792 (LWP 3286))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-27 16:17 ------- 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 153672 ***