GNOME Bugzilla – Bug 171690
printer does not function. Scanner does not function. Office word processor crashes.
Last modified: 2005-03-26 01:57:47 UTC
Distribution: Debian testing/unstable Package: printman Severity: normal Version: GNOME2.8.1 unspecified Gnome-Distributor: Ubuntu Synopsis: printer does not function. Scanner does not function. Office word processor crashes. Bugzilla-Product: printman Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: trying to get printer to work. Add new printer (removed old one) Steps to reproduce the crash: 1. remove printer hp 6119 2. click on add 3. Expected Results: add a new printer How often does this happen? twice now. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-cups-manager' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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)...[Thread debugging using libthread_db enabled] [New Thread 1088423168 (LWP 3982)] [New Thread 1115061168 (LWP 4116)] [Thread debugging using libthread_db enabled] [New Thread 1088423168 (LWP 3982)] [New Thread 1115061168 (LWP 4116)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 1088423168 (LWP 3982)] [New Thread 1115061168 (LWP 4116)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 57346
Thread 1 (Thread 1088423168 (LWP 3982))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-25 20:33 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "printman". 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 frank@columbiabasinmedia.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. Matches the stack trace in bug 160066, which has been marked as a duplicate of 151756. *** This bug has been marked as a duplicate of 151756 ***