Bug 1238664
| Summary: | udisks can not be started: udisks.service contains incorrect binary | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael Chapman <redhat-bugzilla> |
| Component: | udisks | Assignee: | David King <amigadave> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | amigadave, tom.killian |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | udisks-1.0.5-2.fc22 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-07-19 02:00:01 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: | |||
udisks-1.0.5-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/udisks-1.0.5-2.fc22 udisks-1.0.5-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/udisks-1.0.5-2.fc21 Package udisks-1.0.5-2.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing udisks-1.0.5-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11064/udisks-1.0.5-2.fc22 then log in and leave karma (feedback). *** Bug 1239133 has been marked as a duplicate of this bug. *** udisks-1.0.5-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. udisks-1.0.5-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |
As of udisks-1.0.5-1.fc21, udisks.service can not be started because the binary in the ExecStart directive is incorrect. $ rpm -q udisks udisks-1.0.5-1.fc21.x86_64 $ systemctl status udisks.service ● udisks.service - Disk Manager (legacy version) Loaded: loaded (/usr/lib/systemd/system/udisks.service; static) Active: failed (Result: exit-code) since Thu 2015-07-02 21:02:55 AEST; 7min ago Docs: man:udisks(7) Process: 5398 ExecStart=/usr/lib/udisks/udisks-daemon --no-debug (code=exited, status=203/EXEC) Main PID: 5398 (code=exited, status=203/EXEC) Jul 02 21:02:55 beren.home systemd[5398]: Failed at step EXEC spawning /usr/lib/udisks/udisks-daemon: No such file or directory Jul 02 21:02:55 beren.home systemd[1]: udisks.service: main process exited, code=exited, status=203/EXEC Jul 02 21:02:55 beren.home systemd[1]: Failed to start Disk Manager (legacy version). Jul 02 21:02:55 beren.home systemd[1]: Unit udisks.service entered failed state. Jul 02 21:02:55 beren.home systemd[1]: udisks.service failed. $ rpm -ql udisks | grep udisks-daemon /usr/libexec/udisks-daemon /usr/share/man/man8/udisks-daemon.8.gz Dropping in the following systemd config fragment to replace ExecStart can work around the problem: # /etc/systemd/system/udisks.service.d/20-ExecStart.conf [Service] ExecStart= ExecStart=/usr/libexec/udisks-daemon --no-debug