Description of problem: 1) Run Apper 2) Select all updates to install 3) Start installation process...walk away as the 433 packeages install (F24 - so as to be expected there are a few to do...frequently) 5) Check progress later and see that SELinux has blocked mkdir on / How to reproduce? Not sure, other than to try to reinstall any availalbe updates and see if it happens again... SELinux is preventing mkdir from 'write' accesses on the directory /. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mkdir should be allowed write access on the directory 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 mkdir --raw | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:system_mail_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects / [ dir ] Source mkdir Source Path mkdir Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-158.12.fc23.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 Alert Count 1 First Seen 2016-04-14 22:43:33 PDT Last Seen 2016-04-14 22:43:33 PDT Local ID 7b660059-6611-4780-b731-b7ed596216fc Raw Audit Messages type=AVC msg=audit(1460699013.865:1597): avc: denied { write } for pid=12689 comm="mkdir" name="/" dev="dm-1" ino=2 scontext=system_u:system_r:system_mail_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir permissive=0 Hash: mkdir,system_mail_t,root_t,dir,write Version-Release number of selected component: selinux-policy-3.13.1-158.12.fc23.noarch Additional info: reporter: libreport-2.7.0 hashmarkername: setroubleshoot kernel: 4.5.2-302.fc24.x86_64 reproducible: Not sure how to reproduce the problem type: libreport Potential duplicate: bug 1046468
*** This bug has been marked as a duplicate of bug 1046468 ***