One of my flatpak program crash regularly, as it does I get a SELinux error each time from systemd-coredump probably trying to access information inside the flatpak ===================================================================== SELinux is preventing systemd-coredum from using the sys_admin capability. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that systemd-coredum 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 'systemd-coredum' --raw | audit2allow -M my-systemdcoredum # semodule -X 300 -i my-systemdcoredum.pp Additional Information: Source Context system_u:system_r:systemd_coredump_t:s0 Target Context system_u:system_r:systemd_coredump_t:s0 Target Objects Unknown [ capability ] Source systemd-coredum Source Path systemd-coredum Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-40.20-1.fc40.noarch Local Policy RPM selinux-policy-targeted-40.20-1.fc40.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 6.8.10-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 17 21:20:54 UTC 2024 x86_64 Alert Count 29 First Seen 2024-05-13 16:18:28 CEST Last Seen 2024-05-26 08:29:30 CEST Local ID beda04b7-c95d-44e5-97d5-3a769506753e Raw Audit Messages type=AVC msg=audit(1716704970.131:338): avc: denied { sys_admin } for pid=13929 comm="systemd-coredum" capability=21 scontext=system_u:system_r:systemd_coredump_t:s0 tcontext=system_u:system_r:systemd_coredump_t:s0 tclass=capability permissive=0 Hash: systemd-coredum,systemd_coredump_t,systemd_coredump_t,capability,sys_admin Reproducible: Always Steps to Reproduce: 1.Launch a Flatpak application 2.Send it SIGSEGV signal 3.Watch SELinux giving an error from systemd-coredump Actual Results: SELinux error Expected Results: No SELinux error
*** This bug has been marked as a duplicate of bug 2278902 ***