Setting up acpid (1:2.0.28-1ubuntu1) ...
Job for acpid.service failed because of unavailable resources or another system error.
See "systemctl  status acpid.service" and "journalctl  -xe" for details.
invoke-rc.d: initscript acpid, action "start" failed.
● acpid.service - ACPI event daemon
   Loaded: loaded (/lib/systemd/system/acpid.service; disabled; vendor preset: enabled)
   Active: failed (Result: resources)

Mar 29 20:26:47 richard-Z97M-D3H systemd[1]: acpid.service: Got no socket.
Mar 29 20:26:47 richard-Z97M-D3H systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument
Mar 29 20:26:47 richard-Z97M-D3H systemd[1]: Failed to start ACPI event daemon.
Mar 29 20:26:47 richard-Z97M-D3H systemd[1]: acpid.service: Unit entered failed state.
Mar 29 20:26:47 richard-Z97M-D3H systemd[1]: acpid.service: Failed with result 'resources'.
Mar 29 20:29:27 richard-Z97M-D3H systemd[1]: acpid.service: Got no socket.
Mar 29 20:29:27 richard-Z97M-D3H systemd[1]: acpid.service: Failed to run 'start' task: Invalid argument
Mar 29 20:29:27 richard-Z97M-D3H systemd[1]: Failed to start ACPI event daemon.
Mar 29 20:29:27 richard-Z97M-D3H systemd[1]: acpid.service: Failed with result 'resources'.
dpkg: error processing package acpid (--configure):
 subprocess installed post-installation script returned error exit status 1
Setting up blueman (2.0.4-1ubuntu3) ...
dbus.service is not active, cannot reload.
invoke-rc.d: initscript dbus, action "reload" failed.
dpkg: error processing package blueman (--configure):
 subprocess installed post-installation script returned error exit status 1