warning: missing LSB information

[KevinM]

Binary package hint: linux-restricted-modules-common

While performing an update (with sudo apt-get upgrade) to Jaunty kernel 2.6.27-7 64 bit I received the following:
Setting up linux-restricted-modules-common (2.6.28-2.1) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
NonfreeKernelModules: nvidia
Package: linux-image-2.6.27-7-generic 2.6.27-7.14
ProcCmdLine: root=UUID=c86d77b6-57e9-4fa8-857b-8d11cd8bb658 ro
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
SourcePackage: linux
UnreportableReason: This is not a genuine Ubuntu package

[Adrien Cunin (adri2000)]

Indeed.

[Bremm (bremm)]

Same here with powernowd.

Configurando powernowd (1.00-1ubuntu5) ...
update-rc.d: warning: /etc/init.d/powernowd.early missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
 * Starting powernowd...

[Hellsgator (hellsgate)]

Setting up linux-restricted-modules-common (2.6.28-11.15) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

After updates 03/04/09. ;)

[Volnei (volneila)]

Same here in restricted modules atualization today (09/06/09):

Preparando para substituir linux-restricted-modules-common 2.6.28-12.16 (usando .../linux-restricted-modules-common_2.6.28-13.17_all.deb) ...
Desempacotando substituto linux-restricted-modules-common ...
Configurando linux-libc-dev (2.6.28-13.44) ...
Configurando linux-restricted-modules-common (2.6.28-13.17) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

In portuguese, of course... :).

[Andy Whitcroft (apw)]

Indeed the LRM init script is missing its LSB headers. We are installing this script using the debhelpers as below:

    dh_installinit -p linux-restricted-modules-common --no-start -- start 7 S . start 1 0 6 .

So we only care about starting. Starting at priority 7 in rcS.d and priority 1 in rc0.d and rc6.d. Something like this:

### BEGIN INIT INFO
# Provides: linux-restricted-modules
# Required-Start: $local_fs
# Required-Stop:
# Default-Start: S 0 6
# Default-Stop:
# Short-Description: Setup the linux restricted modules
# Description: Link the linux restricted modules at run time.
### END INIT INFO

[Andy Whitcroft (apw)]

Attached is a proposed patch for the linux-restricted-modules package for Jaunty implementing this change. WIll push this to the kernel-team list for review.

[ops0603 (mike-perkins)]

Andy,
Thanks very much for keeping this thread updated, I found it useful to know what the problem was, and that it has been assigned for a fix. I received the same message today when attempting to do an apt-get upgrade as follows;

Preparing to replace linux-restricted-modules-common 2.6.28-11.15 (using .../linux-restricted-modules-common_2.6.28-13.17_all.deb)...

update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

Look forward to an update in the coming days.
Cheers,
M.

[MasterMirko (jedimastermirko)]

Hi all,
I also have the same problem as ops0603 while updating my Kubuntu 9.04. I tried the solution proposed by Andy, but I have some problem while using his patch.

Looking forward for a widely available patch in the next day.

Thank you all!

Mirko

[JacobSteelsmith (jacobsteelsmith)]

I got the same message as ops0603 replacing linux-restricted-modules-common using apt-get upgrade...

[Derek White (d-man97)]

Setting up linux-restricted-modules-common (2.6.28-13.17) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

Is it safe to restart and use the new kernel?

[JacobSteelsmith (jacobsteelsmith)]

Yes. It doesn't seem to affect boot and use.

On Jun 21, 2009 11:01 AM, "Derek White" <email address hidden> wrote:

Setting up linux-restricted-modules-common (2.6.28-13.17) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing
LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

Is it safe to restart and use the new kernel?

-- [Jaunty] warning: missing LSB information
https://bugs.launchpad.net/bugs/305587 You received ...

[MasterMirko (jedimastermirko)]

I also did it, and I had no problems till now.

[aleg (alwin-vanegmond-samuel)]

Got the same message doing the apt-get upgrade.

Setting up linux-restricted-modules-common (2.6.28-13.17) ...
update-rc.d: warning: /etc/init.d/linux-restricted-modules-common missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

[Martin Pitt (pitti)]

We should really avoid conffile changes in stable updates, thus this really shouldn't be changed in jaunty-updates. Can you please upload a new l-r-m without this change? Thanks!

[Martin Pitt (pitti)]

Some more rationale: people who customized the init script will get a conffile prompt on upgrades, which breaks automatic upgrades (which are quite common on stable releases). Also, there are packages which actually evaluate those LSB headers, such as insserv. By adding a new one, we potentially change the boot sequence, which again introduces a regression potential.

[Martin Pitt (pitti)]

Not relevant for Karmic, since l-r-m is gone.

[Martin-Éric Racine (q-funk)]

Very much relevant for Karmic, since acpi-support still misses its LSB headers there too.

[Martin-Éric Racine (q-funk)]

Also relevant for one of powernowd's scripts, again in Karmic:

insserv: warning: script 'acpi-support' missing LSB tags and overrides
insserv: warning: script 'powernowd.early' missing LSB tags and overrides

[Ernst (ernst-blaauw)]

I just installed some updates on Karmic and I got the message too:

Setting up acpi-support (0.127) ...
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
 * Checking battery state... [ OK ]

[dasdsadsada (dasdasdas-deactivatedaccount)]

Karmic has the same problem, so the bug isn't fixed.

Setting up acpi-support (0.127) ...
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
 * Checking battery state...

[Steve Langasek (vorlon)]

Yes, no one has said that this bug is fixed.

[bersyl91 (choppy-free)]

I'be got the same misbehavior with a custom init-script:

# update-rc.d myinitscript defaults 99
update-rc.d: warning: /etc/init.d/myinitscript missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
 Adding system startup for /etc/init.d/myinitscript ...
   /etc/rc0.d/K99myinitscript -> ../init.d/myinitscript
   /etc/rc1.d/K99myinitscript -> ../init.d/myinitscript
   /etc/rc6.d/K99myinitscript -> ../init.d/myinitscript
   /etc/rc2.d/S99myinitscript -> ../init.d/myinitscript
   /etc/rc3.d/S99myinitscript -> ../init.d/myinitscript
   /etc/rc4.d/S99myinitscript -> ../init.d/myinitscript
   /etc/rc5.d/S99myinitscript -> ../init.d/myinitscript

Whereas the myinitscript file contains:

### BEGIN INIT INFO
# Provides: myinitscript
# Required-Start: $network $remote_fs
# Required-Stop: $network $remote_fs
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Description: Start the myinitscript daemon
### END INIT INFO

I run:
Linux version 2.6.28-15-generic (buildd@rothera) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #52-Ubuntu SMP Wed Sep 9 10:49:34 UTC 2009

[Laurent Bonnaud (laurent-bonnaud)]

This bug also affects karmic

[Laurent Bonnaud (laurent-bonnaud)]

This bug still exists in lucid. For example:

# apt-get install --reinstall acpi-support
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 34.8kB of archives.
After this operation, 0B of additional disk space will be used.
Do you want to continue [Y/n]?
Get:1 http://fr.archive.ubuntu.com/ubuntu/ lucid/main acpi-support 0.133 [34.8kB]
Fetched 34.8kB in 0s (291kB/s)
(Reading database ... 135148 files and directories currently installed.)
Preparing to replace acpi-support 0.133 (using .../acpi-support_0.133_i386.deb) ...
 * Disabling power management... [ OK ]
Unpacking replacement acpi-support ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Processing triggers for man-db ...
Setting up acpi-support (0.133) ...
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>
 * Checking battery state... [ OK ]

[Phillip Susi (psusi)]

The powernowd package is obsolete, please do not use it. CPU frequency scaling is now handled by the kernel, so if you still have issues on a modern release, file a bug against the linux package.

[Steve Langasek (vorlon)]

> The powernowd package is obsolete, please do not use it.

The powernowd package is still in the Ubuntu archive as of natty. This is not an invalid bug.

[Phillip Susi (psusi)]

This package is obsolete and has been removed from the archive. Closing associated bugs.

[Laurent Bonnaud (laurent-bonnaud)]

This bug is still in oneiric in this package version:

Package: acpi-support
Version: 0.138

# dpkg-reconfigure acpi-support
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

[Clint Byrum (clint-fewbar)]

Thanks Laurent. Hopefully someone will fix it in the next release, tho I doubt it will get done for 11.10 given how close this is to release.

I'm unsubscribing ubuntu-sru since there are no SRU's prepared for this bug right now.

[Anthony Harrington (linuxchemist)]

Actually just saw this today on 64bit Precise when updating the acpi-support package to 0.139.

Installing new version of config file /etc/acpi/rotatescreen.sh ...
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

[Evgeniy Lisetckiy (e-lisetckiy)]

Really. I'm use Ubuntu 12.04-amd64 with latest updatest on 03/05/2012 and I see some messages.

[Evgeniy Lisetckiy (e-lisetckiy)]

on #32 message - "... I see same message"

[Laurent Bonnaud (laurent-bonnaud)]

This bug is still in precise in this package version:

Package: acpi-support
Version: 0.140

# dpkg-reconfigure acpi-support
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

[Laurent Bonnaud (laurent-bonnaud)]

This bug is still in quantal (the package version is the same as in precise).

[Nick Wellnhofer (nick-aevum)]

I had a deeper look into this issue, and this is what I think is going on: If you switched to Debian-style dependency-based boot ordering on a very old Ubuntu release and kept upgrading to newer releases, somewhere along the line the support for dependency-based boot ordering was dropped in Ubuntu. I was able to recover by simply executing:

$ touch /etc/init.d/.legacy-bootordering

Use at your own risk.

[Laurent Bonnaud (laurent-bonnaud)]

Indeed, the presence or absence of /etc/init.d/.legacy-bootordering changes the error message:

 - without the file:

# dpkg-reconfigure acpi-support
Can't exec "insserv": No such file or directory at /usr/sbin/update-rc.d line 417.
update-rc.d: error: insserv rejected the script header

 - with the file:

# dpkg-reconfigure acpi-support
update-rc.d: warning: /etc/init.d/acpi-support missing LSB information
update-rc.d: see <http://wiki.debian.org/LSBInitScripts>

In any case there is still an error message.

[Laurent Bonnaud (laurent-bonnaud)]

Here is another way to look at this bug:

# /usr/share/insserv/check-initd-order
error: LSB header missing in /etc/rc2.d/S02acpi-support

[Ari (ari-lp)]

I can confirm this bug on Ubuntu 12.04.2 LTS.

$apt-cache policy acpi-support
acpi-support:
  Installed: 0.140.1
  Candidate: 0.140.1

[Thomas (tom-rosary)]

just appeared for me too on 12.04.2 LTS

$ /usr/share/insserv/check-initd-order
error: LSB header missing in /etc/rc2.d/S93smfpd
error: LSB header missing in /etc/rc2.d/S99acpi-support

$ apt-cache policy acpi-support
acpi-support:
  Installiert: 0.140.1
  Kandidat: 0.140.1
  Versionstabelle:
 *** 0.140.1 0
        500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.140 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

[Steve Langasek (vorlon)]

This has been fixed in saucy with the removal of the init script in question.