Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): How reproducible: repeatedly Steps to Reproduce: 1. start vnc 2. AVC pops up 3. Actual results: expect vnc to start without error vnc not registering as started but in fact is listening Expected results: expect vnc to start without error Additional info: SELinux is preventing systemd from unlink access on the file backrow:1.pid. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd should be allowed unlink access on the backrow:1.pid 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 'systemd' --raw | audit2allow -M my-systemd # semodule -X 300 -i my-systemd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:user_home_t:s0 Target Objects backrow:1.pid [ file ] Source systemd Source Path systemd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux backrow 4.7.2-201.fc24.i686+PAE #1 SMP Fri Aug 26 16:23:32 UTC 2016 i686 i686 Alert Count 1 First Seen 2016-09-12 12:45:02 EDT Last Seen 2016-09-12 12:45:02 EDT Local ID c683f460-7434-4401-9e20-db6324cbd812 Raw Audit Messages type=AVC msg=audit(1473698702.255:364): avc: denied { unlink } for pid=1 comm="systemd" name="backrow:1.pid" dev="dm-7" ino=2621479 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:user_home_t:s0 tclass=file permissive=0 Hash: systemd,init_t,user_home_t,file,unlink
Apparently no one wants to look at this