Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

[Simon McVittie]

On 10/10/15 17:38, Gabriel Filion wrote:
> Laptop was booted and working fine since previous afternoon.
> The upgrade/dist-upgrade that brought in dbus 1.10.0-3 was done on the
> morning of oct 9th around 7:something, then I shutdown around 8:00, and
> booted again around 9:40 and I was seeing the error mentioned in my
> original report.

Hmm. Your logs suggest that you started to upgrade dbus 1.8 to 1.10.0-3
(without going via any intermediate version) on 2015-09-17 at 01:46:40,
and finished that upgrade transaction with dbus successfully installed
at 01:48:13. Presumably you didn't notice anything wrong between then
and the 9th?

On 2015-10-09 at 07:48:00, you started an upgrade of systemd and related
packages, which temporarily dropped dbus down to triggers-pending state
(because systemd installs D-Bus services, which cause a dbus reload to
be triggered). That suggests to me that the systemd upgrade is more
likely to be what triggered the symptoms you described.

At 10:28 it looks as though you reinstalled dbus; presumably none of
what you tried between then and 10:33:18 worked. At around 10:34:46 you
rebooted; at 17:43:47 you downgraded dbus to 1.10.0-2, and at 19:01:34
you rebooted again. I can't help wondering whether it was actually some
other event, not the downgrade to 1.10.0-2, that solved this for you...
perhaps the reboot?

It would be really useful to see any systemd, policykit-1 (polkit)
and/or dbus warnings/errors from 2015-10-09, from your syslog. If you
would prefer not to send that day's syslog to the BTS or spend time
censoring it, you can send it to me by private email (compressed if it's
large), and I'll make sure to only quote the relevant debug details on
the bug.

    S