package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Gary Caine]

This is using 17.10 so I believe it is different than the 1633217 bug report

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: avahi-daemon 0.6.32-1ubuntu1.1
ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Fri Apr 6 08:18:27 2018
DpkgHistoryLog:
 Start-Date: 2018-04-06 08:18:02
 Upgrade: libvncclient1:amd64 (0.9.11+dfsg-1, 0.9.11+dfsg-1ubuntu0.1), libraw16:amd64 (0.18.2-2ubuntu0.1, 0.18.2-2ubuntu0.2), libavahi-glib1:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common-data:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-common3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-ui-gtk3-0:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-daemon:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-core7:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), avahi-autoipd:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), python3-crypto:amd64 (2.6.1-7build2, 2.6.1-7ubuntu0.1), avahi-utils:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), libavahi-client3:amd64 (0.6.32-1ubuntu1, 0.6.32-1ubuntu1.1), hdparm:amd64 (9.51+ds-1, 9.51+ds-1ubuntu0.1)
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-01-07 (89 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt 1.5.1
SourcePackage: avahi
Title: package avahi-daemon 0.6.32-1ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Trent Lloyd (lathiat)]

Thanks for the report.

 How did this happen, was it during a package upgrade for a normal installation or is this a new install, etc. If a new install, describe which install media download and options you used. Or were you installing avahi-daemon or some other package using apt install, etc.

[Trent Lloyd (lathiat)]

Looking at your logs, generally it seems like dbus is broken for some reason.

Would also be great to check it's status:
# systemctl status dbus

[Gary Caine (skgary)]

This happened when I did fix broken packages after going into advanced option from grub

here's the output of dbus

 dbus.service - D-Bus System Message Bus
   Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor preset: enab
   Active: active (running) since Wed 2018-04-11 07:53:20 CST; 5min ago
     Docs: man:dbus-daemon(1)
 Main PID: 733 (dbus-daemon)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/dbus.service
           └─733 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nop

Apr 11 07:53:52 gary-System-Product-Name dbus[733]: [system] Successfully activa
Apr 11 07:53:55 gary-System-Product-Name dbus[733]: [system] Failed to activate
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Successfully activa
Apr 11 07:54:09 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:54:34 gary-System-Product-Name dbus[733]: [system] Failed to activate
Apr 11 07:57:18 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:57:43 gary-System-Product-Name dbus[733]: [system] Failed to activate
Apr 11 07:58:23 gary-System-Product-Name dbus[733]: [system] Activating via syst
Apr 11 07:58:48 gary-System-Product-Name dbus[733]: [system] Failed to activate

[Gary Caine (skgary)]

I replied on launchpad but in answer to your 2 questions.

I did the fix broken pages from advanced options from grub, and I'm
pretty sure that this is what caused it.

 From dbus status

  dbus.service - D-Bus System Message Bus
    Loaded: loaded (/lib/systemd/system/dbus.service; static; vendor
preset: enab
    Active: active (running) since Wed 2018-04-11 07:53:20 CST; 5min ago
      Docs: man:dbus-daemon(1)
  Main PID: 733 (dbus-daemon)
     Tasks: 1 (limit: 4915)
    CGroup: /system.slice/dbus.service
            └─733 /usr/bin/dbus-daemon --system --address=systemd:
--nofork --nop

Apr 11 07:53:52 gary-System-Product-Name dbus[733]: [system]
Successfully activa
Apr 11 07:53:55 gary-System-Product-Name dbus[733]: [system] Failed to
activate
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system] Activating
via syst
Apr 11 07:54:01 gary-System-Product-Name dbus[733]: [system]
Successfully activa
Apr 11 07:54:09 gary-System-Product-Name dbus[733]: [system] Activating
via syst
Apr 11 07:54:34 gary-System-Product-Name dbus[733]: [system] Failed to
activate
Apr 11 07:57:18 gary-System-Product-Name dbus[733]: [system] Activating
via syst
Apr 11 07:57:43 gary-System-Product-Name dbus[733]: [system] Failed to
activate
Apr 11 07:58:23 gary-System-Product-Name dbus[733]: [system] Activating
via syst
Apr 11 07:58:48 gary-System-Product-Name dbus[733]: [system] Failed to
activate

On 2018-04-11 06:39 AM, Trent Lloyd wrote:
> Looking at your logs, generally it seems like dbus is broken for some
> reason.
>
> Would also be great to check it's status:
> # systemctl status dbus
>