Bug 901926
| Summary: | rtkit.service does not start after upgrading from F17 to F18 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Iñigo Serna <inigoserna> |
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | dalt74, johannbg, lnykryn, lpoetter, metherid, msekleta, notting, plautrba, systemd-maint, vpavlin |
| 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: | 2013-03-08 00:11:40 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: | |||
UPDATE: 1. Above, I mention "systemctl status rtkit.service". I meant rtkit-daemon.service, of course. 2. If I run /usr/libexec/rtkit-daemon manually from CLI, login screen is shown and I can log in UPDATE 2: 1. Changed component. Looks like it's a "systemd" issue, not rtkit 2. Upgraded today systemd v197 from v195, problem persists 3. colord and cups can't start at boot from systemd either Some logs: [~]# systemctl restart colord.service Job for colord.service failed. See 'systemctl status colord.service' and 'journalctl -xn' for details. [~]# systemctl status colord.service colord.service - Manage, Install and Generate Color Profiles Loaded: loaded (/usr/lib/systemd/system/colord.service; static) Active: failed (Result: exit-code) since Sun 2013-01-20 16:19:52 CET; 2s ago Process: 2888 ExecStart=/usr/libexec/colord (code=exited, status=226/NAMESPACE) Jan 20 16:19:52 inigo.katxi.org systemd[1]: colord.service: main process exited, code=exited, status=226/NAMESPACE Jan 20 16:19:52 inigo.katxi.org systemd[1]: Failed to start Manage, Install and Generate Color Profiles. Jan 20 16:19:52 inigo.katxi.org systemd[1]: Unit colord.service entered failed state [~]# systemctl status cups.service cups.service - CUPS Printing Service Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled) Active: failed (Result: exit-code) since Sun 2013-01-20 16:25:52 CET; 32s ago Process: 3397 ExecStart=/usr/sbin/cupsd -f (code=exited, status=226/NAMESPACE) Jan 20 16:25:52 inigo.katxi.org systemd[1]: Starting CUPS Printing Service... Jan 20 16:25:52 inigo.katxi.org systemd[1]: Started CUPS Printing Service. Jan 20 16:25:52 inigo.katxi.org systemd[1]: cups.service: main process exited, code=exited, status=226/NAMESPACE Jan 20 16:25:52 inigo.katxi.org systemd[1]: Unit cups.service entered failed state [~]# systemctl restart rtkit-daemon Job for rtkit-daemon.service failed. See 'systemctl status rtkit-daemon.service' and 'journalctl -xn' for details. [~]# systemctl status rtkit-daemon rtkit-daemon.service - RealtimeKit Scheduling Policy Service Loaded: loaded (/usr/lib/systemd/system/rtkit-daemon.service; enabled) Active: failed (Result: exit-code) since Sun 2013-01-20 16:28:00 CET; 3s ago Process: 3481 ExecStart=/usr/libexec/rtkit-daemon (code=exited, status=226/NAMESPACE) Jan 20 16:28:00 inigo.katxi.org systemd[1]: rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE Jan 20 16:28:00 inigo.katxi.org systemd[1]: Failed to start RealtimeKit Scheduling Policy Service. Jan 20 16:28:00 inigo.katxi.org systemd[1]: Unit rtkit-daemon.service entered failed state UPDATE 3: Fixed! Issue comes from/var/tmp being a symlink to /tmp. This breaks systemd's PrivateTmp features. Thus, setting "PrivateTmp=no" fixes the problems with the 3 daemons mentioned in this bug report. My computer comes from old upgrades (maybe Fedora 10 or even before). In one of those upgrades /var/tmp become a symbolic link to /tmp. I read solution from: https://bugs.archlinux.org/task/30229 and comment #2 of https://bbs.archlinux.org/viewtopic.php?pid=1185935 *** Bug 904821 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 835131 *** |
Description of problem: After upgrading my x86_64 computer from F17 to F18, login screen is not showed anymore. Looking at logs shows rtkit.service is not running. Executing "systemctl restart rtkit.service" from CLI does not work either. # systemctl status rtkit.service rtkit.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) # cat /var/log/message: [...] dbus-daemon[600]: [system] Failed to active service 'org.freedesktop.RealtimeKit1': timed out [...] systemd[1] Starting RealtimeKit Scheduling Policy Service... [...] systemd[662] Failed at step NAMESPACE spawning /usr/libexec/rtkit-daemon: Operation not permitted [...] systemd[1] rtkit-daemon.service: main process exited, code=exited, status=226/NAMESPACE [...] systemd[1] Unit rtkit-daemon.service entered failed state Disabling selinux does not help. Version-Release number of selected component (if applicable): rtkit 0.11-3.fc18.x86_64 systemd-195-15.fc18.x86_64 dbus-1.6.8-2.fc18.x86_64 How reproducible: Always