Description of problem: After wake from sleep today, i am unable to unlock the gnome session. The unlock screen accepts the password but on pressing the enter shows some auth error and gives back the password entry dialog. The behavior looks similar to https://bugzilla.redhat.com/show_bug.cgi?id=1002464 except Ctrl+Alt+F2 and back to Ctrl+Alt+F1 still doesn't help. I am able to normally log into consoles, and even start a different X session with openbox from where i am entering this report. journalctl shows following log which might be relevant: Dec 22 12:17:24 pankajlaptop gdm-password][22341]: pam_unix(gdm-password:auth): conversation failed Dec 22 12:17:24 pankajlaptop gdm-password][22341]: pam_unix(gdm-password:auth): auth could not identify password for [pankaj] Dec 22 12:17:24 pankajlaptop gdm-password][22341]: gkr-pam: no password is available for user Version-Release number of selected component (if applicable): gdm-3.10.0.1-1.fc20.x86_64 gnome-shell-3.10.2.1-3.fc20.x86_64 systemd-208-9.fc20.x86_64 How reproducible: No idea, i have previously been able to lock/unlock the session without any issues. Actual results: Unlock screen password entry prompt reappears Expected results: Gnome session should unlock Additional info: A quick google search returned https://bbs.archlinux.org/viewtopic.php?id=162856 , where people say updating/reinstalling arbitrary packages (libpng, librsvg ...), fixed their problem, but i'm skeptical
I could get back my session by killing gnome-session (it automatically died when i started gnome-session i display :1) and replacing it with openbox. When i tried to replace back openbox with gnome-shell, it went back to the unlock screen and again wouldn't accept my login attempts.
I need to kill gnome-shell frequently because it hangs every time the screen locks due to a bug with gnome-settings-daemon. Sometimes after I restart gnome-shell it gets stuck in this situation and I end up having to kill my session. I get the same log messages as the reporter. One further odd thing is that the next log message is: gdm-password]: gkr-pam: unlocked login keyring What??
A temporary workaround is to switch to a console and force unlock the screen from the command line: export DISPLAY=:0 dbus-send --type=method_call --print-reply --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.SetActive boolean:false You will have to do this every time the screen locks until you restart your session. I put that line into a file so I could easily run it.
I suspect an issue with gdm-session-worker as there seems to be another process every time I try to unlock with a password and they don't go away. I traced it with strace and it tries checking the right password, but then it appears to try again with an empty password which of course doesn't work. The first two log messages come from the PAM library, but I haven't yet been able to find out which process they are coming from.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
This is reproducible on Fedora 21 with gdm-3.14.2-1.fc21.x86_64. Reopening. I'm getting the exact same error messages in journal.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.