RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2082887 - selinux-policy > 34.1.25-1.el9 breaks plasma desktop
Summary: selinux-policy > 34.1.25-1.el9 breaks plasma desktop
Keywords:
Status: CLOSED DUPLICATE of bug 2058657
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: CentOS Stream
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Zdenek Pytela
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-08 08:18 UTC by Gordan Bobic
Modified: 2022-07-07 09:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-09 07:04:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 2058657 1 unspecified CLOSED latest selinux-policy blocks KDE Plasma Desktop from starting 2022-07-12 15:12:32 UTC
Red Hat Issue Tracker RHELPLAN-121331 0 None None None 2022-05-08 08:28:10 UTC

Description Gordan Bobic 2022-05-08 08:18:02 UTC
Description of problem:
With selinux-policy-34.1.25-1.el9, everything works fine, login works and the desktop shows up.

As soon as selinux-policy is upgraded beyond that version, login screen shows up, but after entering the password, only a black screen shows up forever. No KDE loading animation, just a black screen.

Version-Release number of selected component (if applicable):
34.1.25-1.el9 works
34.1.26-1.el9 is broken.

How reproducible:
Every time. Install later selinux-policy, and it breaks. Downgrade back to 34.1.25-1 and it works again.

Steps to Reproduce:
1. Install plasma-workspace
2. On login screen select Plasma (X11)
3. With selinux-policy 34.1.25 it works, with later versions login never completes.

Actual results:
Black screen, no KDE loading splash screen, no desktop.

Expected results:
Login should complete and lead to a working desktop.

Comment 1 Gordan Bobic 2022-05-08 08:35:32 UTC
Possibly a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2058657

Comment 2 Milos Malik 2022-05-08 09:44:15 UTC
In order to find out what exactly is the cause, we need to see SELinux denials that are triggered in enforcing and permissive mode.

Please collect SELinux denials and attach them to this BZ:

# ausearch -m avc -m user_avc -m selinux_err -i -ts today

Thank you.

Comment 3 Gordan Bobic 2022-05-08 10:06:44 UTC
I have been able to confirm - this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2058657

Comment 4 Zdenek Pytela 2022-05-09 07:04:23 UTC

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


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