Description of problem: SELinux is preventing upowerd from 'rename' accesses on the file history-rate-Sony_Interactive_Entertainment_Wireless_Controller-f4:93:9f:56:03:cb.dat.I1KBMZ. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that upowerd should be allowed rename access on the history-rate-Sony_Interactive_Entertainment_Wireless_Controller-f4:93:9f:56:03:cb.dat.I1KBMZ 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 'upowerd' --raw | audit2allow -M my-upowerd # semodule -X 300 -i my-upowerd.pp Additional Information: Source Context system_u:system_r:init_t:s0 Target Context system_u:object_r:devicekit_var_lib_t:s0 Target Objects history-rate-Sony_Interactive_Entertainment_Wirele ss_Controller-f4:93:9f:56:03:cb.dat.I1KBMZ [ file ] Source upowerd Source Path upowerd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.2-26.fc29.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Permissive Host Name (removed) Platform Linux (removed) 4.18.0-0.rc0.git9.1.fc29.x86_64 #1 SMP Thu Jun 14 18:07:49 UTC 2018 x86_64 x86_64 Alert Count 1 First Seen 2018-07-11 08:41:20 +05 Last Seen 2018-07-11 08:41:20 +05 Local ID 1ca280f3-1e46-4146-814a-a87ef6bab683 Raw Audit Messages type=AVC msg=audit(1531280480.730:502): avc: denied { rename } for pid=1278 comm="upowerd" name="history-rate-Sony_Interactive_Entertainment_Wireless_Controller-f4:93:9f:56:03:cb.dat.I1KBMZ" dev="sdc1" ino=6160472 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:devicekit_var_lib_t:s0 tclass=file permissive=1 Hash: upowerd,init_t,devicekit_var_lib_t,file,rename Version-Release number of selected component: selinux-policy-3.14.2-26.fc29.noarch Additional info: component: selinux-policy reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.18.0-0.rc4.git3.1.local.fc29.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1600718 ***