Description of problem: SELinux is preventing gdb from 'read' accesses on the chr_file renderD128. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the renderD128 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:dri_device_t:s0 Target Objects renderD128 [ chr_file ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.20-1.fc38.noarch Local Policy RPM selinux-policy-targeted-38.20-1.fc38.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.3.12-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jul 6 04:05:18 UTC 2023 x86_64 Alert Count 1 First Seen 2023-07-08 20:30:33 IST Last Seen 2023-07-08 20:30:33 IST Local ID 650f4d3f-30d0-4579-a79b-040bdd33688f Raw Audit Messages type=AVC msg=audit(1688828433.578:350): avc: denied { read } for pid=31888 comm="gdb" name="renderD128" dev="devtmpfs" ino=734 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dri_device_t:s0 tclass=chr_file permissive=0 Hash: gdb,abrt_t,dri_device_t,chr_file,read Version-Release number of selected component: selinux-policy-targeted-38.20-1.fc38.noarch Additional info: reporter: libreport-2.17.11 package: selinux-policy-targeted-38.20-1.fc38.noarch component: selinux-policy reason: SELinux is preventing gdb from 'read' accesses on the chr_file renderD128. kernel: 6.3.12-200.fc38.x86_64 hashmarkername: setroubleshoot type: libreport component: selinux-policy
Created attachment 1974702 [details] File: description
Created attachment 1974703 [details] File: os_info
*** This bug has been marked as a duplicate of bug 2219165 ***