Description of problem: X sometimes fails to apply the wrong keyboard layout and randomly switches to the wrong one after returning from a KVM switch. See steps to reproduce. Version-Release number of selected component (if applicable): 1.14.5 How reproducible: Unreliable with a single KVM switch process, but quite reliable with a lot of switches (10 or so) In fact it happens so often that I need to learn to type with a German layout on an English keyboard to be able to use the KVM switch at all, and it hurts productivity quite a lot :-( Steps to Reproduce: 1. Use German laptop with German layout keyboard. Install system with default German layout. 2. Add optional English (US) layout e.g. in Gnome 3 settings 3. Plug in KVM switch with usb connector, plug US usb keyboard into switch 4. Set layout to English, e.g. with the gnome shell "en" selection in the top bar 4. Switch away and back to the laptop for a while. The other machine is a Microsoft Windows desktop (no idea if that is relevant) 5. After a few switches back to the laptop, suddenly the layout reverts to German. X log is littered with XKB errors. setxkbmap us fails. I can only type with a German layout on the attached US keyboard. Reproducible: Steps to Reproduce:
Created attachment 5141 [details] Xorg.0.log, see Could not invoke xbkcomp errors
Created attachment 5142 [details] xinput output while the bug is in effect
This happens with setxkbmap while the bug condition is in effect: jonas@Cyberman#15: setxkbmap -v 10 us Setting verbose level to 10 locale is C Warning! Multiple definitions of keyboard layout Using command line, ignoring X server Trying to load rules file ./rules/evdev... Trying to load rules file /usr/share/X11/xkb/rules/evdev... Success. Applied rules from evdev: rules: evdev model: pc105 layout: us options: compose:rwin Trying to build keymap using the following components: keycodes: evdev+aliases(qwerty) types: complete compat: complete symbols: pc+us+inet(evdev)+terminate(ctrl_alt_bksp)+compose(rwin) geometry: pc(pc105) Error loading new keyboard description jonas@Cyberman#15:
I got even as far as having a US layout on the built-in German keyboard of the laptop, but a German layout on the external US keyboard plugged in through the KVM switch. :-| I got a hint this may or may not be relevant: root@Cyberman#14: ls /proc/`pidof X`/fd | wc -l 55 root@Cyberman#14: Oh and a reboot fixes the problem, at least last time I had this. (I'm right now trying to collect a bit of data while it is active)
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. 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 Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD