GNOME Bugzilla – Bug 459379
crash in Text Editor: Attempting to print
Last modified: 2007-07-23 08:22:42 UTC
Version: 2.18.0 What were you doing when the application crashed? Attempting to print Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 14:56:37 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Foresight Icon Theme: Kreski-Lines Memory status: size: 362373120 vsize: 362373120 resident: 27774976 share: 19148800 rss: 27774976 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185154032 rtime: 97 utime: 88 stime: 9 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496382256 (LWP 18384)] [New Thread 1094719824 (LWP 18387)] (no debugging symbols found) 0x000000357420d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 149837
Thread 1 (Thread 46912496382256 (LWP 18384))
No plugin installed in $HOME. ----------- .xsession-errors (32 sec old) --------------------- ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed ** (gedit:18384): WARNING **: Writing output pipe failed (gedit:18384): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed --------------------------------------------------
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 443083 ***