Red Hat Bugzilla – Bug 106807
LTC4885-Possible bug in GTK and miniChinput integration
Last modified: 2007-04-18 12:58:18 EDT
The following has be reported by IBM LTC:
Possible bug in GTK and miniChinput integration
IBM/IntelliStation Z Pro
Dual-processors Intel Xeon
RedHat 9.0 / Simplified Chinese locale (GB18030)
Gtk 2.2.1 (original from RH)
miniChinput, chinese input method, several versions were tested.
Steps to Reproduce:
1. Run a gtk example with two entry widgets
2. Switch focus, using the mouse, to a second widget while holding a key down
in the first
3. Without releasing key, keep switch the focus between the widgets
To be able to enter characteres on both widgets
Keyboard stops responding properly
This pretty much cause eclipse to stop working on Linux/zn_CH environments.
See eclipse bug:
I'm also submited a bug against GTK, it has more detailed steps and info, it
also contains an example testcase:
http://bugzilla.gnome.org/show_bug.cgi?id=123580Glen / Greg
Please open Redhat problem. Thanks
Pretty much positive this is a miniChinput bug; I put some debug statements
in and what GTK+ is sending to the input method looks fine.
And once you get miniChinput in the stuck state, the problem exists for
other processes as well ... even if GTK+ was buggy, it shouldn't be
able to cause such a problem.
(Just because it doesn't happen with other apps doesn't mean it isn't
a miniChinput bug ... GTK+ uses different parts of the XIM protocol
than many other apps.)
It seems a bug in XIM key event synchronization part, key events are cached not
getting thru. Using Dynamic Event flow model in IM server itself will fix the
The new package is here: http://people.redhat.com/yshao/miniChinput/
or Red Hat Rawhide.
------ Additional Comments From email@example.com 2003-31-10 12:11 -------
does the status FIXEDAWAITINGTEST mean that the Submitter has to verify (test)
the fix ?
------ Additional Comments From firstname.lastname@example.org 2003-25-11 22:27 -------
Yes, the bug submitter needs to verify the fix. Thanks.
------ Additional Comments From email@example.com 2003-26-11 11:32 -------
I verify that the original bug report in here is fixed.
But I can't say miniChinput is working 100% with Eclipse, it's not hard to get
in situations where it stops working but I don't have a concrete test cases to
reproduce the problem.
I tracked this down to Xlib bugs. Unfortunately, I haven't had
time to get write that up and propose fixes. I'll try to do that
Look at this pr:
My last comment has steps how to cause a failure situation.
I've tested this with GTK 2.4 and the latest miniChinput (from
fedora: 0.0.3-53) and bug still happens.
You just need to open the IM in a textentry and tab to a second
textentry. This causes the input method to stop working.
This is critical IMO.
----- Additional Comments From firstname.lastname@example.org 2004-04-22 15:42 -------
See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=57408#c7
For new steps on how to reproduce the bug.
Sorry for the late reply, could anyone have a look of
miniChinput-0.0.3-56 which has just been built, it should fix the
Where is miniChinput-0.0.3-56 available for download ?
Sorry, you can download from here
Or you can download it from Red Hat Rawhide which is available from
many mirror sites.
Does the miniChinput-0.0.3-56 works for you?
----- Additional Comments From email@example.com 2004-09-10 12:13 -------
Well, it does fix this one bug I mentioned. But miniChinput is far from been
stable, yesterday I was testing Eclipse 3.0.1 RC2 on Chinese and I had to
restart minichinput several times...
We are now in the transition phase to move away from Input Method such
as miniChinput which utilise the legacy X Input Method (XIM)
architecture. You may like to try out the new Simplified Chinese Input
Method by downloading the im-sdk and iiimf-le-chinput packages from
the Red Hat Rawhide. There is also a later version of miniChinput now
Hope this help.
Resolving this bug for now. Please reopen this bug if the problem for
miniChinput still persist.
For bugs related to iiimf-le-chinput, please file a New bug if it is
What |Removed |Added
------- Additional Comments From firstname.lastname@example.org 2005-07-11 18:16 EDT -------
Will close this based on comment #15 that it fixes the bug this was opened for.