GNOME Bugzilla – Bug 153248
gnome-cups-add crashes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Debian 3.1 Package: gnome-system-tools Severity: normal Version: GNOME2.6.1 0.18 Gnome-Distributor: Debian Synopsis: gnome-cups-add crashes Bugzilla-Product: gnome-system-tools Bugzilla-Component: runlevel-admin Bugzilla-Version: 0.18 BugBuddy-GnomeVersion: 2.0 (2.6.1.1) Description: Description of the crash: gnome-cups-add hangs when I try to add a new printer Steps to reproduce the crash: 1. Open gnome-cups-manager from command line or menu 2. select add new printer 3. It crash Expected Results: Printer adding help or something like that How often does this happen? Always Additional Information: >gnome-cups-manager --version Gnome gnome-printer-view 0.18 > gnome-cups-add --version Gnome gnome-cups-add 0.18 Gnome 2.6.1 on Debian Sarge Debugging Information: Backtrace was generated from '/usr/bin/gnome-cups-add' (no debugging symbols found)...Using host libthread_db library "/lib/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 16384 (LWP 2123)] [New Thread 32769 (LWP 2124)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x40650c0b in waitpid () from /lib/libpthread.so.0
+ Trace 50328
Thread 1 (Thread 16384 (LWP 2123))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-21 04:45 ------- Unknown version 0.18 in product gnome-system-tools. Setting version to "0.22.0". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-system-tools". 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 aurelio@frenopatico.net. 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 154554, which has been marked as a duplicate of 151756. *** This bug has been marked as a duplicate of 151756 ***