Red Hat Bugzilla – Bug 608991
Key Down does not work (key sequence : eji6) after hitting space
Last modified: 2014-08-04 18:02:51 EDT
Description of problem:
When using Chinese Chewing of iBus in Gedit
Key Down does not work to select next candidate (key sequence : eji6) after hitting space
Version-Release number of selected component (if applicable):
RHEL Version:Red Hat Enterprise Linux Workstation release 6.0 Beta (Santiago)
Steps to Reproduce:
1. Open Gedit and turn iBus with Chinese Chewing on
2. Type eji6 then space to pop up other candidates characters.
3. After step2 following Key down(arrow down) pressing does not work.
Key down does nothing.
Hitting enter does not work till pressing a number key.
Key down(arrow down) shows next character.
Hitting enter should confirm the current character?
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
Please also post the result of:
gconftool-2 -a /desktop/ibus/engine/Chewing
Hi thanks 4 your help!
Here is information.
$ gconftool-2 -a /desktop/ibus/engine/Chewing
plainZhuyin = false
spaceAsSelection = true
escCleanAllBuf = false
inputStyle = in candidate window
syncCapsLockLocal = keyboard
forceLowercaseEnglish = false
selKeys = 1234567890
phraseChoiceRearward = true
easySymbolInput = true
candPerPage = 10
KBType = default
maxChiSymbolLen = 20
numpadAlwaysNumber = true
autoShiftCur = false
hsuSelKeyType = 1
addPhraseDirection = false
Fix is ready, yet need exception flags to be set as +
Is the fix already in Fedora?
From Jul 15 RHEL meeting:
STATUS: Update from jens. Worked with dchen to get it done but dchen
didn't follow process. It's in nightly.
STATUS: Tagged ibus-chewing-188.8.131.5200714-1.el6 for next Snapshot 8
STATUS: Changed status to MODIFIED.
Oh, just realize it is same thing that upstream issue 993 trying to address.
Basically, the default behaviors of down arrow in ibus-chewing are:
1) In editing mode (preedit buffer is not empty, candidate window is not shown),
open the candidate window.
2) In selection mode (candidate window is shown),
Show the candidate with different length.
Assuming the "Select for back" is on.
For example, when typing "gj bj4 z83" (輸入法),
Press down arrow first time will show the "輸入法" as candidate,
the second time will show the "法" and its homophone such as 髮、砝。
Thus. it is not really a bug.
Still, as the default behavior is not intuitive to new users,
I may need to do at least one of the followings:
1) Documentation on the keybindings/behaviors of ibus-chewing.
2) An option that enable the key binding that Kenichi Takemura and firstname.lastname@example.org
Documentations(release notes) should be updated regarding this key behaviours.
There is a flag requires_release_note for requesting relnotes.
Not sure why the bug state was reset?
(Currently we have not documented ibus hotkeys or shortcuts at all
in the relnotes - perhaps we should?)
Anyway, Ding-Yi: please describe the change in Technical Notes box, as requested by PM.
Ding-Yi: Any update regarding rel-note?
The usage and hot keys are documents in both README include in this package,
I checked the README of 'ibus-chewing-184.108.40.20600714-1.el6.i686'
But It does not seem to have appropriate descriptions about Key down like http://code.google.com/p/ibus/wiki/ChewingUserGuide(This is OK).
Can you tell me where the README location is?
$ rpm -q ibus-chewing
$ cat /usr/share/doc/ibus-chewing-220.127.116.1100714/README
It is a Chinese input engine for IBus.
It is released under GPLv2, see COPYING for detail.
See INSTALL for installation instruction.
Ah, I made a stupid mistake.
The file should be USER-GUIDE, not README.
I'll update README to reflect this change.
Can you produce an url to the file for QA?
Takemura-san, I think you have to make do with the URL above for now.
I understood. Thank you Ding-Yi and Jens for your support.
Moving this bug to VERIFIED.