Red Hat Bugzilla – Bug 493701
(ibus) imsettings disconnect/reconnect kills gtk app
Last modified: 2009-04-07 00:43:51 EDT
* imsettings > Show status icon
* Run application like xchat
* Begin typing in a language like ibus-korean, leave it in pre-edit
* Click disconnect and reconnect on the imsettings-applet
IBUS:ERROR:ibusimcontext.c:584:_bus_connected_cb: assertion failed: (IBUS_IS_IM_CONTEXT (ibusimcontext))
Application crashes with this message.
Warren, do you use the focus-on-click mode for window manager? or you have never touched any configuration with gnome-window-properties say? please check /apps/metacity/general/focus_mode gconf key if you use metacity.
I don't recall changing any settings.
Thanks. well, imsettings doesn't do any real work to switch immodule but just sets the gconf key and gtk+ changes it on the focus change. I haven't looked at the source code for ibus immodule though, I guess it may assumes an input context is valid after focus is coming back?
or this needs to be confirmed, if this won't happens with a step like 1) disconnect 2) back to apps 3) reconnect again with imsettings 4) back to apps again, gtk+ might just reuse a old instance since it may looks like no immodule changed because unfortunately there are no implementation so far in gtk+ to update immodule except on the focus change.
ideally IM change would be applied immediately to resolve an issue not destroying old IM process. but ibus could has a workaround to validate if an input context is sane and reconnect as needed.
I fixed in ibus-1_1_0_20090407-1_fc11. Please test it.