Description of problem: The gnome lock screen does not recognize a user password to unlock. Version-Release number of selected component (if applicable): Latest / FC24 How reproducible: Steps to Reproduce: 1. Clean iso install of FC24 server / headless 2. Full update 3. dnf groupinstall gnome 4. systemctl to enable/start gdm service 5. log in to gnome (at this point, it fails to recognize the return key after typing in the password. you must click on the button) 6. engage lock screen at gnome desktop 7. try to unlock with valid password (no capslock, 100% correct user pw) Actual results: Hangs/does not unlock - kept hitting escape to re-enter and try again - no luck. Expected results: Should unlock - tried many times. Eventually disabled lock screen as the only way to fix it...and still couldn't log in to gnome by hitting return key. In addition to lock screen failure, the return key should work as default submit for pw popup. Additional info: Hardware Configuration: MB: ASUS B150M-A D3 (new) CPU: Pentium G4400 / 3.3Ghz (New) RAM: 8gb (2gbx4 DDR3-1600) (New) Primary Drive: WD 1TB Blue (New) RocketRaid 620, bios 1.3 (passive PCI - no driver loaded after install - had to patch, compile and load after the fact - didn't change anything)
per Adam W., I ran dnf install @workstation-product-environment (and rebooted just to make sure). Note that dnf group list -v environment returns nothing found in the repos. 1. Logged into gnome classic (return key still doesn't work - have to click the button) 2. Re-enabled the lock screen and set to activate at 30 seconds. After waiting 2 minutes, I learned that besides the pw not working, the lock screen timer is also broken. 3. Set to engage when screen went to sleep and waited for sleep. zzzz 4. Woke up machine and could not unlock, as before, no matter what I tried. I clicked on "log in as a different user" and it took me back to the main graphical login menu, where I clicked on the same user account, which then showed me a dialog to "unlock" with the user pw. And again, the return key does not work to drive input. Presumably, if I had another account to choose, it would show me a login dialog rather than an unlock dialog. It seemed to remember the lock state of the user who had been locked out. I wonder if it would save that state if I logged in and logged out as another user? (beyond scope of this bug, but an interesting QA test). So...not fixed by workstation-product-environment + other problems (return key and lock screen timers not working). Going back to KDE/plasma (which does not have these problems).
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.