Description of problem: SELinux is preventing gdb from 'read' accesses on the chr_file nvidiactl. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the nvidiactl 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:xserver_misc_device_t:s0 Target Objects nvidiactl [ chr_file ] Source gdb Source Path gdb Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-38.17-1.fc38.noarch Local Policy RPM selinux-policy-targeted-38.17-1.fc38.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.3.8-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 15 02:15:40 UTC 2023 x86_64 Alert Count 404 First Seen 2023-03-26 16:21:47 EDT Last Seen 2023-06-30 16:21:05 EDT Local ID cb449402-27b3-4255-8c21-935969464f1d Raw Audit Messages type=AVC msg=audit(1688156465.83:3475): avc: denied { read } for pid=579677 comm="gdb" name="nvidiactl" dev="devtmpfs" ino=1065 scontext=system_u:system_r:abrt_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xserver_misc_device_t:s0 tclass=chr_file permissive=0 Hash: gdb,abrt_t,xserver_misc_device_t,chr_file,read Version-Release number of selected component: selinux-policy-targeted-38.17-1.fc38.noarch Additional info: reporter: libreport-2.17.10 reason: SELinux is preventing gdb from 'read' accesses on the chr_file nvidiactl. package: selinux-policy-targeted-38.17-1.fc38.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.3.8-200.fc38.x86_64 component: selinux-policy
Created attachment 1973457 [details] File: description
Created attachment 1973458 [details] File: os_info
This has been a constant nuisance since before Fedora 37.
Hi Tony, thank you for reporting the bug. We are investigating it. *** This bug has been marked as a duplicate of bug 2219166 ***