[Online-Update] delllctservice* init scripts are missing LSB headers

Bug #1605952 reported by Mauricio Maluff Masi
44
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Dell Sputnik
Incomplete
High
Shih-Yuan Lee

Bug Description

I upgraded my XPS 13 today from 14.04 to 16.04.1. After my upgrade, any time I ran one of the following commands:
apt-get upgrade
dpkg --configure -a
apt-get -f install

I would get a ton of dpkg errors that looked like this:

insserv: warning: script 'K01delllctservice' missing LSB tags and overrides
insserv: warning: script 'delllctservicecontent' missing LSB tags and overrides
insserv: warning: script 'delllctservice' missing LSB tags and overrides
insserv: Starting delllctservice depends on grub-common and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service delllctservice and grub-common if started
insserv: loop involving service grub-common at depth 4
insserv: loop involving service delllctservice at depth 1
insserv: Starting delllctservice depends on grub-common and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service delllctservice and grub-common if started
insserv: Starting delllctservice depends on grub-common and therefore on system facility `$all' which can not be true!
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

Somehow in the upgrade process, my runtime dependencies got messed up, at least in part because these scripts are missing LSB headers. dpkg failed to process most of my packages with init scripts. Moving delllctservice and delllctservicecontent out of /etc/init.d, then running the following seemed to fix the problem:
dpkg --configure -a
apt-get -f install

After everything was fixed, moving them back to /etc/init.d caused no further issues.

I'm sure this wasn't my only problem, there were a lot of other things that probably went wrong with my upgrade that led to this. But the lack of LSB headers in these scripts certainly contributed to my problem, and I think it'd be a good safeguard to add some.

description: updated
summary: - dellctservice* init scripts are missing LSB headers
+ delllctservice* init scripts are missing LSB headers
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote : Re: delllctservice* init scripts are missing LSB headers

And I found at least one other person who suffered from this, so I'm not completely alone:
http://askubuntu.com/questions/680026/ubuntu-resolve-unmet-dependencies

Pascal Morin (pcm689)
Changed in dell-sputnik:
assignee: nobody → Shih-Yuan Lee (fourdollars)
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

Hi Mauricio,

Could you help to provide the output of `sudo dmidecode -s system-product-name` for us to confirm which XPS 13 you are using?

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote : Re: [Bug 1605952] Re: delllctservice* init scripts are missing LSB headers

Here you go!

XPS 13 9343

I also saved off the output of dpkg --configure -all, if you'd like it.
I've attached it here.

On Thu, Jul 28, 2016 at 10:45 PM Shih-Yuan Lee <email address hidden>
wrote:

> Hi Mauricio,
>
> Could you help to provide the output of `sudo dmidecode -s system-
> product-name` for us to confirm which XPS 13 you are using?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1605952
>
> Title:
> delllctservice* init scripts are missing LSB headers
>
> Status in Dell Sputnik:
> New
>
> Bug description:
> I upgraded my XPS 13 today from 14.04 to 16.04.1. After my upgrade, any
> time I ran one of the following commands:
> apt-get upgrade
> dpkg --configure -a
> apt-get -f install
>
> I would get a ton of dpkg errors that looked like this:
>
> insserv: warning: script 'K01delllctservice' missing LSB tags and
> overrides
> insserv: warning: script 'delllctservicecontent' missing LSB tags and
> overrides
> insserv: warning: script 'delllctservice' missing LSB tags and overrides
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: There is a loop between service delllctservice and grub-common
> if started
> insserv: loop involving service grub-common at depth 4
> insserv: loop involving service delllctservice at depth 1
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: There is a loop between service delllctservice and grub-common
> if started
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: exiting now without changing boot order!
> update-rc.d: error: insserv rejected the script header
>
> Somehow in the upgrade process, my runtime dependencies got messed up,
> at least in part because these scripts are missing LSB headers. dpkg failed
> to process most of my packages with init scripts. Moving delllctservice and
> delllctservicecontent out of /etc/init.d, then running the following seemed
> to fix the problem:
> dpkg --configure -a
> apt-get -f install
>
> After everything was fixed, moving them back to /etc/init.d caused no
> further issues.
>
> I'm sure this wasn't my only problem, there were a lot of other things
> that probably went wrong with my upgrade that led to this. But the
> lack of LSB headers in these scripts certainly contributed to my
> problem, and I think it'd be a good safeguard to add some.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1605952/+subscriptions
>

Chih-Hsyuan Ho (chih)
Changed in dell-sputnik:
importance: Undecided → High
Changed in dell-sputnik:
status: New → In Progress
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote : Re: delllctservice* init scripts are missing LSB headers

I don't see any problem when upgrading to Ubuntu 16.04.1 by the image we provided to Dell.
It seems that Dell put something else breaking the upgrade process.

Changed in dell-sputnik:
status: In Progress → Incomplete
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

What I tested is somerville-trusty-amd64-iso-20140620-0.iso + dino_A14.fish.tar.gz.

Revision history for this message
foggy (chang-liu4) wrote :

Hi Mauricio

Could you help to confirm if the MyLinux APP included in your test system?thanks!

Revision history for this message
foggy (chang-liu4) wrote :

Hi kent & Shih,

I want to confirm 2 item:
1. Is the issue caused by the deb package I send you,If you remove the deb package,is it OK?
2. If we can confirm it is caused by deb package,could canonical find way to remove the package from Ubuntu 14.04SP1 and earlier version with online update?

Revision history for this message
Chih-Hsyuan Ho (chih) wrote :

@Foggy, our feedback to your questions:

1. The upgrade issue is caused by the extra "MyLinux APP" for sure.
2. We can either provide an empty package of the same name to overwrite it or a better way is for Dell to provide another version of such package to us, and we release it from the Dino specific online archive.

Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote : Re: [Bug 1605952] Re: delllctservice* init scripts are missing LSB headers

My computer definitely has that package installed, and these scripts
definitely belong to it.

On Wed, Aug 10, 2016, 01:55 Chih-Hsyuan Ho <email address hidden> wrote:

> @Foggy, our feedback to your questions:
>
> 1. The upgrade issue is caused by the extra "MyLinux APP" for sure.
> 2. We can either provide an empty package of the same name to overwrite it
> or a better way is for Dell to provide another version of such package to
> us, and we release it from the Dino specific online archive.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1605952
>
> Title:
> delllctservice* init scripts are missing LSB headers
>
> Status in Dell Sputnik:
> Incomplete
>
> Bug description:
> I upgraded my XPS 13 today from 14.04 to 16.04.1. After my upgrade, any
> time I ran one of the following commands:
> apt-get upgrade
> dpkg --configure -a
> apt-get -f install
>
> I would get a ton of dpkg errors that looked like this:
>
> insserv: warning: script 'K01delllctservice' missing LSB tags and
> overrides
> insserv: warning: script 'delllctservicecontent' missing LSB tags and
> overrides
> insserv: warning: script 'delllctservice' missing LSB tags and overrides
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: There is a loop between service delllctservice and grub-common
> if started
> insserv: loop involving service grub-common at depth 4
> insserv: loop involving service delllctservice at depth 1
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: There is a loop between service delllctservice and grub-common
> if started
> insserv: Starting delllctservice depends on grub-common and therefore on
> system facility `$all' which can not be true!
> insserv: exiting now without changing boot order!
> update-rc.d: error: insserv rejected the script header
>
> Somehow in the upgrade process, my runtime dependencies got messed up,
> at least in part because these scripts are missing LSB headers. dpkg failed
> to process most of my packages with init scripts. Moving delllctservice and
> delllctservicecontent out of /etc/init.d, then running the following seemed
> to fix the problem:
> dpkg --configure -a
> apt-get -f install
>
> After everything was fixed, moving them back to /etc/init.d caused no
> further issues.
>
> I'm sure this wasn't my only problem, there were a lot of other things
> that probably went wrong with my upgrade that led to this. But the
> lack of LSB headers in these scripts certainly contributed to my
> problem, and I think it'd be a good safeguard to add some.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/dell-sputnik/+bug/1605952/+subscriptions
>

Kent Lin (kent-jclin)
tags: added: online-update
Revision history for this message
Mauricio Maluff Masi (mmaluff) wrote : Re: delllctservice* init scripts are missing LSB headers

I've also noticed these errors pop up frequently when I run apt upgrade:

insserv: warning: script 'delllctservicecontent' missing LSB tags and overrides
insserv: warning: script 'delllctservice' missing LSB tags and overrides

Though it hasn't caused any functional issues that I've noticed.

Revision history for this message
Kent Lin (kent-jclin) wrote :

new package provided by Dell Kevin

Revision history for this message
Kent Lin (kent-jclin) wrote :
summary: - delllctservice* init scripts are missing LSB headers
+ [Online-Update] delllctservice* init scripts are missing LSB headers
Revision history for this message
Kent Lin (kent-jclin) wrote :
Revision history for this message
Kent Lin (kent-jclin) wrote :
Revision history for this message
Shih-Yuan Lee (fourdollars) wrote :

The Debian source package in comment #13 & #14 is not qualified.

$ pbuilder-dist xenial amd64 build mylinux_3.4.dsc
... [omit]
I: Copying back the cached apt archive contents
I: Copying source file
I: copying [mylinux_3.4.dsc]
I: copying [./mylinux_3.4.tar.gz]
I: Extracting source
dpkg-source: warning: extracting unsigned source package (mylinux_3.4.dsc)
dpkg-source: info: extracting mylinux in mylinux-3.4
dpkg-source: info: unpacking mylinux_3.4.tar.gz
I: Building the package
I: Running cd /build/*/ && env PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us -uc -j8 -rfakeroot
dpkg-buildpackage: warning: debian/changelog(l52): invalid abbreviated month name 'June'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
dpkg-buildpackage: warning: debian/changelog(l52): cannot parse non-comformant date '24 June 2014 13:37:00 +0800'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
dpkg-buildpackage: source package mylinux
dpkg-buildpackage: source version 3.4
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by scott <scott@unknown>
 dpkg-source --before-build mylinux-3.4
dpkg-buildpackage: host architecture amd64
dpkg-source: warning: mylinux-3.4/debian/changelog(l52): invalid abbreviated month name 'June'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
dpkg-source: warning: mylinux-3.4/debian/changelog(l52): cannot parse non-comformant date '24 June 2014 13:37:00 +0800'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
 fakeroot debian/rules clean
dh clean
dh: warning: debian/changelog(l52): invalid abbreviated month name 'June'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
dh: warning: debian/changelog(l52): cannot parse non-comformant date '24 June 2014 13:37:00 +0800'
LINE: -- scott <scott@unknown> Tue, 24 June 2014 13:37:00 +0800
Error parsing time at /usr/lib/x86_64-linux-gnu/perl/5.22/Time/Piece.pm line 469.
debian/rules:13: recipe for target 'clean' failed
make: *** [clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
I: copying local configuration
E: Failed autobuilding of package
I: unmounting dev/pts filesystem
I: unmounting run/shm filesystem
I: unmounting proc filesystem
I: cleaning the build env
I: removing directory /var/cache/pbuilder/build/30135 and its subdirectories

Revision history for this message
Jm (jmdelehaye) wrote :

Workaround :

Add these lines in /etc/init.d/delllctservice and /etc/init.d/delllctservicecontent, just below the first line (#!/bin/sh) :

### BEGIN INIT INFO
# Provides: delllctservice
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: Starts delllctservice
# Description: delllctservice is needed by "Dell My Linux" application
### END INIT INFO

Source : https://forum.ubuntu-fr.org/viewtopic.php?id=1827251

tags: added: trusty
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.