Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1645914 - SELinux is preventing systemd-user-ru from read access on the directory dbus-1
Summary: SELinux is preventing systemd-user-ru from read access on the directory dbus-1
Keywords:
Status: CLOSED DUPLICATE of bug 1644313
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 29
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-04 20:16 UTC by Chrit van Ewijk
Modified: 2018-11-04 20:20 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-04 20:20:28 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
The e-mail text of the SElinux alert message destined for the administrator (1.88 KB, text/plain)
2018-11-04 20:16 UTC, Chrit van Ewijk 		no flags Details
View All

Description Chrit van Ewijk 2018-11-04 20:16:13 UTC 
Created attachment 1501474 [details]
The e-mail text of the SElinux alert message destined for the  administrator

Description of problem:
I get repeatedly (at least the last 4 times) the same SELinux alert message at boot time. See attachment for the message text. Before i upgraded to F29 last week i did not get those alerts. I used "sudo dnf system-upgrade download --releasever=29" .


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


How reproducible: At every boot i get this same alert. I ignore it, I do not notice any further problems while working at my PC.


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Lukas Vrabec 2018-11-04 20:20:28 UTC 

*** This bug has been marked as a duplicate of bug 1644313 ***
Note You need to log in before you can comment on or make changes to this bug.