powernowd does not start cleanly on Jaunty

Bug #340301 reported by Alex Sidorenko
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
powernowd (Ubuntu)
Fix Released
Undecided
Unassigned
Nominated for Jaunty by Florent

Bug Description

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: it is tracked on bug #340666
The second problem was first reported on bug #340300, now marked as duplicate.

These problems can be reproduced as follows.

root@jaunty:/var/log# /etc/init.d/powernowd.early start
/etc/init.d/powernowd: 180: /sbin/lsmod: not found
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]
Usage: modprobe [-v] [-V] [-C config-file] [-d <dirname> ] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
modprobe -r [-n] [-i] [-v] <modulename> ...
modprobe -l -t <dirname> [ -a <modulename> ...]

Related branches

Revision history for this message
Noel J. Bergman (noeljb) wrote :

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.

Changed in powernowd:
status: New → Confirmed
Revision history for this message
Alex Sidorenko (asid) wrote :

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 software...)

We probably need to submit a separate bugreport for acpid.

Alex

Florent (florent.x)
description: updated
Florent (florent.x)
description: updated
Revision history for this message
Florent (florent.x) wrote :

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.

Revision history for this message
Florent (florent.x) wrote :

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 +28,6 @@
 . /etc/default/rcS

 if [ "x$VERBOSE" = "xno" ]; then
- MODPROBE_OPTIONS="$MODPROBE_OPTIONS -Q"
+ MODPROBE_OPTIONS="$MODPROBE_OPTIONS -q"
         export MODPROBE_OPTIONS
 fi

Revision history for this message
Florent (florent.x) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 as the latter was dropped in
      the latest module-init-tools.

 -- Loic Minier <email address hidden> Tue, 10 Mar 2009 22:33:32 +0000

Changed in powernowd:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.