Description of problem: After disconnecting the keyboard and then reconnecting the keyboard, the layout of the Russian keyboard changes. Steps to Reproduce: 1. Add the Russian keyboard layout (not any of the alternatives, just normal Russian), and switch to it 2. Check that the actual layout matches the one that is shown in the window when pressing the Eye-button 3. Disconnect the keyboard, and reconnect it 4. The Russian keyboard layout is now not matching the layout shown in the window when pressing the Eye-button Actual results: The keyboard layout doesn't match the one in the window when clicking the eye-icon. An easy way to test this is that the letter "ю" is now on the key above Tab, left to 1, below Esc; and the key to the left of Right Shift is "ё". Expected results: The keyboard layout matches the one in the window when clicking the eye-icon. An easy way to test this is that the letter "ё" is now on the key above Tab, left to 1, below Esc; and the key to the left of Right Shift is ".". Additional info: I find this problem hard to explain, as I don't know the technical details of the different Russian language keyboard layouts. I primarily use the Norwegian keyboard layout, and the Russian one for learning. The fix right now is to remove and add the keyboard layout whenever I notice it's not the correct. After changing to the desired keyboard layout, this is the output of setxkbmap -print: xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+no+ru:2+us:3+inet(evdev)+level3(ralt_switch)" }; xkb_geometry { include "pc(pc105)" }; }; After disconnecting keyboard, the output stays the same (sleep 5 && setxkbmap -print): xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+no+ru:2+us:3+inet(evdev)+level3(ralt_switch)" }; xkb_geometry { include "pc(pc105)" }; }; After reconnecting the keybaord, the output changes to: xkb_keymap { xkb_keycodes { include "evdev+aliases(qwerty)" }; xkb_types { include "complete" }; xkb_compat { include "complete" }; xkb_symbols { include "pc+no+ru(typewriter):2+inet(evdev)" }; xkb_geometry { include "pc(pc105)" }; };
I realized that this is not happening on reboot! I will update the description and title. The problem arises when disconnecting and reconnecting the keyboard. The last few weeks, as well as upgrading Fedora, I have started working from home. Because of this, I disconnect and reconnect the keyboard to and from my Fedora-box, because I can not (sadly) use it for work.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 EOL if it remains open with a Fedora 'version' of '33'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.