GNOME Bugzilla – Bug 496702
crash in Text Editor: changing font into "kapu...
Last modified: 2007-12-25 11:54:56 UTC
Version: 2.18.2 What were you doing when the application crashed? changing font into "kaputaunicode" 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.20-2925.13.fc7xen #1 SMP Tue Jul 17 10:38:27 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: 46620672 vsize: 46620672 resident: 23248896 share: 18608128 rss: 23248896 rss_rlim: 4294967295 CPU usage: start_time: 1195037025 rtime: 54 utime: 43 stime: 11 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 -1208174352 (LWP 7646)] (no debugging symbols found) 0x0081c402 in __kernel_vsyscall ()
+ Trace 177629
Thread 1 (Thread -1208174352 (LWP 7646))
No plugin installed in $HOME. Module versions: - glib 2.12.13 - gtk+ 2.10.14 - 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.14) - gnome-python 2.18.1 ----------- .xsession-errors (2087 sec old) --------------------- ICE default IO error handler doing an exit(), pid = 5474, errno = 0 kbuildsycoca running... ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81) ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81) ASSERT: "!icon.isEmpty()" in konq_pixmapprovider.cc (81) QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca kbuildsycoca running... Reusing existing ksycoca --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!