Description of problem: I cannot change keyboard layout (Russian-English) in X (fluxbox) Version-Release number of selected component (if applicable): Fedora 10 release Steps to Reproduce: I can switch layot in virtual console but I cannot do it in fluxbox I have tried use xorg.conf from F9 Additional info: /etc/X11/xorg.conf Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "Protocol" "Standard" Option "XkbModel" "pc105" Option "XkbRules" "xorg" Option "XkbLayout" "us,ru" Option "XkbOptions" "grp:ctrl_shift_toggle,grp_led:scroll" Option "AutoRepeat" "250 30" Option "XkbOptions" "grp:shifts_toggle,grp_led:scroll" EndSection
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available) 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.
Created attachment 325960 [details] xorf.conf
Created attachment 325961 [details] Xorg.0.log
Done
Created attachment 326005 [details] xorg.conf I seem to be hitting the same issue. By default, the InputDevice section is being ignored. (Both xorg.conf and Xorg.0.log attached.)
Created attachment 326006 [details] Xorg.0.log
P.S. I've been using the same Xorg.conf since ~F2. (With minor changes along the way...) - Gilboa
Disabling AllowEmptyInput in the ServerFlags section, does enable non English keybaord - but at the expense of completely losing keyboard functionality - every keystroke in gdm is translated to 3 keys. (Some kind of raw mode?) Someone @xorg has completely lost it. - Gilboa
FYI: setxkbmap (xorg-x11-xkb-utils) still works, so it's possible to enable non-English keyboards by manually sending the following command: setxkbmap -layout "us,il" -option "grp:alt_shift_toggle,grp_led:scroll" - Gilboa
landgraf: what's the output of "setxkbmap -print"? The log file shows the options being recognized. (In reply to comment #8) > Disabling AllowEmptyInput in the ServerFlags section, does enable non English > keybaord - but at the expense of completely losing keyboard functionality - > every keystroke in gdm is translated to 3 keys. (Some kind of raw mode?) > > Someone @xorg has completely lost it. Please read http://who-t.blogspot.com/2008/10/new-keyboard-configuration-handling.html before you try options without knowing what they actually do.
> Please read > http://who-t.blogspot.com/2008/10/new-keyboard-configuration-handling.html > before you try options without knowing what they actually do. "If you disable AllowEmptyInput, AutoAddDevices or AutoEnableDevices, then you get the traditional X server behaviour: 1. Devices referenced in the ServerLayout are available in the server, or if none are specified, 2. The first pointer or keyboard device in the xorg.conf become available in the server, or if none are specified, 3. The standard configs become available (/dev/console and /dev/input/mice)." I want to disable the auto-configuration as I have a working xorg.conf. According to this documentation (and other documentation on the web) this is the only way to revert to the old manual configuration. What exactly did I do wrong? (In response to: "before you try options without knowing what they actually do") - Gilboa
OK. Now I saw it. "Update: If you are using evdev 2.1 and you only disable AllowEmptyInput, the devices will still be added and you will get duplicate events (key repeat handling will then make each key press emit three characters). AEI defaults to (AutoAddDevices && AutoEnableDevices), so if you want to disable HAL, the best option is to set AutoAddDevices to "off"." In my defense: A. This is the first time I saw anything documentation about AutoAddDevices. All other documentations talked about AllowEmptyInput and nothing else. B. Seems to me, that Xorg devs got it backwards, read: If a manual configuration present, Xorg should disable the automated configuration unless configured otherwise. ... Though, as annoying as it - this an upstream issue and not a Fedora problem. - Gilboa
In regards to these settings, I am upstream, basically. AEI sets whether the server forces default input devices, nothing more. AAD sets whether devices should be added to the server. If you disable AEI but not AAD, then you get all devices through HAL + the default devices - resulting in duplicate events. If you disable AAD, it implicitly also disables AEI because otherwise you may end up with no devices.
OK. I understand. Let explain the problem on my end. I had a working configuration. X.org got updated, and suddenly the configuration no long works. I look at the logs, and all I can see is: "AllowEmptyInput is on, devices using drivers 'kbd' or 'mouse' will be disabled." ... Nothing about AAD - only AEI. So I do a short google search about AEI, and finds that it may solve my problem. I try it, and all goes to hell. So, even if my view that automated detection should be disabled if a manual configuration is detected - is deemed unreasonable - the log files should be far more informative - especially given the fact that the man page doesn't say anything about device auto-detection. Either way, thanks for taking the time to answer my questions. - Gilboa
(In reply to comment #14) > So, even if my view that automated detection should be disabled if a manual > configuration is detected - is deemed unreasonable - the log files should be > far more informative - especially given the fact that the man page doesn't say > anything about device auto-detection. man xorg.conf describes the effects of AEI, AAD and AED in brief. If you think that description is inadequate, please provide a patch or at least the wording you believe is better (The log files are log files and shouldn't contain instructions). Better so even, please open a bug on bugs.freedesktop.org and participate in the process to get this issue resolved. CC me on the bugreport and note the bug number here too. Anyway, we're adding noise here to the original bugreport, so I'd prefer it if we could switch back to the issue reported in Comment #1.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
I try add Option "AllowEmptyInput" "false" Option "AutoAddDevices" "false" and Option "AutoEnableDevices" "false" in different vatiants. After start X I try turn off KDE layout switch )in "KDE settings"). Layout swatch work properly untill restart X and work properly in (Alt+F1, Alt+F2 * other console). After restart X keyboard switch doesn't work again (in virtual console (Alt+F1, Alt+F2) it works). I hat tried F11 Alpha, switching had worked properly after install (!!!) but until update only (yum update) :(.
UPD: If I start X with startx (from runlevel 3) keyboard layputs work properly! If I start X automaticaly (init 5) after logging It doen't work (use gdm).
Reassigning to gdm then.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Changing to F11. AAD and AED are still being ignored in both KDE and GNOME. - Gilboa
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Changing to F12. - Gilboa
Please close this bug. It's not actually in F13/14
Thank you for letting us know.