Description of problem: SELinux is preventing plymouthd from 'map' accesses on the chr_file /dev/fb0. ***** Plugin catchall (100. confidence) suggests ************************** If si crede che plymouthd dovrebbe avere possibilità di accesso map sui fb0 chr_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 'plymouthd' --raw | audit2allow -M my-plymouthd # semodule -X 300 -i my-plymouthd.pp Additional Information: Source Context system_u:system_r:plymouthd_t:s0 Target Context system_u:object_r:framebuf_device_t:s0 Target Objects /dev/fb0 [ chr_file ] Source plymouthd Source Path plymouthd Port <Sconosciuto> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-270.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.13.0-0.rc4.git4.1.fc27.x86_64 #1 SMP Fri Aug 11 15:03:46 UTC 2017 x86_64 x86_64 Alert Count 88 First Seen 2017-08-13 13:21:30 CEST Last Seen 2017-08-15 22:33:15 CEST Local ID 92622f60-4b4b-4eee-b230-0bebb9add3de Raw Audit Messages type=AVC msg=audit(1502829195.581:2075): avc: denied { map } for pid=5126 comm="plymouthd" path="/dev/fb0" dev="devtmpfs" ino=11430 scontext=system_u:system_r:plymouthd_t:s0 tcontext=system_u:object_r:framebuf_device_t:s0 tclass=chr_file permissive=0 Hash: plymouthd,plymouthd_t,framebuf_device_t,chr_file,map Version-Release number of selected component: selinux-policy-3.13.1-270.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.13.0-0.rc4.git4.1.fc27.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1517405 ***