Description of problem: SELinux is preventing mount from 'mounton' accesses on the carpeta /tmp/selftest-mountpoint-215687625. ***** Plugin catchall (100. confidence) suggests ************************** Si cree que de manera predeterminada se debería permitir a mount el acceso mounton sobre selftest-mountpoint-215687625 directory. Then debería reportar esto como un error. Puede generar un módulo de política local para permitir este acceso. Do permita el acceso temporalmente ejecutando: # ausearch -c 'mount' --raw | audit2allow -M mi-mount # semodule -X 300 -i mi-mount.pp Additional Information: Source Context system_u:system_r:snappy_t:s0 Target Context system_u:object_r:tmp_t:s0 Target Objects /tmp/selftest-mountpoint-215687625 [ dir ] Source mount Source Path mount Port <Desconocido> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.1-32.fc28.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.17.5-200.fc28.x86_64 #1 SMP Tue Jul 10 13:39:04 UTC 2018 x86_64 x86_64 Alert Count 2 First Seen 2018-07-15 16:31:51 CDT Last Seen 2018-07-15 16:35:40 CDT Local ID 7f7e9741-e0c1-4cca-8376-a8c8e09e8811 Raw Audit Messages type=AVC msg=audit(1531690540.838:241): avc: denied { mounton } for pid=2385 comm="mount" path="/tmp/selftest-mountpoint-215687625" dev="tmpfs" ino=45220 scontext=system_u:system_r:snappy_t:s0 tcontext=system_u:object_r:tmp_t:s0 tclass=dir permissive=1 Hash: mount,snappy_t,tmp_t,dir,mounton Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: component: selinux-policy reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.5-200.fc28.x86_64 type: libreport
Description of problem: Installing snap packages generated this exception. But I have not faced any problem in daily use. Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.6-200.fc28.x86_64 type: libreport
Description of problem: Installed snapd and rebooted Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.7-200.fc28.x86_64 type: libreport
Description of problem: 1. I restarted my device 2. Logged in Deviceinfo: Dell Precision 5510 Version-Release number of selected component: selinux-policy-3.14.1-37.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.12-200.fc28.x86_64 type: libreport
Alerts happen to me right after boot, together with https://bugzilla.redhat.com/show_bug.cgi?id=1597878 and others Happen to pop up only after I installed snapd (a.k.a. snapcraft)
Description of problem: https://bugzilla.redhat.com/show_bug.cgi?id=1601273 https://bugzilla.redhat.com/show_bug.cgi?id=1601279 https://bugzilla.redhat.com/show_bug.cgi?id=1597878 Version-Release number of selected component: selinux-policy-3.14.1-40.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.19-200.fc28.x86_64 type: libreport
Description of problem: Problem arises during boot process Version-Release number of selected component: selinux-policy-3.14.1-40.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.19-200.fc28.x86_64 type: libreport
Description of problem: Part of a series of errors generated by mount when I boot up my system, Fedora 28 Version-Release number of selected component: selinux-policy-3.14.1-40.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.19-200.fc28.x86_64 type: libreport
Description of problem: iinstalling apps from snapd Version-Release number of selected component: selinux-policy-3.14.1-42.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.18.7-200.fc28.x86_64 type: libreport
*** Bug 1629856 has been marked as a duplicate of this bug. ***
*** Bug 1693265 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.