Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: I have configured FC12 to use ibus and anthy for Japanese language input. When I run any Java application (e.g. jconsole), after the application window first opens, I can enter Japanese text just fine: After pressing Ctrl-Space, the ibus toolbar will pop up in the lower right part of the screen, and after entering some characters and pressing the space bar twice, the "box" with suggested Kanji completions will show up. Now, after I focus another window and then come back to the Java application, pressing Ctrl-Space will still activate the Kanji input mode and the keyboard works as expected, but neither the ibus toolbar nor the Kanji completions window show up any more. Clicking the ibus icon in the system tray brings up the message, "No input window". This problem is observed with any version of Java including the Fedora- provided java-1.6.0-openjdk as well as Sun's own 1.6.0_18 version (both 32 and 64-bit versions). It is not observed in any non-Java applications. Version-Release number of selected component (if applicable): anthy-9100h-10.fc12.x86_64 ibus-1.2.1-1.fc12.x86_64 ibus-anthy-1.2.0.20100115-1.fc12.x86_64 ibus-gtk-1.2.1-1.fc12.x86_64 ibus-libs-1.2.1-1.fc12.x86_64 ibus-table-1.2.0.20100111-1.fc12.noarch java-1.6.0-openjdk-1.6.0.0-36.b17.fc12.x86_64 java-1.6.0-openjdk-demo-1.6.0.0-36.b17.fc12.x86_64 java-1.6.0-openjdk-devel-1.6.0.0-36.b17.fc12.x86_64 java-1.6.0-openjdk-plugin-1.6.0.0-36.b17.fc12.x86_64 Steps to Reproduce: 1. Enable ibus via IM Chooser and configure it to use "Japanese - Anthy" input method. 2. Run jconsole from java-1.6.0-openjdk 3. Activate any text input field in the jconsole GUI, press Ctrl-Space. ibus toolbar will show up. Press Ctrl-Space again to switch back to "regular" input. 4. Focus another window, then come back to jconsole window. 5. Again press Ctrl-Space in any text input field. ibus toolbar will no more show up.
This is a bug in java. It does not set focus correctly. It will be fixed in next java update release around May, 2010.
Now, I'm not sure what was done to address this issue, but after my latest "yum update" run, I can no more reproduce this problem -- even when using Sun's JDK 1.6.0_18, the version in which I had certainly observed the problem at the time it was reported. It looks to me like some kind of fix/workaround was implemented outside of Java. So, from my perspective, the bug can be closed.
Yeah. I added some workaround code in ibus for this.
All right, thanks for caring.