no se puede instalar nada usando apt-get debido a insserv

Cada vez que intento instalar algo usando apt-getrecibo los mensajes de error relacionados insserv. He intentado instalar muchos paquetes diferentes, pero todo da el mismo error. Y aparentemente, el paquete CUPS está haciendo / ha hecho algo porque cada mensaje de error lo involucra. Los siguientes son los errores que se muestran cuando ejecuté sudo apt-get install wine1.8 winetricks:

After this operation, 716 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up util-linux (2.27.1-6ubuntu3.1) ...
insserv: warning: script 'K01cups-browsed' missing LSB tags and overrides
insserv: warning: script 'cups-browsed' missing LSB tags and overrides
insserv: There is a loop at service plymouth if started
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: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Max recursions depth 99 reached
insserv:  loop involving service speech-dispatcher at depth 1
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service cups-browsed and hwclock if started
insserv:  loop involving service hwclock at depth 1
insserv: There is a loop at service cups-browsed if started
insserv:  loop involving service networking at depth 4
insserv: There is a loop between service plymouth and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service mountdevsubfs at depth 2
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: There is a loop between service cups-browsed and dns-clean if started
insserv:  loop involving service dns-clean at depth 1
insserv: Starting cups-browsed depends on plymouth and therefore on system facility `$all' which can not be true!
insserv: Starting cups-browsed depends on plymouth 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
dpkg: error processing package util-linux (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 util-linux
E: Sub-process /usr/bin/dpkg returned an error code (1)

El contenido de /etc/insserv.conf es el siguiente:

#
# All local filesystems are mounted (done during boot phase)
#
$local_fs   +umountfs

#
# Low level networking (ethernet card)
#
$network    +networking

#
# Named is operational
#
$named      +named +dnsmasq +lwresd +bind9 +unbound $network

#
# All remote filesystems are mounted (note in some cases /usr may
# be remote. Most applications that care will probably require
# both $local_fs and $remote_fs)
#
$remote_fs  $local_fs +umountnfs +sendsigs

#
# System logger is operational
#
$syslog     +rsyslog +sysklogd +syslog-ng +dsyslog +inetutils-syslogd

#
# The system time has been set correctly
#
$time       +hwclock

#
# Services which need to be interactive
#
<interactive>   glibc udev console-screen keymap keyboard-setup console-setup cryptdisks cryptdisks-early checkfs-loop

salida para $ apt-cache policy cups-browsed plymouth dns-clean

cups-browsed:
  Installed: 1.8.3-2ubuntu3
  Candidate: 1.8.3-2ubuntu3
  Version table:
 *** 1.8.3-2ubuntu3 500
        500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
plymouth:
  Installed: 0.9.2-3ubuntu13
  Candidate: 0.9.2-3ubuntu13.1
  Version table:
     0.9.2-3ubuntu13.1 500
        500 http://in.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 0.9.2-3ubuntu13 500
        500 http://in.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
N: Unable to locate package dns-clean

No conozco ninguna otra información relevante que pueda ser importante para resolver esto, por eso no la he publicado. Si desea más información, no dude en preguntar.

— Pranjal
fuente

Verifique para asegurarse de que no tiene nada tonto en la configuración de insserv, particularmente /etc/insserv.conf y /etc/insserv.conf.d/*. Si no está seguro, agregue el contenido de esos archivos a la pregunta.

— un CVn

@ MichaelKjörling He agregado el contenido de/etc/insserv.conf

— Pranjal

¿Qué versión de Ubuntu? ¿Ha agregado algún software que no sea un paquete de los repositorios "estándar"? ¿Qué pasa con la edición reciente de los archivos del sistema?

— roaima

Necesitas mirar los archivos /etc/insserv.conf.d. Publique el contenido de cualquier archivo cuyo nombre contenga dns, plymoutho cups. O tal vez otros archivos, el problema no es con un solo archivo sino con ellos en combinación, crean un bucle donde A debe iniciarse antes de que B deba iniciarse antes de que C deba ser ... debe iniciarse antes de A.

— Gilles 'SO- deja de ser malvado '

@Gilles No hay archivos en/etc/insserv.conf.d

— Pranjal

En primer lugar, el problema es que estás atrapado en la secuencia de arranque.

El método de secuencia de arranque se decide durante la instalación o las actualizaciones. Si no hay bucles en las dependencias declaradas por los encabezados LSB de todos los init.dscripts instalados y no hay scripts obsoletos , el sistema se convierte en una secuencia de arranque basada en la dependencia.

Tenemos que verificar

Bucle en dependencias : ocurre cuando>
- Faltan etiquetas LSB en algunas secuencias de comandos o error en las etiquetas LSB como falta Required-Start:o Required-Stop:etiquetas
- Algunas secuencias de comandos dependen de otras secuencias de comandos que dependen de la instalación del sistema $allque no puede ser cierto. Debido a que las secuencias de comandos que dependen de $allse cargan en último lugar al inicio Como se carga al final, nada puede depender de ello. Por lo tanto, desordena la secuencia de arranque basada en la dependencia.
Guiones obsoletos : ocurren cuando
- Algunos paquetes se están actualizando a versiones más nuevas que pueden no usar un script /etc/init.d/y el responsable puede haber perdido el código para eliminar el script anterior. No es nuestro error.

La causa es seguramente extranjera. Vaya /etc/init.dy vea el archivo correspondiente cups-browsedy confirme que tiene un comentario LSB con Provides, Required-Start/ Required-Stop(al menos vacío), Default-Start/ Default-Stopen él como a continuación.

### BEGIN INIT INFO
# Provides :          cups-browsed
# Required-Start :
# Required-Stop :
# Default-Start :     2 3 4 5
# Default-Stop  :     0 1 6
# Short-Description : Some info
# Description :       Some more info
### END INIT INFO

Si no está allí, tiene la opción de agregar el comentario LSB o purgar completamente el programa y los scripts /etc/init.d/y los /etc/rc?archivos. Espero que esto funcione.

No dude en preguntar si tiene alguna duda.

— mc al cuadrado
fuente

Ha pasado más de un mes después de que publiqué la pregunta. Como no obtuve ninguna respuesta en ese momento, purgué el programa y todo funcionó. Ahora tengo nuevamente instalado cupsy misteriosamente todo está funcionando bien. Todavía estoy aceptando la suya como respuesta correcta porque ha mencionado la sugerencia del programa de purga en ella.

— Pranjal

Tengo el mismo problema. Revisé el /etc/init.d/cups-browsedarchivo y ya tiene los comentarios como mencionaste. ¿Cómo purgo el programa y los scripts?

— Mohan

Ok, entiendo, pero lo que no entiendo es ¿por qué? Estos encabezados INIT INFO habían existido durante más de una década, pero a nadie le importaban. Desde un punto de vista humano, tener dos dígitos del 0 al 99 es una forma muy clara de establecer el orden de inicio, pero ahora tengo que rastrear los encabezados de Inicio obligatorio. ¿Por qué? A veces menos es más.

— soger

Ubuntu no le gustan los espacios en blanco antes de los dos puntos.

— tak3shi