GNOME Bugzilla – Bug 475734
crash in Text Editor: printing
Last modified: 2007-09-13 10:19:17 UTC
Version: 2.18.0 What were you doing when the application crashed? printing Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 66961408 vsize: 66961408 resident: 20340736 share: 13664256 rss: 20340736 rss_rlim: 4294967295 CPU usage: start_time: 1189515273 rtime: 188 utime: 171 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gedit' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208957216 (LWP 4261)] (no debugging symbols found) 0x00284402 in __kernel_vsyscall ()
+ Trace 161987
Thread 1 (Thread -1208957216 (LWP 4261))
No plugin installed in $HOME. ----------- .xsession-errors (22 sec old) --------------------- ** (gedit:4261): WARNING **: IPP request failed with status 1030 ** (gedit:4261): WARNING **: could not set the value of Settings.Document.Filter, node not found Caught non-fatal exception. Traceback: File "/usr/share/system-config-printer/system-config-printer.py", line 2432, in on_tvNPDevices_cursor_changed printer_name = self.foomatic.getPrinterFromCupsDevice(self.device) File "/usr/share/system-config-printer/foomatic.py", line 724, in getPrinterFromCupsDevice commandsets = device.id_dict["CMD"].split (",") AttributeError: 'list' object has no attribute 'split' Continuing anyway.. /usr/bin/gs: found /usr/bin/hpijs: found /usr/lib/cups/filter/foomatic-rip: found (gedit:4261): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GnomePrintConfig' --------------------------------------------------
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. *** This bug has been marked as a duplicate of 405900 ***