Description of problem: SELinux is preventing snapd from 'write' accesses on the file code.lock. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that snapd should be allowed write access on the code.lock 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 'snapd' --raw | audit2allow -M my-snapd # semodule -X 300 -i my-snapd.pp Additional Information: Source Context system_u:system_r:snappy_t:s0 Target Context system_u:object_r:var_run_t:s0 Target Objects code.lock [ file ] Source snapd Source Path snapd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-36.13-3.fc36.noarch Local Policy RPM snapd-selinux-2.56.2-4.fc36.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.18.16-200.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Aug 3 15:44:49 UTC 2022 x86_64 x86_64 Alert Count 3 First Seen 2022-08-07 14:31:17 CST Last Seen 2022-08-11 18:23:04 CST Local ID 31d6012b-d020-4e36-82ac-d0b09027347b Raw Audit Messages type=AVC msg=audit(1660213384.488:388): avc: denied { write } for pid=6857 comm="snapd" name="code.lock" dev="tmpfs" ino=2349 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=file permissive=1 Hash: snapd,snappy_t,var_run_t,file,write Version-Release number of selected component: selinux-policy-targeted-36.13-3.fc36.noarch Additional info: component: snapd reporter: libreport-2.17.1 hashmarkername: setroubleshoot kernel: 5.18.16-200.fc36.x86_64 type: libreport
Similar problem has been detected: Occurs at startup hashmarkername: setroubleshoot kernel: 5.19.6-200.fc36.x86_64 package: selinux-policy-targeted-36.14-1.fc36.noarch reason: SELinux is preventing snapd from 'write' accesses on the file core18.lock. type: libreport
Similar problem has been detected: I'd like to update this onenote application. hashmarkername: setroubleshoot kernel: 6.0.8-200.fc36.x86_64 package: selinux-policy-targeted-36.16-1.fc36.noarch reason: SELinux is preventing snapd from 'write' accesses on the file p3x-onenote.lock. type: libreport
Similar problem has been detected: During update hashmarkername: setroubleshoot kernel: 6.0.15-200.fc36.x86_64 package: selinux-policy-targeted-36.17-1.fc36.noarch reason: SELinux is preventing snapd from 'write' accesses on the Datei /run/snapd/lock/core20.lock. type: libreport
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.