Red Hat Bugzilla – Bug 398901
regressions in post-F8 rawhide gnome-keyboard-properties
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
I have set up US-international and BR-ABNT2 keyboard layouts, but I use
US-international with a Generic 105-key keyboard by default. Caps Lock is
configured as an additional Ctrl. Both Alt keys are supposed to switch between
layouts, and the Caps Lock led is supposed to indicate the alternate layout is
After F8, my rawhide-tracking box has severely regressed in these regards. Now
some regressions are fixed, but some still remain. The Alt keys don't switch
between layouts any more, Caps Lock doesn't indicate which layout is active any
more, and even though Caps Lock does work as an additional Ctrl key, it still
toggles the Caps Lock led, without effect on keyboard input.
Also, I can't select which is the default layout in the Keyboard Preferences ->
Layouts screen any more. I can move one layout before the other, but the
Default selector doesn't work at all.
Version-Release number of selected component (if applicable):
Caps lock works as control, but it still toggles the caps lock keyboard led,
which it shouldn't do if it's just another Ctrl.
Changing the keyboard repeat rate doesn't seem to have any effect.
The keystroke to switch layouts still doesn't work.
These are almost certainly not control-center issues, but problems in the
underlying X layers. Moving to a better component for further triage.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.