Bug 493701

Summary: (ibus) imsettings disconnect/reconnect kills gtk app
Product: [Fedora] Fedora Reporter: Warren Togami <wtogami>
Component: ibusAssignee: Peng Huang <phuang>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: i18n-bugs, petersen, phuang, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-04-07 04:43:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 481098    

Description Warren Togami 2009-04-02 17:46:58 UTC
imsettings-0.106.1-2.fc11.x86_64
gtk2-2.16.0-1.fc11.x86_64
ibus-1.1.0.20090331-1.fc11.x86_64

* 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.

Comment 1 Akira TAGOH 2009-04-06 00:45:14 UTC
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.

Comment 2 Warren Togami 2009-04-06 00:50:48 UTC
click

I don't recall changing any settings.

Comment 3 Akira TAGOH 2009-04-06 01:44:09 UTC
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.

Comment 4 Peng Huang 2009-04-07 04:43:51 UTC
I fixed in ibus-1_1_0_20090407-1_fc11. Please test it.