GNOME Bugzilla – Bug 476089
crash in Text Editor:
Last modified: 2007-09-13 03:23:46 UTC
Version: 2.18.0 What were you doing when the application crashed? 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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 74711040 vsize: 74711040 resident: 22454272 share: 14274560 rss: 22454272 rss_rlim: 4294967295 CPU usage: start_time: 1189484513 rtime: 175 utime: 160 stime: 15 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/i686/nosegneg/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208527136 (LWP 3246)] (no debugging symbols found) 0x0067e402 in __kernel_vsyscall ()
+ Trace 162248
Thread 1 (Thread -1208527136 (LWP 3246))
No plugin installed in $HOME. ----------- .xsession-errors (17 sec old) --------------------- (bug-buddy:3195): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Model not found, discarding config ** (gedit:3246): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:3246): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed (gedit:3246): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed ** (gedit:3246): WARNING **: could not set the value of Settings.Document.Filter, node not found (gedit:3246): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed (gedit:3246): libgnomeprintui-CRITICAL **: gnome_paper_selector_load_paper_size: assertion `GNOME_IS_PAPER_SELECTOR (ps)' failed --------------------------------------------------
*** This bug has been marked as a duplicate of 476088 ***