Description of problem: When restarting a service, the systemctl command throws a misleading and useless error message. For example [marcobillpeter@dhcp145-26 cups]$ sudo systemctl restart cupsd Failed to issue method call: Unit cupsd.service failed to load: No such file or directory. See system logs and 'systemctl status cupsd.service' for details. Version-Release number of selected component (if applicable): How reproducible: always, just misspell service name Steps to Reproduce: 1. [marcobillpeter@dhcp145-26 cups]$ sudo systemctl restart cupsd Failed to issue method call: Unit cupsd.service failed to load: No such file or directory. See system logs and 'systemctl status cupsd.service' for details. Actual results: Failed to issue method call: Unit cupsd.service failed to load: No such file or directory. See system logs and 'systemctl status cupsd.service' for details. Expected results: An error message saying that the service name is unknown and show the syntax to list all known services (which will help an enduser Additional info:
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
http://cgit.freedesktop.org/systemd/systemd/commit/?id=04ef5b03
systemd-208-20.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/systemd-208-20.fc20
Package systemd-208-20.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-208-20.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-8572/systemd-208-20.fc20 then log in and leave karma (feedback).
systemd-208-20.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.