GNOME Bugzilla – Bug 168321
Not sure of the cause of this one.
Last modified: 2005-02-23 23:34:21 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: eggcups Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: Not sure of the cause of this one. Bugzilla-Product: eggcups Bugzilla-Component: session-cupsd Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Have two TCP queues on a Hawking USB print server, an HP OfficeJet5510 using stock driver for OfficeJet 5500 series and and HP LaserJet 1012 using stock LaserJet 1012 driver, both with the recommended driver. I attempted to print from a Mozilla Thunderbird window, and the job is sent, but never prints. I tried to cancel the queued print jobs, and eventually, eggcups crashed. The print queue icon on the menubar still appears. Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? This is the 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 -1208412480 (LWP 11217)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x004717a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 56056
Thread 1 (Thread -1208412480 (LWP 11217))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-02-23 18:26 ------- 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. Matches the stack trace in bug 165810, which has been marked as a duplicate of 159718. *** This bug has been marked as a duplicate of 159718 ***