Description of problem: SELinux is preventing gdb from 'read' accesses on the chr_file card0. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gdb should be allowed read access on the card0 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 card0 [ 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.10-201.fsync.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Jul 1 17:41:47 UTC 2023 x86_64 Alert Count 4 First Seen 2023-07-02 15:41:05 MSK Last Seen 2023-07-02 18:42:01 MSK Local ID 75369781-249b-491f-835b-3d923605dad4 Raw Audit Messages type=AVC msg=audit(1688312521.536:146): avc: denied { read } for pid=1191 comm="gdb" name="card0" dev="devtmpfs" ino=168 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 reason: SELinux is preventing gdb from 'read' accesses on the chr_file card0. package: selinux-policy-targeted-38.20-1.fc38.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.3.10-201.fsync.fc38.x86_64 component: selinux-policy
Created attachment 1973759 [details] File: description
Created attachment 1973760 [details] File: os_info
*** This bug has been marked as a duplicate of bug 2219166 ***
*** Bug 2221385 has been marked as a duplicate of this bug. ***