Hide Forgot
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 Build Identifier: After locking the screen the keyboard layout of the last active application is active on the login screen, instead of switching to the last layout used on the login screen. IMHO the login screen is a separate window and should honor the configuration: Input Source Option: Allow different source for each window localectl status System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us,hu X11 Variant: ,101_qwerty_dot_nodead I am really not sure if xorg-x11 is the right component, please reassign, if not. Reproducible: Always Steps to Reproduce: Preconditions: 1. At least 2 input sources configured. 2. Input Source Option: Allow different source for each window enabled Steps: 1. Open two terminal windows. 2. Switch to the second keyboard layout while the second terminal window is active. 3. Lock screen -> Second keyboard layout is active on login screen. 4. Login, switch to first terminal window (keyboard layout switches to the first layout) 5. Lock screen -> First keyboard layout is active Actual Results: Keyboard layout of the last active window is active on the login screen. Switching keyboard layout on the login screen will switch the keyboard layout of the last active window before lock screen. Expected Results: The keyboard layout of the login screen should be handled separately of other windows. When locking the screen, the login screen should switch to the last keyboard layout used _on the login screen_.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.