Bug 1265913

Summary: After update to 3.13.1-148 gdm stopped working - "Oh no! Something has gone wrong."
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bugzilla, dominick.grift, dwalsh, lvrabec, mgrepl, plautrba, robatino, ypossem
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-01 08:13:31 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:
Embargoed:
Attachments:
Description Flags
output of "ausearch -m avc,user_avc -ts recent"
none
Another ausearch -m avc,user_avc -ts recent none

Description piio 2015-09-24 07:15:51 UTC
Description of problem:
Ater update selinux-policy to 3.13.1-148, gdm doesn't list users, displays gnome-shell 'error occured' error.

Version-Release number of selected component (if applicable):
3.13.1-148

How reproducible:
Always

Steps to Reproduce:
1. Update selinux-policy to 3.13.1-148, reboot Fedora
2. See 'problem occured' in gdm screen
3.

Actual results:
Can't login through gdm to gnome-shell or another desktop.

Expected results:
Login through gdm to gnome-shell or another desktop

Additional info:
setenforce permissive and systemctl restart gdm makes gdm to work again.
I downgraded selinux-policy to 3.13.1-147

In logs I see only:
pam_systemd(sudo:session): Cannot create session: Already running in a session

Comment 1 York Possemiers 2015-09-25 00:53:41 UTC
This has happened to me too. Running fixfiles onboot does not fix this.

Comment 2 Miroslav Grepl 2015-09-25 07:52:52 UTC
Could you guys re-test it with permissive and after login 

# ausearch -m avc,user_avc -ts recent

to see if we can get any AVCs?

Comment 3 Andre Robatino 2015-09-26 03:16:56 UTC
Created attachment 1077309 [details]
output of "ausearch -m avc,user_avc -ts recent"

Comment 4 York Possemiers 2015-09-28 20:42:17 UTC
Created attachment 1078066 [details]
Another ausearch -m avc,user_avc -ts recent

I am aware someone has already posted one, but for comparison, I have also posted mine. Note that my install came with this issue, it was not bourne of an update.

Comment 5 York Possemiers 2015-10-01 00:36:25 UTC
Issue persists in 3.13.1-149 (did relabel again)

Comment 6 Miroslav Grepl 2015-10-01 08:13:31 UTC

*** This bug has been marked as a duplicate of bug 1267207 ***