Bug 1368186

Summary: Login loop with SELinux policy set to enforced.
Product: [Fedora] Fedora Reporter: Eduardo Lima (Etrunko) <elima>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 24CC: rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-19 13:15:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
journalctl -u gdm after setenforce 0
none
journalctl -u gdm after setenforce 1 none

Description Eduardo Lima (Etrunko) 2016-08-18 15:19:09 UTC
Created attachment 1191907 [details]
journalctl -u gdm after setenforce 0

I am not sure what packages have been updated since the last time it worked, but I rebooted today and was caught in a login loop.

After some time investigating I found that probably there is some problem in gdm/pam related to SELinux with enforced policy. After running setenforce 0 gdm starts fine.

Comment 1 Eduardo Lima (Etrunko) 2016-08-18 15:19:58 UTC
Created attachment 1191908 [details]
journalctl -u gdm after setenforce 1

Comment 2 Eduardo Lima (Etrunko) 2016-08-19 13:15:00 UTC
Just updated my system today again, lots of packages from updates-testing repository, and gdm works again with setenforce 1. I will keep monitoring this issue and will reopen if necessary.