GNOME Bugzilla – Bug 388652
crash in System Log:
Last modified: 2006-12-22 20:01:26 UTC
Version: 2.16.0 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled ----------- .xsession-errors (8 sec old) --------------------- FIXME: need to reconnect to CUPS here Traceback (most recent call last): File "/usr/share/system-config-printer/system-config-printer.py", line 850, in on_btnApply_clicked self.populateList() File "/usr/share/system-config-printer/system-config-printer.py", line 389, in populateList self.printers = cupshelpers.getPrinters(self.cups) File "/usr/share/system-config-printer/cupshelpers.py", line 213, in getPrinters printers_conf = PrintersConf(connection) File "/usr/share/system-config-printer/cupshelpers.py", line 293, in __init__ self.parse(self.fetch('/admin/conf/printers.conf'), 'Printer') File "/usr/share/system-config-printer/cupshelpers.py", line 306, in fetch raise e cups.HTTPError: -1 ** (bug-buddy:5188): WARNING **: Couldn't load icon for Open Folder -------------------------------------------------- Memory status: size: 100593664 vsize: 0 resident: 100593664 share: 0 rss: 30502912 rss_rlim: 0 CPU usage: start_time: 1166801747 rtime: 0 utime: 57 stime: 0 cutime:9 cstime: 0 timeout: 48 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/sbin/gnome-system-log' (no debugging symbols found) Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208903456 (LWP 5184)] (no debugging symbols found) 0x00712402 in __kernel_vsyscall ()
+ Trace 96263
Thread 1 (Thread -1208903456 (LWP 5184))
Thanks for taking the time to report this bug. 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 in order to help the developers? *** This bug has been marked as a duplicate of 366458 ***