GNOME Bugzilla – Bug 61324
Red Hat gedit crash [gdk_draw_text_wc]
Last modified: 2004-12-22 21:47:04 UTC
Package: gedit Severity: normal Version: 0.9.4 Synopsis: crashed Class: sw-bug Distribution: Red Hat Linux release 7.1 (Seawolf) System: Linux 2.4.2-2 i686 unknown C library: glibc-2.2.2-10 C compiler: 2.96 glib: 1.2.9 GTK+: 1.2.9 ORBit: ORBit 0.5.7 gnome-libs: gnome-libs 1.2.8 libxml: 1.8.10 gnome-print: gnome-print-0.25-9 gnome-core: gnome-core 1.2.4 Description: gedit crashed when i started typing few words in iso8859-5 charset. i siwtched the keyboard to support internationalization (which forks fine with all other apps). gedit never crashed like this, maybe i shoudln't send this bug report, but i started typing it, so here I am. best regards Tomislav Debugging information: (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x406f8519 in __wait4 () from /lib/i686/libc.so.6
+ Trace 10799
------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-28 05:35 ------- The original reporter (tmarkovski@mt.net.mk) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, chema@celorio.com.
*** Bug 62861 has been marked as a duplicate of this bug. ***
*** Bug 64350 has been marked as a duplicate of this bug. ***
*** Bug 66721 has been marked as a duplicate of this bug. ***
*** Bug 69032 has been marked as a duplicate of this bug. ***
*** Bug 69750 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of 51644 ***
*** Bug 93528 has been marked as a duplicate of this bug. ***