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 528502 - GTK does not destroy all im contexts immediately, when the im module is changed by xsettings.
GTK does not destroy all im contexts immediately, when the im module is chang...
Status: RESOLVED DUPLICATE of bug 522885
Product: gtk+
Classification: Platform
Component: Input Methods
2.2.x
Other All
: Normal normal
: ---
Assigned To: Hidetoshi Tajima
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2008-04-17 01:42 UTC by Peng Huang
Modified: 2008-09-29 04:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Peng Huang 2008-04-17 01:42:40 UTC 
Please describe the problem:
GTK does not destroy all im contexts immediately, when the im module is changed by xsettings.

Steps to reproduce:
1. use im-chooser to select scim as input method.
2.  open several input widgets, like gnome-terminal or gedit
3.  use im-chooser to disable input method.



Actual results:
GTK will not destroy all im contexts immediately. You could the scim icon still in tray bar.  You must focus all input widgetsone by one, and then those old im contexts will be destroyed. the scim icon will be closed.

Expected results:
GTK will destroy all old im contexts immediately, when the im modules setting is changed via xsettings.

Does this happen every time?
always

Other information:
Changing im modules settings by xsettings is a new feature. Please ref to http://bugzilla.gnome.org/show_bug.cgi?id=502446 .
Comment 1 Matthias Clasen 2008-09-29 04:14:17 UTC 

*** This bug has been marked as a duplicate of 522885 ***