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 407996 - crash on XSetIMValues() call when using xim and esperanto locale
crash on XSetIMValues() call when using xim and esperanto locale
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Input Methods
2.10.x
Other Linux
: Normal critical
: ---
Assigned To: Hidetoshi Tajima
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-02-14 20:41 UTC by Sebastien Bacher
Modified: 2018-02-10 03:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Sebastien Bacher 2007-02-14 20:41:11 UTC 
That bug has been opened on https://launchpad.net/bugs/83142

"Binary package hint: gedit

I'm using Feisty Herd 2 for about a week. Using the Esperanto locale makes it impossible to use dead keys in any application. When I try to change the input method, to see if it helps, the application crashes.

I have the following variable defined in my /etc/environment file:

GTK_IM_MODULE = "xim"

And I'm using Brazilian ABNT2 model keyboard, with the "br" layout.

When using other locale, say pt_BR, everything works as it should.

I tried to uncomment the lines referring the Esperanto locale in /usr/share/X11/locale/compose.dir and locale.dir, but it hasn't done any effect.
...
LANG=eo_XX.UTF-8
...
libgtk2.0-0 2.10.9-0ubuntu1
...
I think I solved this bug, and bug 84011 also: the composing rules of X for the Esperanto locales were commented in file:

/usr/share/X11/locale/compose.dir

lines 97 and 98, 362 and 363, 592 and 593, 857 and 858

and in file

/usr/share/X11/locale/locale.dir

lines 97 and 98, 345 and 346, 577 and 578, 825 and 826

Once I uncommented those lines, dead keys started to work again, and right-clicking in gedit to change input method also worked.
...
http://librarian.launchpad.net/6438135/_usr_bin_gedit.1000.crash
Crash file

Sending crash file.

I hope this is what you need."


Debug backtrace for the crash:

+ Trace 110775

  • #0 XSetIMValues
    at ../../../src/xlibi18n/ICWrap.c line 194
  • #1 gtk_im_context_xim_finalize
    at gtkimcontextxim.c line 586
  • #2 IA__g_object_unref
    at gobject.c line 1788
  • #3 gtk_im_multicontext_set_slave
    at gtkimmulticontext.c line 174
  • #4 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #5 IA__g_closure_invoke
    at gclosure.c line 490
  • #6 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #7 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #8 IA__g_signal_emit
    at gsignal.c line 2243
  • #9 IA__gtk_widget_activate
    at gtkwidget.c line 3946 






Comment 1


Matthias Clasen





          2018-02-10 03:28:42 UTC
        



We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.