Red Hat Bugzilla – Bug 245293
kpowersave can't find pidof
Last modified: 2008-04-29 17:00:44 EDT
Description of problem:
Every now and then (at start, after resume) kpowersave complains that
it "Could not start 'pidof'. Could not autosuspend the machine.
Please check your installation.".
Version-Release number of selected component (if applicable):
Almost every time
Steps to Reproduce:
1. install kpowersave, run it in KDE
It also complained about not being able to umount all removable devices a few
noticed the same problem... since j'm running non english version the
translation of system massage is like ...."kpowersave is not able to execute/run
pidof, could not autosuspend, Please check suspend settings"....
it cures every time i login the system or change settings in kpowersave...
suspending manually using kpowersave works fine...
kernel 126.96.36.199-10_1.cubbi_tuxonice.fc7 #1 SMP i686 (atrpms)
same here with fedora 8, up-to-date as of feb.7, 2008
Cannot confirm, worksforme.
Looks working here too... No idea when it got fixed, but for a long time I
don't have this problem.
Well... it got fixed at some point...
Sorry, saw this again today... kpowersave-0.7.3-1.fc8.
Created attachment 297262 [details]
The error message screenshot (the error window only).
I can confirm this.
Here's the interesting part: /sbin/pidof exists
grep -R pidof /var/log
..doesn't return any results
ok, looks like this was fixed only in rawhide, in build kpowersave-0.7.3-3.
Looks like we need to issue an update for f7/f8.
kpowersave-0.7.3-3.fc8 has been submitted as an update for Fedora 8
kpowersave-0.7.3-3.fc8 has been pushed to the Fedora 8 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update kpowersave'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F8/FEDORA-2008-2959
kpowersave-0.7.3-3.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.