GNOME Bugzilla – Bug 307550
CUPS died while trying to install printer
Last modified: 2005-06-13 19:53:19 UTC
Distribution: Debian testing/unstable Package: file-roller Severity: normal Version: GNOME2.8.1 0.25 Gnome-Distributor: Ubuntu Synopsis: CUPS died while trying to install printer Bugzilla-Product: file-roller Bugzilla-Component: general Bugzilla-Version: 0.25 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: A message appeared whan I was configuring CUPS using the main menu Steps to reproduce the crash: 1. ask for a new printer 2. accept default choices 3. click apply Expected Results: How often does this happen? twice till 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 4401)] [New Thread 1097366448 (LWP 4415)] [Thread debugging using libthread_db enabled] [New Thread 1088423168 (LWP 4401)] [New Thread 1097366448 (LWP 4415)] (no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 1088423168 (LWP 4401)] [New Thread 1097366448 (LWP 4415)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(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 60952
Thread 1 (Thread 1088423168 (LWP 4401))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-13 19:32 UTC ------- Unknown version 0.25 in product file-roller. Setting version to "unspecified". 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 none@hotmail.com.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report? *** This bug has been marked as a duplicate of 154582 ***