GNOME Bugzilla – Bug 480973
crash in Text Editor: printing a file
Last modified: 2007-09-28 12:05:14 UTC
Version: 2.18.0 What were you doing when the application crashed? printing a file 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: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 66699264 vsize: 66699264 resident: 19558400 share: 13266944 rss: 19558400 rss_rlim: 4294967295 CPU usage: start_time: 1190889519 rtime: 353 utime: 332 stime: 21 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 -1208101152 (LWP 10974)] (no debugging symbols found) 0x00d39402 in __kernel_vsyscall ()
+ Trace 165935
Thread 1 (Thread -1208101152 (LWP 10974))
No plugin installed in $HOME. ----------- .xsession-errors --------------------- (gedit:10939): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed (gedit:10939): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed ** (gedit:10939): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:10939): GnomePrint-CRITICAL **: gnome_print_config_unref: assertion `GNOME_IS_PRINT_CONFIG (config)' failed ** (gedit:10974): WARNING **: IPP request failed with status 1030 Model not found, discarding config ** (gedit:10974): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:10974): 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 ***