Bug 839736
| Summary: | After update to systemd-44-13 or newer, logging in via gdm gets no console session, sound doesn't work, Gnome Session uses >100% CPU | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Eric Smith <spacewar> |
| Component: | systemd | Assignee: | Michal Schmidt <mschmidt> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | johannbg, lnykryn, lpoetter, metherid, mschmidt, msekleta, notting, plautrba, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-10-07 22:46:41 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Eric Smith
2012-07-12 16:59:15 UTC
Created attachment 597856 [details]
systemd-tmpfiles status with systemd-44-17 (failed)
Created attachment 597857 [details]
systemd-tmpfiles status with systemd-44-17 with patches 405-407 removed (good)
I've found that setting /etc/sysconfig/selinux to set permissive rather than enforcing and using the normal systemd-44-17 does result in getting a login session, sound working, etc. There are var/log/messages entries for AVC denials and systemd errors. I'll attached edited log files for both the permissive (successful) and enforcing (failure) cases. I don't know what to make of these, other than to note that apparently when enforcing, systemd-logind reports that it can't create /run/user, which presumably is the reason that a user session can't be created. Created attachment 598226 [details]
avc and systemd messages from /var/log/messages with selinux enforcing
Created attachment 598227 [details]
avc and systemd messages from /var/log/messages with selinux permissive
The problem is that your /usr/local is a symlink. The SELinux policy does not take this possibility into account. The 'filesystem' package provides it as a directory. You should not modify your system this way. Or if you do, make sure you can do the necessary SELinux policy changes too. You could use a bind mount instead of a symlink to avoid the SELinux issue. Patch 0405 changes the behaviour of systemd-tmpfiles slightly. When opening the configuration directories, any other error than ENOENT now causes the whole thing to fail. This was an unexpected change that I can fix. Interesting! Thanks for looking at this. I always set up /usr/local and /opt as symlinks to /home/local and /home/opt so that they're on a filesystem that doesn't get wiped when I do an upgrade or reinstall. I barely know my way around SELinux, and certainly don't know how to fix the policy properly. I'll look into using bind mount as you suggest. (In reply to comment #6) > Patch 0405 changes the behaviour of systemd-tmpfiles slightly. When opening > the configuration directories, any other error than ENOENT now causes the > whole thing to fail. This was an unexpected change that I can fix. Fixed upstream: http://cgit.freedesktop.org/systemd/systemd/commit/?id=578ac0604e6c10b267f73e114bc2215aa3f6619a systemd-190-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/systemd-190-1.fc18 Package systemd-191-2.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-191-2.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-191-2.fc18 then log in and leave karma (feedback). Package glibc-2.16-17.fc18, systemd-192-1.fc18, selinux-policy-3.11.1-23.fc18, rtkit-0.11-3.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 systemd-192-1.fc18 selinux-policy-3.11.1-23.fc18 rtkit-0.11-3.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/selinux-policy-3.11.1-23.fc18,rtkit-0.11-3.fc18,systemd-192-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). Package glibc-2.16-17.fc18, rtkit-0.11-3.fc18, systemd-193-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.16-17.fc18 rtkit-0.11-3.fc18 systemd-193-1.fc18' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14581/rtkit-0.11-3.fc18,systemd-193-1.fc18,glibc-2.16-17.fc18 then log in and leave karma (feedback). systemd-44-20.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/systemd-44-20.fc17 |