GNOME Bugzilla – Bug 499897
crash in Text Editor:
Last modified: 2007-11-27 09:47:13 UTC
Version: 2.18.2 What were you doing when the application crashed? 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.22-rc7 #1 SMP Fri Jul 6 05:59:47 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Snow-Apple Memory status: size: 120082432 vsize: 120082432 resident: 35852288 share: 23314432 rss: 35852288 rss_rlim: 4294967295 CPU usage: start_time: 1196143215 rtime: 403 utime: 349 stime: 54 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 -1208494368 (LWP 1586)] (no debugging symbols found) 0xb7fac410 in __kernel_vsyscall ()
+ Trace 179785
Thread 1 (Thread -1208494368 (LWP 1586))
No plugin installed in $HOME. Module versions: - glib 2.12.11 - gtk+ 2.10.13 - gtksourceview - libgnomeui 2.18.1 - libglade 2.6.0 - libgnomeprintui 2.18.0 - gnome-vfs 2.18.1 - pygobject 2.12.3 - pygtk 2.10.6 - gnome-python - gnome-python-desktop 2.18.0 - enchant - iso-codes Python module versions: - python 2.5 - pygtk 2.10.6 (GTK+ 2.10.13) - gnome-python 2.18.1 ----------- .xsession-errors (29 sec old) --------------------- x_order_2: colinear! x_order_2: colinear! colinear! colinear! x_order_2: colinear! x_order_2: colinear! x_order_2: colinear! x_order_2: colinear! x_order_2: colinear! x_order_2: colinear! (gedit:1586): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `GnomePrintConfig' (bug-buddy:1669): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field --------------------------------------------------
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 ***