Description of problem: SELinux is preventing umount from 'getattr' accesses on the filesystem /. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that umount should be allowed getattr access on the filesystem 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 'umount' --raw | audit2allow -M my-umount # semodule -X 300 -i my-umount.pp Additional Information: Source Context system_u:system_r:snappy_t:s0 Target Context system_u:object_r:fs_t:s0 Target Objects / [ filesystem ] Source umount Source Path umount Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages filesystem-3.3-3.fc27.x86_64 Policy RPM selinux-policy-3.13.1-284.37.fc27.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.18.12-100.fc27.x86_64 #1 SMP Thu Oct 4 16:22:17 UTC 2018 x86_64 x86_64 Alert Count 20 First Seen 2018-02-21 14:59:57 +0330 Last Seen 2018-10-17 08:17:41 +0330 Local ID e0088dd8-66e7-4747-88cc-dc1a79666a3b Raw Audit Messages type=AVC msg=audit(1539751661.330:103): avc: denied { getattr } for pid=1128 comm="umount" name="/" dev="loop4" ino=2 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:fs_t:s0 tclass=filesystem permissive=1 Hash: umount,snappy_t,fs_t,filesystem,getattr Version-Release number of selected component: selinux-policy-3.13.1-284.37.fc27.noarch Additional info: component: selinux-policy reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.18.12-100.fc27.x86_64 type: libreport Potential duplicate: bug 1597878
Also affecting Fedora 28: [bharrington@leviathan Documents]$ uname -a Linux leviathan.rvu.io 4.18.16-200.fc28.x86_64 #1 SMP Sat Oct 20 23:53:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ rpm -qa snap* snapd-2.36-1.fc28.x86_64 snapd-glib-1.44-1.fc28.x86_64 snap-confine-2.36-1.fc28.x86_64 snapd-selinux-2.36-1.fc28.noarch
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Description of problem: i just opened my laptop and got an Alert message! Version-Release number of selected component: selinux-policy-3.13.1-284.37.fc27.noarch Additional info: reporter: libreport-2.9.3 hashmarkername: setroubleshoot kernel: 4.18.19-100.fc27.x86_64 type: libreport