Bug 1368186 - Login loop with SELinux policy set to enforced.
Summary: Login loop with SELinux policy set to enforced.
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 24
Hardware: Unspecified
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-18 15:19 UTC by Eduardo Lima (Etrunko)
Modified: 2016-08-19 13:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-19 13:15:00 UTC
Type: Bug

Attachments (Terms of Use)
journalctl -u gdm after setenforce 0 (32.62 KB, text/plain)
2016-08-18 15:19 UTC, Eduardo Lima (Etrunko) 		no flags Details
journalctl -u gdm after setenforce 1 (449.22 KB, text/plain)
2016-08-18 15:19 UTC, Eduardo Lima (Etrunko) 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.