package qemu-system-sparc 1:2.5+dfsg-5ubuntu10.9 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Alonso Hernández N.]

I just starting up the computer

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: qemu-system-sparc 1:2.5+dfsg-5ubuntu10.9
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Mar 8 01:52:28 2017
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2017-02-05 (31 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
KvmCmdLine:
 COMMAND STAT EUID RUID PID PPID %CPU COMMAND
 kvm-irqfd-clean S< 0 0 732 2 0.0 [kvm-irqfd-clean]
MachineType: Dell Inc. Latitude E5530 non-vPro
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=UUID=5a66271d-eac1-4dec-9139-2f72bd4e12e3 ro quiet splash vt.handoff=7
SourcePackage: qemu
Title: package qemu-system-sparc 1:2.5+dfsg-5ubuntu10.9 failed to install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 05GRXT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/20/2013:svnDellInc.:pnLatitudeE5530non-vPro:pvr01:rvnDellInc.:rn05GRXT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5530 non-vPro
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[Christian Ehrhardt  (paelzer)]

Hi Alonso,
thank you for taking the time to report the bug and make Ubuntu better.
The reason this showed up on "I just starting up the computer" is that you had an issue to update these packages (might have been done in background, there likely also was a popup) in the past.
Now on reboot the system is notifying you if you are aware or if you want to submit a report.

[Christian Ehrhardt  (paelzer)]

From the log:
onfigurando qemu-system-common (1:2.5+dfsg-5ubuntu10.9) ...
insserv: warning: script 'K10runmbbservice' missing LSB tags and overrides
insserv: warning: script 'runmbbservice' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
insserv: There is a loop between service plymouth and urandom if started
insserv: loop involving service urandom at depth 4
insserv: loop involving service hwclock at depth 3
insserv: There is a loop between service runmbbservice and udev if started
insserv: loop involving service udev at depth 1
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 cups-browsed at depth 2
insserv: There is a loop at service runmbbservice if started
insserv: loop involving service networking at depth 6
insserv: loop involving service mountdevsubfs at depth 3
insserv: loop involving service mountkernfs at depth 1
insserv: loop involving service runmbbservice at depth 1
insserv: exiting now without changing boot order!
update-rc.d: error: insserv rejected the script header

[Christian Ehrhardt  (paelzer)]

No the "weird" one in that list to me seems to be "runmbbservice" I coudn't find that to be part of the distribution.

$ apt-file search runmbbservice
[nothing]

This file seems to be known to cause such issues to all sort of package upgrades.
It is not qemu related at all, in this case it just happened to be the package triggering it.

It seems this script is installed by some out of archive "Mobile Broadband device" code.
And TL;DR this script is just incompatible/broken/however-you-want-to-call-it.

Same issue on another package (recommendation is to remove the broken script, then all works again)
https://answers.launchpad.net/ubuntu/+source/apt/+question/284708

Same issue on Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758060

[Christian Ehrhardt  (paelzer)]

I'd consider this a local config error, and thereby set it to incomplete - don't hesitate to set it back to new if you think this is an Ubuntu bug (and explain why you think so).