GNOME Bugzilla – Bug 435434
crash in Text Editor: Printing to SMB printer
Last modified: 2007-05-03 12:46:12 UTC
Version: 2.18.0 What were you doing when the application crashed? Printing to SMB printer Distribution: Fedora release 6.93 (Rawhide) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.20-1.3104.fc7 #1 SMP Sat Apr 21 22:20:43 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10299905 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 83275776 vsize: 83275776 resident: 21856256 share: 14434304 rss: 21856256 rss_rlim: 4294967295 CPU usage: start_time: 1178177270 rtime: 391 utime: 322 stime: 69 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 -1208850720 (LWP 3713)] (no debugging symbols found) 0x0040c402 in __kernel_vsyscall ()
+ Trace 132059
Thread 1 (Thread -1208850720 (LWP 3713))
No plugin installed in $HOME. ----------- .xsession-errors (13 sec old) --------------------- /usr/lib/cups/filter/foomatic-rip: found Canceling job 1 Canceling job 2 Canceling job 3 Canceling job 4 Canceling job 5 Canceling job 6 (gedit:3713): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed (gedit:3713): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed ** (gedit:3713): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:3713): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GnomePrintConfig' --------------------------------------------------
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 405900 ***