Comment 74 for bug 66104

Also reproduced with libX11-0.99.3 fwiw.

Here is a backtrace of where gedit loops with kinput2:

#0 XIfEvent (dpy=0x6ca790, event=0x7fff84fd6000,
    predicate=0x2aaaaab427a0 <_CheckCMEvent>, arg=0x10b4000 " \220ݪ�*")
    at IfEvent.c:58
#1 0x00002aaaaab42cea in _XimXRead (im=0x10b4000, recv_buf=0x7fff84fd61f0 "",
    buf_len=2048, ret_len=0x7fff84fd6144) at imTrX.c:446
#2 0x00002aaaaab45f86 in _XimReadData (im=0x10b4000, len=0x7fff84fd61a6,
    buf=0x7fff84fd61f0 "", buf_size=2048) at imTransR.c:154
#3 0x00002aaaaab46323 in _XimRead (im=0x10b4000, len=0x7fff84fd71fe,
    buf=0x7fff84fd61f0 "", buf_size=2048,
    predicate=0x2aaaaab48c20 <_XimSyncCheck>, arg=0x10b8800 "\200\217ݪ�*")
    at imTransR.c:231
#4 0x00002aaaaab49d0e in _XimForwardEvent (ic=0x10b8800, ev=0x7fff84fd7290,
    sync=1) at imDefLkup.c:296
#5 0x00002aaaaab39c8b in _XimFilterKeypress (d=<value optimized out>,
    w=<value optimized out>, ev=0x7fff84fd7290,
    client_data=<value optimized out>) at imDefFlt.c:187
#6 0x00002aaaaaaf9104 in XFilterEvent (ev=0x7fff84fd7290,
    window=<value optimized out>) at FilterEv.c:99
#7 0x00002aaab4e7fecd in gtk_im_context_xim_register_type ()
   from /usr/lib64/gtk-2.0/2.10.0/immodules/im-xim.so