Description of problem: Triggered by crash of Wesnoth game SELinux is preventing gdb from using the 'sys_admin' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should have the sys_admin capability 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:system_r:abrt_t:s0-s0:c0.c1023 Target Objects Unknown [ capability ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-37.17-1.fc37.noarch Local Policy RPM selinux-policy-targeted-37.17-1.fc37.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.0.18-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Jan 7 17:10:00 UTC 2023 x86_64 x86_64 Alert Count 2 First Seen 2023-01-14 18:26:17 MST Last Seen 2023-01-14 18:26:17 MST Local ID 59a920c2-28df-42e2-9a65-c8848c5a4f36 Raw Audit Messages type=AVC msg=audit(1673745977.202:501): avc: denied { sys_admin } for pid=4778 comm="gdb" capability=21 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tclass=capability permissive=0 Hash: gdb,abrt_t,abrt_t,capability,sys_admin Version-Release number of selected component: selinux-policy-targeted-37.17-1.fc37.noarch Additional info: component: selinux-policy reporter: libreport-2.17.4 hashmarkername: setroubleshoot kernel: 6.0.18-300.fc37.x86_64 type: libreport Potential duplicate: bug 1897863
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. *** This bug has been marked as a duplicate of bug 1897863 ***