GNOME Bugzilla – Bug 485507
crash in Text Editor: choosing print page size...
Last modified: 2007-10-13 18:04:49 UTC
Version: 2.18.0 What were you doing when the application crashed? choosing print page size. 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: 69226496 vsize: 69226496 resident: 22982656 share: 13606912 rss: 22982656 rss_rlim: 4294967295 CPU usage: start_time: 1192036382 rtime: 190 utime: 171 stime: 19 cutime:0 cstime: 1 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 -1208682784 (LWP 3847)] (no debugging symbols found) 0x00323402 in __kernel_vsyscall ()
+ Trace 169334
Thread 1 (Thread -1208682784 (LWP 3847))
No plugin installed in $HOME. ----------- .xsession-errors (21 sec old) --------------------- ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed ** (gedit:3847): WARNING **: Writing output pipe failed (gedit:3847): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomePrintConfig' --------------------------------------------------
Thank you for reporting this bug. It look like a duplicate of bug 405900.
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 ***