Description of problem: acpi power button shutdown fails due to omission of path to shutdown in PATH in /etc/acpi/actions/power.sh In 'power.sh' PATH=/sbin:/bin:/usr/bin # which shutdown /usr/sbin/shutdown Hmm... Version-Release number of selected component (if applicable): acpid-2.0.21-1.fc20.x86_64 How reproducible: Always Steps to Reproduce: 1. Install acpid-2.0.21-1.fc20.x86_64 2. Delete all the conditional stuff between 'PATH=/sbin:/bin:/usr/bin' and 'shutdown -h now' 3. 'acpid restart' 4. Nil result Actual results: Nothing Expected results: Shutdown Additional info: Adding path to 'shutdown' in 'power.sh' fixes bug
Well, this is worth fix, but I cannot see why it is failing. There should be symlink: /sbin -> /usr/sbin Do you have such symlink on your filesystem? $ rpm -ql filesystem | grep ^/sbin$ /sbin $ rpm -qV filesystem # none error $ readlink /sbin usr/sbin
acpid-2.0.21-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/acpid-2.0.21-2.fc20
acpid-2.0.23-2.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/acpid-2.0.23-2.fc22
acpid-2.0.23-2.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/acpid-2.0.23-2.fc21
Package acpid-2.0.23-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 acpid-2.0.23-2.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-8550/acpid-2.0.23-2.fc22 then log in and leave karma (feedback).
acpid-2.0.23-2.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
acpid-2.0.23-2.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
acpid-2.0.21-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.