GNOME Bugzilla – Bug 479212
crash in Text Editor: tenttando imprimir Mode...
Last modified: 2007-09-22 10:04:29 UTC
Version: 2.18.0 What were you doing when the application crashed? tenttando imprimir Modelo Canon MP130 (scanner, impressora e copiadora 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: 67260416 vsize: 67260416 resident: 20930560 share: 14073856 rss: 20930560 rss_rlim: 4294967295 CPU usage: start_time: 1190452965 rtime: 108 utime: 97 stime: 11 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 -1208863008 (LWP 3425)] (no debugging symbols found) 0x0042e402 in __kernel_vsyscall ()
+ Trace 164609
Thread 1 (Thread -1208863008 (LWP 3425))
No plugin installed in $HOME. ----------- .xsession-errors --------------------- ** (gnome-default-printer:3417): WARNING **: IPP request failed with status 1030 ** (gnome-default-printer:3417): WARNING **: IPP request failed with status 1030 ** Message: adding printer MP130 ** (gnome-default-printer:3417): WARNING **: Couldn't find default printer in list! ** Message: printer MP130 attributes changed ** (gnome-default-printer:3417): WARNING **: IPP request failed with status 1030 ** (gedit:3425): WARNING **: IPP request failed with status 1030 ** (gedit:3425): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:3425): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' 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 ***