GNOME Bugzilla – Bug 165432
Eggcups crashes when I print to a Hawking HPS1U Printserver
Last modified: 2005-04-22 12:32:53 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: eggcups Severity: major Version: GNOME2.8.0 0.10 Gnome-Distributor: Red Hat, Inc Synopsis: Eggcups crashes when I print to a Hawking HPS1U Printserver Bugzilla-Product: eggcups Bugzilla-Component: session-cupsd Bugzilla-Version: 0.10 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: Almost every time I send a print job to print I get a crash of eggcups. I am printing to an HP Deskjet 3845 printer using the Hawking HPS1U print server. I have configured the queue to use IPP printing. When eggcups restarts, the print job completes with no visible errors. How often does this happen? Nearly every 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 -1208109376 (LWP 5536)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x004c27a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
+ Trace 54987
Thread 1 (Thread -1208109376 (LWP 5536))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-01-27 13:39 ------- 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 bgreenfield@neodeo.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.
Appears to be a unique stack trace, according to the simple-dup-finder.
Nope, it's a duplicate of bug 158750 it seems :-) *** This bug has been marked as a duplicate of 158750 ***