Description of problem: oowriter keep experiencing seg fault when used with im-sdk. Tried to reproduce in en_US locale but the error did not surfaced. Version-Release number of selected component (if applicable): openoffice.org-1.1.2-20.6.EL4 in dist-U1 im-sdk-12.1-12.EL in dist-U1-HEAD How reproducible: Always Steps to Reproduce: 1.LANG=zh_TW.UTF-8 oowriter 2.CTRL-SPACE to activate LE 3.enter 'a' 4 times 4.right mouse click on anywhere in the text area of oowriter till oowriter seg fault (took me 4 clicks) Actual results: Seg fault Expected results: No seg fault Additional info: I tried Dan's recent libvclplug_gtk645li.so patch and it is able to stop the seg fault from occuring.
Additional Test Case 1. LANG=ja_JP.UTF-8 oowriter 2. CTRL-SPACE to activate LE 3. enter 'a' 4 times 4. right mouse click on anywhere in the text area of oowriter till oowriter seg fault (took me 4 clicks)
llim: openoffice.org-1.1.2-21.6.EL4 in dist-4E-U1-HEAD should correct this crash.
llim: good QA'ing in U1 New im-sdk in -HEAD need to be pushed *along* with OOo to get this fix as well. We cannot risk to have a crashing system.
->modified since current builds (-21 and -22) have this fix. It involves protecting calls to gtk_im_context_reset() so that while inside the gtk_im_context_reset() we don't allow recursion, similar to the "need_im_reset" stuff in GTK+. Segfault was actually a stack overflow due to this recursion.
Tested with openoffice.org-1.1.2-22.6.EL4 against CJKI locale, confirmed this has been fixed.
did this one get shipped ?
Took the chance to test with openoffice.org-1.1.2-24.6.0.EL4, cant reproduce the bug anymore.