GNOME Bugzilla – Bug 492706
crash in Text Editor:
Last modified: 2007-11-12 22:22:53 UTC
Version: 2.18.0 What were you doing when the application crashed? Distribution: Mandriva Linux release 2007.1 (Official) for x86_64 Gnome Release: 2.18.0 2007-03-15 (Mandriva) BugBuddy Version: 2.18.0 System: Linux 2.6.17-15mdv #1 SMP Tue Aug 14 18:32:17 MDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Gorilla Icon Theme: Gorilla Memory status: size: 321826816 vsize: 321826816 resident: 26054656 share: 14934016 rss: 26054656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1194012291 rtime: 267 utime: 239 stime: 28 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 47587442490640 (LWP 3103)] (no debugging symbols found) 0x0000003519a0cc2e in waitpid () from /lib64/libpthread.so.0
+ Trace 174612
Thread 1 (Thread 47587442490640 (LWP 3103))
No plugin installed in $HOME. ----------- .xsession-errors (557880 sec old) --------------------- (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", (npviewer.bin:24702): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap", ...Too much output, ignoring rest... --------------------------------------------------
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 443083 ***