I got the following SElinux alert:
SELinux is preventing (ostnamed) from mounton access on the file /proc/mtrr.
***** Plugin catchall (100. confidence) suggests **************************
If you believe that (ostnamed) should be allowed mounton access on the
mtrr file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c '(ostnamed)' --raw | audit2allow -M my-ostnamed
# semodule -X 300 -i my-ostnamed.pp
Additional Information:
Source Context system_u:system_r:init_t:s0
Target Context system_u:object_r:mtrr_device_t:s0
Target Objects /proc/mtrr [ file ]
Source (ostnamed)
Source Path (ostnamed)
Port <Unknown>
Host phaeotrone
Source RPM Packages
Target RPM Packages
Policy RPM selinux-policy-3.13.1-244.fc27.noarch
Selinux Enabled True
Policy Type targeted
Enforcing Mode Permissive
Host Name phaeotrone
Platform Linux phaeotrone
4.11.0-0.rc2.git1.1.fc27.x86_64
#1 SMP Tue Mar 14 15:33:03 UTC 2017
x86_64 x86_64
Alert Count 4
First Seen 2017-03-16 19:42:59 CET
Last Seen 2017-03-17 02:05:18 CET
Local ID 44a99dd1-0388-4171-892f-7fe2596f7ec7
Raw Audit Messages
type=AVC msg=audit(1489712718.826:127): avc: denied { mounton } for
pid=813 comm="(ostnamed)" path="/proc/mtrr" dev="proc" ino=4026531961
scontext=system_u:system_r:init_t:s0
tcontext=system_u:object_r:mtrr_device_t:s0 tclass=file permissive=1
Hash: (ostnamed),init_t,mtrr_device_t,file,mounton
However, even disabling SElinux followed by reboot didn't help ...
On 3/17/17 1:27 AM, Adam Williamson wrote:
On Fri, 2017-03-17 at 01:21 +0100, GERHARD GOETZHABER wrote:
What's this? Recently I set up both Rawhide branches for new (on Xfce
either since KDE has become nothing more than a tragedy and therefore is
given up by me), finally keeping fc27 because the latter one seems to
simply be the very better system. Though it was real hard work to
integrate all codecs into fc27 by hand the efficiency overall appears
great - except only LibreOffice: Crazy! Whenever one of the suite's
parts is called by file or the software itself only the intro shortly
lights up followed by just nothing else. Not even an oops, however.
I wonder why nobody else has complained that phenomenon ...
Runs fine here.
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
