Red Hat Bugzilla – Bug 123254
Keyboard layout switch key switches from prim to sec, but not back
Last modified: 2007-11-30 17:10:42 EST
Description of problem: Keyboard key combination, which is supposed to switch keyboard layouts does switch them, but only "one way". Suppose, 2 layouts are configured, and a key to switch between them is chosen in Control Center -- keyboard shortcuts. Suppose the primary layout is active. Then hitting the key once switches the keyboard to the secondary layout (as expected). Hitting the key once more doesn't switch the keyboard back to the primary layout (contrary to expectation and behavior in RedHat 8.0) Version-Release number of selected component (if applicable): kdebase v 3.1.4 release 6 How reproducible: See description Steps to Reproduce: 1. Start control center 2. Choose keyboard layout 3. Select any secondary layout (reproduced with 'ru') 4. Choose Keyboard Shortcuts 5. Choose a shortcut for Keyboard/Switch to Next Keyboard Layout (reproduced with Alt-Ctrl-K) 6. Close control center (after accepting changes) 7. Try the key, see failure to switch Actual results: The keyboard layouts do not form a ring, but rather a list, as far as switching between them is concerned. No switch from last layout to the first one Expected results: Switching from last layout to the first should be possible using the same key, as for switching from first to second. Additional info:
With bulgarian to workaround this I defined alternative switch key. The problem is that Alt-<en_key> becomes Alt-<bg_key> when switching to Bulgarian input, so I hat to add the Alt-<Bulgarian key> as alternative key... With Fedora core (even updated today) I have no keyboard layouts at all, so I can't select any.
The problem with the keyboard layouts is fixed long long ago, but the native kde keyboard switcher still requires two keys like Alt-<en_letter> and Alt-<bg_letter>. Now I use http://kkbswitch.sf.net/ and do configure my keyboard lauouts from XFree86/Xorg's config. Maybe kkbswitch is a good addition (nice flags...)?
This problem seems to be fixed in new upstream (3.2.3). It works fine for me.