Bug 1889521 - gdm won't log in after selinux policy change in upgrade
Summary: gdm won't log in after selinux policy change in upgrade
Status: CLOSED DUPLICATE of bug 1886196
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-19 20:31 UTC by George White
Modified: 2020-10-20 07:00 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-20 07:00:58 UTC
Type: Bug

Attachments (Terms of Use)
Output of `ausearch -c gdm-session-wor` (1012 bytes, text/plain)
2020-10-19 20:31 UTC, George White
no flags Details

Description George White 2020-10-19 20:31:46 UTC
Created attachment 1722702 [details]
Output of `ausearch -c gdm-session-wor`

Description of problem:
After running dnf upgrade, gdm would no longer log in any user for any session. Audit messages are printed to the journal which show gdm is being denied access to its own scripts.

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

How reproducible:

Steps to Reproduce:
1. Power on machine.
2. Boot to gdm.
3. Attempt to log in to either GNOME, GNOME Classic, GNOME on Xorg session types with a valid user and password combination.

Actual results:
gdm returns the user to the user selection screen

Expected results:
The GNOME desktop starts.

Additional info:
Attached is the output of `ausearch -c gdm-session-wor`.

Comment 1 George White 2020-10-19 20:34:00 UTC
Passing these audit messages to audit2allow, then adding the allow stanzas to the system policy resolves the issue.

Comment 2 Zdenek Pytela 2020-10-20 07:00:58 UTC

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

Note You need to log in before you can comment on or make changes to this bug.