From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030206 Description of problem: Using kcontrol to configure multiple keyboard layouts. Country is Greece OR Netherlands OR Sweden, primary language is English US, secondary language is Greek OR none, keyboard is 101 or 104 keys (tested all possible combinations of the above); these settings make no difference whatsoever for the following. With X, Y and US English (us) keyboards defined and US English as the default, switching from US to X or Y works fine. Switching from X or Y back to US doesn't work at all and leaves the previously set keyboard active (i,e. you switch from Greek to US and you still have Greek). Logging out and back in makes no difference. Logging out and back in on "KDE" instead of "default", in an attempt to force new defaults, makes no difference either. The *only* way to restore the US keyboard is to use kcontrol to remove all other keyboard definitions, leaving only US English. I tried several different combinations of X and Y (Greek, Arabic, Georgian, Thai) and the problem is always the same. Trying to type on the command line and getting Greek is a tad frustrating. With X, Y and US English w/deadkeys (instead of US English) keyboards defined, the problem disappears. Switching works perfectly from any definition to any, even without closing applications, let alone logging out. It just works as it should. Thus, I assume that something is broken in the US English keyboard definition. Version-Release number of selected component (if applicable): kdebase-3.1-7 & kdebase-3.1-9 Additional info: Did not try US w/deadkeys with kdebase-3.1-7; I had already upgraded when I got the idea of trying a different US keyboard definition than US English.
This bug is reported against old release of Red Hat Linux or Fedora Core that is no longer supported. Chances are that it has been already fixed in newer Fedora Core release. If you still experience the problem with current release of Fedora Core, please update the Version field (you may need to switch Product to Fedora Core first) in the bug report and put it back to NEW state.
I just tested it on Cent^wRHEL 4.3. The problem has gone away.