Description of problem: SELinux is preventing agetty from using the 'checkpoint_restore' capabilities. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that agetty should have the checkpoint_restore 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 'agetty' --raw | audit2allow -M my-agetty # semodule -X 300 -i my-agetty.pp Additional Information: Source Context system_u:system_r:getty_t:s0-s0:c0.c1023 Target Context system_u:system_r:getty_t:s0-s0:c0.c1023 Target Objects Unknown [ capability2 ] Source agetty Source Path agetty Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-39.4-1.fc39.noarch Local Policy RPM selinux-policy-targeted-39.4-1.fc39.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.7.5-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Feb 17 17:20:08 UTC 2024 x86_64 Alert Count 14 First Seen 2024-02-20 23:05:29 AST Last Seen 2024-02-23 12:17:18 AST Local ID 8738f841-d260-4c87-9593-f1f23f8eac02 Raw Audit Messages type=AVC msg=audit(1708705038.986:163): avc: denied { checkpoint_restore } for pid=1400 comm="agetty" capability=40 scontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tcontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tclass=capability2 permissive=0 Hash: agetty,getty_t,getty_t,capability2,checkpoint_restore Version-Release number of selected component: selinux-policy-targeted-39.4-1.fc39.noarch Additional info: reporter: libreport-2.17.11 reason: SELinux is preventing agetty from using the 'checkpoint_restore' capabilities. package: selinux-policy-targeted-39.4-1.fc39.noarch component: selinux-policy hashmarkername: setroubleshoot type: libreport kernel: 6.7.5-200.fc39.x86_64 component: selinux-policy
Created attachment 2018329 [details] File: description
Created attachment 2018330 [details] File: os_info
*** This bug has been marked as a duplicate of bug 2259622 ***