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 1540323
Summary: | SELinux is preventing acpid from 'read' accesses on the chr_file event30. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Raman Gupta <rocketraman> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | dwalsh, lvrabec, mgrepl, plautrba, pmoore |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:352b07c5c13d27464c46dc3d757ed23e5e0f6c3056b8d6ee00322818822d2581; | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-02-28 16:35:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Raman Gupta
2018-01-30 19:04:30 UTC
Hi, Could you please run: #restorecon -Rv /dev/ To fix your issue? Thanks, Lukas. (In reply to Lukas Vrabec from comment #1) > Hi, > > Could you please run: > > #restorecon -Rv /dev/ Hmm, why is the file in question (event30) not being relabeled? It seems as if this is not going to fix the problem... # restorecon -Rv /dev/ Relabeled /dev/vboxusb/005/077 from system_u:object_r:device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/076 from system_u:object_r:device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/075 from system_u:object_r:device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/004 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/009 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/008 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/005/002 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/007/002 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/001/003 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Relabeled /dev/vboxusb/001/002 from system_u:object_r:usb_device_t:s0 to system_u:object_r:xserver_misc_device_t:s0 Re-opening. This is still happening after running the recommended restorecon command. *** This bug has been marked as a duplicate of bug 1547139 *** |