Description of problem: SELinux is preventing gst-plugin-scan from 'execute' accesses on the file 2F686F6D652F787A6A3862332F2333383033393037202864656C6574656429. ***** Plugin catchall (100. confidence) suggests ************************** If si crede che gst-plugin-scan dovrebbe avere possibilità di accesso execute sui 2F686F6D652F787A6A3862332F2333383033393037202864656C6574656429 file in modo predefinito. Then si dovrebbe riportare il problema come bug. E' possibile generare un modulo di politica locale per consentire questo accesso. Do allow this access for now by executing: # ausearch -c 'gst-plugin-scan' --raw | audit2allow -M my-gstpluginscan # semodule -X 300 -i my-gstpluginscan.pp Additional Information: Source Context unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 Target Context unconfined_u:object_r:user_home_dir_t:s0 Target Objects 2F686F6D652F787A6A3862332F233338303339303720286465 6C6574656429 [ file ] Source gst-plugin-scan Source Path gst-plugin-scan Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-225.11.fc25.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.10.8-200.fc25.x86_64 #1 SMP Fri Mar 31 13:20:22 UTC 2017 x86_64 x86_64 Alert Count 1 First Seen 2017-04-12 22:23:17 CEST Last Seen 2017-04-12 22:23:17 CEST Local ID a1c4f62f-f3b2-4286-bf96-c1dbe235c56f Raw Audit Messages type=AVC msg=audit(1492028597.800:297): avc: denied { execute } for pid=5458 comm="gst-plugin-scan" path=2F686F6D652F787A6A3862332F2333383033393037202864656C6574656429 dev="sda2" ino=3803907 scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_dir_t:s0 tclass=file permissive=1 Hash: gst-plugin-scan,thumb_t,user_home_dir_t,file,execute Version-Release number of selected component: selinux-policy-3.13.1-225.11.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.10.8-200.fc25.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1442237 ***