This bug was fixed in the package powernowd - 1.00-1ubuntu4
---
powernowd (1.00-1ubuntu4) jaunty; urgency=low
* Update init script for new module-init-tools; LP: #340301.
- Don't hardcode path of lsmod to /sbin as it moved to /bin.
- Set MODPROBE_OPTIONS to -q instead of -Q
** Attachment added: "fix-powernowd-init.patch"
http://launchpadlibrarian.net/23766317/fix-powernowd-init.patch
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Here is the fix for second problem ("Usage:" messages).
It is because the option "modprobe -Q" is not supported any more.
It should be replaced with "modprobe -q
--- a/etc/init.d/powernowd Wed Mar 11 23:50:10 2009 +0100
+++ b/etc/init.d/powernowd Thu Mar 12 00:23:06 2009 +0100
@@ -28,6
Problem on "/sbin/lsmod" will be fixed on module-init-tools. It was a
packaging error. See bug #340666.
Second problem is still opened : "Usage:" messages printed on standard
output.
--
powernowd does not start cleanly on Jaunty
https://bugs.launchpad.net/bugs/340301
You received this bug notifi
** Description changed:
Two problems with script /etc/init.d/powernowd:
- it tries to use /sbin/lsmod
- it prints a "Usage:" message on standard output
- The first problem affects other packages: see bug #341262
+ The first problem affects other packages: it is tracked on bug #340666
Th
** Description changed:
- The script /etc/init.d/powernowd tries to use /sbin/lsmod:
+ Two problems with script /etc/init.d/powernowd:
+ - it tries to use /sbin/lsmod
+ - it prints a "Usage:" message on standard output
+
+ The first problem affects other packages: see bug #341262
+ The second pro
I have found that other packages rely on /sbin/lsmod either, e.g.
{root 14:42:28} fgrep lsmod /etc/init.d/acpi*
/etc/init.d/acpid: LIST="$(/sbin/lsmod | awk '!/Module/ {print $1}')"
acpid 1.0.6-9ubuntu4
vmware module generation depends on /sbin/lsmod (well, this is not free
sof
That is not the only error message from the script, as can be seen from
Bug 340300 (interesting that both were reported back to back).
The attached patch eliminates the error messages, but that may be hiding
something that needs to be fixed.
** Attachment added: "powernowd.patch"
http://launc
