Bug 1485471
Summary: | SELinux is preventing systemd-logind from 'read' accesses on the directory dbus-1. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike Simms <micsim2007> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | alexander.heike, amessina, cadencenix, chelsi.doyle, Claude.Frantz, csamyn, danielsun3164, ddmpost, deepblu, diamantis.karagkiaouris.dev, dimhen, dominik, dooberindallas, dwalsh, edcalderon, ekuric, e.nedelec, ericbasil.rabi, eva_nieto, frans-jan, Gecko8211, goochmi, goodmirek, igiwatson, ipsixin3d, jayabharat, jfrieben, jonathonpoppleton, jonlukassen, joshua, lonelywoolf, lsm5, lvrabec, mail, mail, marco.guazzone, marco.n.coppola, matheuscumth, mehedihasanbappy1997, mgrepl, mschorm, nddker, penguin01210, plautrba, pmoore, quintela, redhat, rfmazzini, rocketraman, s.kieske, viorel.tabara, write.to.lee.igor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:3ae89f1f4e5eeb22d0c8baf0c9bb138c3743e19643eeb8ea3d76b461f23822ef; | ||
Fixed In Version: | selinux-policy-3.13.1-260.8.fc26 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-09-03 08:33:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike Simms
2017-08-25 20:52:45 UTC
duplicate of a bug in rawhide listed above BUT this is release version so not sure whether or not to close. anyhow it also happens with kernel 4.12.8 from updates testing Description of problem: running kernel-tests on 4.12.9 Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport I see the same problem while using Fedora 26 Release (4.12.8-300.fc26.x86_64) and that components (testing updates have been installed because of troubleshooting; usually I prefer versions from "@updates" repository): dnfdaemon-selinux.noarch 0.3.18-3.fc26 @updates-testing libselinux.x86_64 2.6-7.fc26 @updates libselinux-python3.x86_64 2.6-7.fc26 @updates libselinux-utils.x86_64 2.6-7.fc26 @updates rpm-plugin-selinux.x86_64 4.13.0.1-7.fc26 @updates selinux-policy.noarch 3.13.1-260.6.fc26 @updates selinux-policy-targeted.noarch 3.13.1-260.6.fc26 @updates Hello everybody . I have a Fedora Mate 26, a similar problem after the upgrade, the kernel 4.12.8-300.fc26.x86_64 *** Bug 1486517 has been marked as a duplicate of this bug. *** Can confirm this issue in Fedora KDE. *** Bug 1486912 has been marked as a duplicate of this bug. *** *** Bug 1486919 has been marked as a duplicate of this bug. *** Description of problem: appeared juste after login (Mate spin, using lightDM) Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.8-300.fc26.x86_64 type: libreport Description of problem: I unfortunately am very inexperienced with Linux and I have no information I can share about what may have cause this error - I can't attach an event to the error's appearance. I haven't noticed anything else out of the ordinary. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.8-300.fc26.x86_64 type: libreport Nate, I wouldn't be too concerned. As the update which caused this behaviour was pushed stable despite this bug, the maintainer clearly isn't that concerned about the alert and we evidently have to put up with it for now at least Description of problem: Selinux alert was visible after system boot on F26 with latest packages Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.8-300.fc26.x86_64 type: libreport Description of problem: I just installed Fedora XFCE 26 and then updated it by "dnf upgrade" command. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.8-300.fc26.x86_64 type: libreport *** Bug 1487435 has been marked as a duplicate of this bug. *** Description of problem: On login to KDE. Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.8-300.fc26.x86_64 type: libreport Description of problem: This error appear just after first login after system boot Fedora 26 MATE, done a clean install and updated to 1 Sep 2017, then reboot and login. The error appear there. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: I ran the following commands, after they finished successfully I got the error message dnf config-manager --add-repo=http://negativo17.org/repos/fedora-spotify.repo dnf install spotify Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport I have been testing selinux-policy-3.13.1-260.8.fc26 from Koji and it fixes this bug for me.. Thanks. Description of problem: This happened after logout from gnome wayland session. Lots of "gnome-session-binary[1507]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed" errors in journal before SELinux problem. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: This just appeared after logging in after rebooting after an update (selinux-policy-targeted-3.13.1-260.6.fc26.noarch was among the updated packages). Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport (In reply to Colin J Thomson from comment #18) > I have been testing selinux-policy-3.13.1-260.8.fc26 from Koji and it fixes > this bug for me.. Thanks. Worked for me too. Description of problem: put on charging. After 15 minutes, throws an error notification Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Confirmed fixed here too, so closing as resolved selinux-policy-3.13.1-260.8.fc26 is now in updates-testing folks *** Bug 1487919 has been marked as a duplicate of this bug. *** Description of problem: desde que instale fedora ocurrio que me pide acceso un proceso. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: reboot after update Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: Immediately at login Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: O erro é reportado logo ao iniciar o fedora 26 cinnamon. Não foi notado nenhum problema decorrente deste. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport Description of problem: Happens (everytime) just after login to the mate-environment. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport The following comment has been added to the selinux-policy-3.13.1-260.8.fc26 update: bodhi - 2017-09-05 00:51:42.804586 (karma: 0) This update has been pushed to stable. https://bodhi.fedoraproject.org/updates/FEDORA-2017-fd93b6e5f8 This version resolves the issue folks, please update your systems! Description of problem: Problem arose after log-in after resume from suspend. Version-Release number of selected component: selinux-policy-3.13.1-260.6.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.9-300.fc26.x86_64 type: libreport |