Description of problem: I used to hit Alt + Shift to change the keyboard layout. But it's not working anymore in FC6. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
It also takes a lot of space to write the layout. It says ' us ' or 'ir prokeypad' There's no need to mention 'prokeypad'. There's just one version on ir layout.
(In reply to comment #1) > It also takes a lot of space to write the layout. It says ' us ' or 'ir > prokeypad' There's no need to mention 'prokeypad'. There's just one > version on ir layout. Sara, this should be reported as a separate bug.
(In reply to comment #0) > Description of problem: > I used to hit Alt + Shift to change the keyboard layout. But it's not working > anymore in FC6. The bug here is that when using Alt+Shift to change keyboard group, it worked in FC5 if you pressed and held Alt and then pressed Shift. Now in FC6, it only works if you press Shift first.
The reason its not working is because keyboard layout indicator crashes in FC6. look at bug #213163 for more details.
No, as I said it works if I press shift first, and then alt, but not the other way around.
This also affects the "Alt+Ctrl changes group" option, but not "Shift+Ctrl changes group". Since these are xkb layout options, this must be a server-side problem. Right ?
I do think it's unlikely to be a problem in xorg-x11-xtrans-devel ... reassigning to xkb
Fedora Core 6 is no longer supported, could you please reproduce this with the updated version of the currently supported distribution (Fedora 7, 8, or Rawhide)? If this issue turns out to still be reproducible, please let us know in this bug report. If after a month's time we have not heard back from you, we will have to close this bug as CANTFIX. Setting status to NEEDINFO, and awaiting information from the reporter. [This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or Gecko. If you see any other reason, why this bug shouldn't be closed, please, comment on it 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 reporter's distribution. 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 information. Closing as INSUFFICIENT_DATA. {This is mass-closing of all obsolete bugs; if this bug was in your opinion closed by mistake, please, reopen it with additional information; thanks a lot and I am sorry for bothering you in such case.}
This is fixed in F8.