Description of problem: Pressing a CapsLock button doesn't display a warning in GDM that CapsLock button is pressed. Version-Release number of selected component (if applicable): gdm 3.22.1.1.fc25 How reproducible: Always Steps to Reproduce: 1. Log in to the Wayland session, 2. Lock the laptop, 3. Start typing the password to log in back and press before or during the password input, the CapsLock button. Actual results: The warning (symbolic icon representing ! sign in the input field widget) isn't displayed. Expected results: A warning that the CapsLock button is presses should appear. Additional info: I haven't tested if this is the case when the OS is booted for the first time. This certainly happens when already logged in.
I just did a fresh boot. Pressing CapsLock when entering password for a user doesn't show a warning that the CapsLock is pressed.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 is still happening on Fedora 27
*** This bug has been marked as a duplicate of bug 1398724 ***