package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In the apt-get output, there are many lines like this:
update-initramfs: deferring update (trigger activated)
insserv: warning: script 'K10runmbbservice' missing LSB tags and overrides
insserv: warning: script 'runmbbservice' missing LSB tags and overrides
insserv: There is a loop between service plymouth and procps if started
insserv: loop involving service procps at depth 2
insserv: loop involving service udev at depth 1
insserv: There is a loop at service plymouth if started
insserv: There is a loop at service runmbbservice if started
insserv: There is a loop between service runmbbservice and hwclock if started
insserv: loop involving service hwclock at depth 1
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv: loop involving service bluetooth at depth 1
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 3
insserv: loop involving service mountdevsubfs at depth 1
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service runmbbservice and udev if started
insserv: loop involving service mountkernfs at depth 1
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
[...]
insserv: Starting runmbbservice depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service runmbbservice and dns-clean if started
insserv: loop involving service dns-clean at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header
dpkg: error processing package udev (--configure):
subprocess installed post-installation script returned error exit status 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: udev 229-4ubuntu10
ProcVersionSign
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CustomUdevRuleF
Date: Sun Oct 2 09:21:27 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2015-12-25 (281 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: MSI MS-7971
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: systemd
Title: package udev 229-4ubuntu10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-05-22 (132 days ago)
dmi.bios.date: 09/07/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.40
dmi.board.
dmi.board.name: Z170A PC MATE (MS-7971)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7971
dmi.product.
dmi.sys.vendor: MSI
tags: | removed: need-duplicate-check |
Further analysis shows that the system has an (empty?!?) file runmbservice in the /etc/init.d/ directory, plus links in the rcX.d directories:
root@bto03:~# find /etc/ | grep runmbbservice | xargs ls -ld d/runmbbservice d/K10runmbbserv ice -> /etc/init. d/runmbbservice d/S99runmbbserv ice -> /etc/init. d/runmbbservice d/K10runmbbserv ice -> /etc/init. d/runmbbservice d/S99runmbbserv ice -> /etc/init. d/runmbbservice d/K10runmbbserv ice -> /etc/init. d/runmbbservice d/S99runmbbserv ice -> /etc/init. d/runmbbservice d/K10runmbbserv ice -> /etc/init. d/runmbbservice d/S99runmbbserv ice -> /etc/init. d/runmbbservice
-rwxr-xr-x 1 root root 0 Sep 28 11:44 /etc/init.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc2.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc2.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc3.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc3.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc4.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc4.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc5.
lrwxrwxrwx 1 root root 25 Sep 28 11:44 /etc/rc5.
Removing this (useless?!?) file and links turns the "apt-get upgrade" into this:
root@bto03:~# apt-get upgrade drivers- common (1:0.4.17.2) ... img-4.4. 0-36-generic i915/kbl_ dmc_ver1. bin for module i915_bpo i915/skl_ guc_ver6. bin for module i915_bpo
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up udev (229-4ubuntu10) ...
addgroup: The group `input' already exists as a system group. Exiting.
update-initramfs: deferring update (trigger activated)
Setting up ubuntu-
Setting up ifupdown (0.8.10ubuntu1.1) ...
Processing triggers for initramfs-tools (0.122ubuntu8.1) ...
update-initramfs: Generating /boot/initrd.
W: Possible missing firmware /lib/firmware/
W: Possible missing firmware /lib/firmware/
root@bto03:~#