Sometimes, not always, when I come back to my F20 computer after a while, I can't unlock gnome-shell's lockscreen/shield. This message is very briefly shown after entering the password, before a "sorry, that didn't work": "System is booting up. See pam_nologin(8)" If I switch to a tty with ctrl+alt+1/2/3/etc, as soon as I strike a key I'm thrown back to the graphical lockscreen. Trying to SSH into the machine yields the exact same message: "System is booting up. See pam_nologin(8)" This is bullsh.. My system ain't in the process of "booting up".
Oh and I meant ctrl+alt+F1/F2/F3/etc. selinux is disabled, firewalld is not installed, etc.
Hm... Can you post some logs (journalctl output) from around when this happens?
That's the tricky/ugly part... when it happens I can't get any such information, because I am not allowed to login, either graphically, in a virtual terminal or remotely through SSH :(
You can (temporarily) remove pam_nologin from pam configuration. Something like sudo sed -i -r 's/^(.*pam_nologin.so)/#\1/' /etc/pam.d/sshd should do the job. Then you should be able to log in over ssh.
*** This bug has been marked as a duplicate of bug 1043212 ***
I'm having the same exact issue as everyone else. I installed Fedora 20 from the ISO I downloaded from your website. I didn't update or anything for months. I never had the issue. Today I updated all my software via terminal "yum update" and now I'm having "System is booting up. See "pam_nologin(8)"." This only happens due to being idle and the screen locking. This is a huge issue for me because I use Fedora 20 mainly for security. I have very private protected health information and have to abide by HIPAA standards. The only work around I could find (which really isn't a work around) is to "turn off" screen lock in privacy settings. This is a huge issue for me since I NEED to lock my screen due to information stored on the computer. The only way to get past the message is to manually power off the computer and log back in. So for now I'm leaving the computer powered off until there's a fix or might possibly look at other distributions.
Hytekk, you're commenting on a duplicate. The problem is being investigated (and on its way to being solved) in bug 1043212 (there are also some workarounds there, but I haven't experienced the issue since January so I don't need them)