After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 272078 - RTL composer crash in gtkhtml 3.5.5
RTL composer crash in gtkhtml 3.5.5
Status: RESOLVED FIXED
Product: GtkHtml
Classification: Other
Component: Editing
unspecified
Other All
: Normal blocker
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2005-02-01 22:00 UTC by Mark Gordon
Modified: 2005-08-31 22:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mark Gordon 2005-02-01 22:00:46 UTC
Distribution: Novell Linux Desktop 9 (i586)
Package: Evolution
Priority: Blocker
Version: GNOME2.6. 2.1.4
Gnome-Distributor: Novell, Inc.
Synopsis: RTL composer crash in gtkhtml 3.5.5
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous
Bugzilla-Version: 2.1.4
BugBuddy-GnomeVersion: 2.0 (2.6.1.1)
Description:
Description of the crash:
Composer crash (sorry, bug-buddy isn't offering a gtkhtml option; I'll
clean this up) when entering RTL text.  I'm using one of the Yiddish
input methods from gtk-im-extra

Steps to reproduce the crash:
1. Install gtk-im-extra
2. Open a composer window
3. Select either of the Yiddish input methods
4. Press the "a" key (you should get a pasekh-alef), then the space
bar.
5. ...then you crash

Expected Results:
space

How often does this happen?
Always (this seems to be the minimal case; I'm crashing after typing the
second character).

Additional Information:
http://gtk-im-extra.sourceforge.net/
gtkhtml2-3.5.5.0.200502011251-0.snap.novell.0.1
evolution-2.1.4.0.200502011251-0.snap.novell.0.1


Debugging Information:

Backtrace was generated from '/opt/gnome/bin/evolution-2.2'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1095605536 (LWP 14546)]
[New Thread 1120746416 (LWP 14615)]
[Thread debugging using libthread_db enabled]
[New Thread 1095605536 (LWP 14546)]
[New Thread 1120746416 (LWP 14615)]
[Thread debugging using libthread_db enabled]
[New Thread 1095605536 (LWP 14546)]
[New Thread 1120746416 (LWP 14615)]
[New Thread 1118645168 (LWP 14614)]
[New Thread 1116150704 (LWP 14599)]
[New Thread 1114049456 (LWP 14598)]
[New Thread 1109334960 (LWP 14567)]
[New Thread 1111571376 (LWP 14564)]
[New Thread 1107229616 (LWP 14562)]
[New Thread 1105128368 (LWP 14561)]
0xffffe410 in ?? ()

Thread 1 (Thread 1095605536 (LWP 14546))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #5 libgnomeui_segv_handle
    at gnome-ui-init.c line 741

      3221214080, 3221213800, 1091771272, 141425672, 1091952200,
3221213848, 
      1091897382, 3221214080, 1}}, sa_flags = 4, sa_restorer =
0x86e0028}
	pid = #0  0xffffe410 in ?? ()



Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Mark Gordon 2005-02-01 22:18:01 UTC
Hebrew works fine, so I'm not *entirely* sure that the input method
isn't at fault, though it works in gedit, xchat, etc.
Comment 2 Radek Doulik 2005-02-02 16:57:52 UTC
that might be problem in IM code. using Isr keyboard switched by
keyboard indicator in panel works OK for me. sure I will try to fix
that. could you meanwhile try the panel keyboard switcher and look if
other things work as supposed?
Comment 3 Radek Doulik 2005-02-02 16:59:49 UTC
ah, didn't see your comment from yesterday. that's cool. I fixed few
things meanwhile in cvs (HEAD) so you may use snapshots which should
have more fixes than 3.5.5
Comment 4 Kaushal Kumar 2005-07-07 14:06:06 UTC
Mark: I tried using Arabic using the Keyboard switcher, and it worked fine.
Looks like it is fixed by Rodo. Could you please verify with the Head. Thanks. 
Comment 5 Mark Gordon 2005-08-31 22:59:41 UTC
I'm unable to reproduce this any more, though the Yiddish input method is still
flaky (not sure whether to blame the input method or gtkhtml), at least as
compared to the Hebrew keyboard map, which is working quite well for me now. 
Resolving as FIXED.