Description of problem: SELinux is preventing gdb from 'open' accesses on the chr_file /dev/fb0. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed open access on the fb0 chr_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 'gdb' --raw | audit2allow -M my-gdb # semodule -X 300 -i my-gdb.pp Additional Information: Source Context system_u:system_r:abrt_t:s0-s0:c0.c1023 Target Context system_u:object_r:framebuf_device_t:s0 Target Objects /dev/fb0 [ chr_file ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-37.15-1.fc37.noarch Local Policy RPM selinux-policy-targeted-37.15-1.fc37.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.0.10-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 26 16:55:13 UTC 2022 x86_64 x86_64 Alert Count 1 First Seen 2022-12-04 21:46:14 WET Last Seen 2022-12-04 21:46:14 WET Local ID d3eab843-b38e-47e1-ad57-523208fc7b07 Raw Audit Messages type=AVC msg=audit(1670190374.671:320): avc: denied { open } for pid=11745 comm="gdb" path="/dev/fb0" dev="devtmpfs" ino=479 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:framebuf_device_t:s0 tclass=chr_file permissive=0 Hash: gdb,abrt_t,framebuf_device_t,chr_file,open Version-Release number of selected component: selinux-policy-targeted-37.15-1.fc37.noarch Additional info: component: selinux-policy reporter: libreport-2.17.4 hashmarkername: setroubleshoot kernel: 6.0.10-300.fc37.x86_64 type: libreport Potential duplicate: bug 2103410
It is required to turn this boolean on to allow abrt execute its gdb handler and be able to troubleshoot further: # setsebool -P abrt_handle_event on and subsequently report another bug for the affected component. Refer to abrt_handle_event_selinux(8) for more information. Closing as dup of bz#1896648. *** This bug has been marked as a duplicate of bug 1896648 ***