I can easily reproduce this on a generic ppc64el virtual machine; policykit-1 may have trouble starting up:
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
In my case however it happened with the systemd postinst:
Processing triggers for systemd (219-9ubuntu1) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.8.12-1ubuntu5) ...
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Running the install again appears to eventually let it succeed. Since it's not just reproducible with apport; I'm reassigning this to policykit-1.
I can easily reproduce this on a generic ppc64el virtual machine; policykit-1 may have trouble starting up: .PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop
In my case however it happened with the systemd postinst: .PolicyKit1: Timeout was reached (g-io-error-quark, 24)
Processing triggers for systemd (219-9ubuntu1) ...
Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop
Failed to execute operation: Connection timed out
dpkg: error processing package systemd (--unpack):
subprocess installed post-installation script returned error exit status 1
Processing triggers for dbus (1.8.12-1ubuntu5) ...
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Running the install again appears to eventually let it succeed. Since it's not just reproducible with apport; I'm reassigning this to policykit-1.