Bug 21914

Summary: Unable to log in using LightDM when /run/nologin present
Product: Mageia Reporter: Stig-Ørjan Smelror <smelror>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Normal CC: jani.valimaa
Version: 6   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:
Attachments: ls --full-time /run/nologin
Journal after boot with nologin present

Description Stig-Ørjan Smelror 2017-10-22 12:59:06 CEST
Hi.

Experienced this just now and LightDM showed a message about incorrect password.

I saw the error when I Ctrl-Alt-F2 and tried to log in on the console and saw the message about "Machine booting".

Had to log in as root and delete /run/nologin before I was able to proceed.
I forgot to run tests on the file before I removed it. Sorry about that.

Cheers,
Stig
Comment 1 Jani Välimaa 2017-10-22 14:17:18 CEST
I'd say that it's not a bug. Lightdm uses pam_nologin module. See 'man pam_nologin'.

CC: (none) => jani.valimaa

Comment 2 Stig-Ørjan Smelror 2017-10-22 14:36:03 CEST
Thanks Jani.

I thought I'd be able to log in locally even though /run/nologin was present and that it was meant for remote logins. Guess I was wrong.

But, I was able to log in when I used SDDM... Maybe it's "broken"...


Cheers,
Stig
Comment 3 Stig-Ørjan Smelror 2017-10-22 14:37:03 CEST
Created attachment 9745 [details]
ls --full-time /run/nologin
Comment 4 Stig-Ørjan Smelror 2017-10-22 14:37:46 CEST
Created attachment 9746 [details]
Journal after boot with nologin present
Comment 5 Jani Välimaa 2017-10-22 14:42:47 CEST
(In reply to Stig-Ørjan Smelror from comment #2)
> Thanks Jani.
> 
> I thought I'd be able to log in locally even though /run/nologin was present
> and that it was meant for remote logins. Guess I was wrong.
> 
> But, I was able to log in when I used SDDM... Maybe it's "broken"...
> 

sddm doesn't use pam_nologin.so. See files under /etc/pam.d/.
Comment 6 Jani Välimaa 2017-10-22 14:43:58 CEST
I'm closing this as INVALID.

Resolution: (none) => INVALID
Status: NEW => RESOLVED