[Pkg-utopia-maintainers] Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

[Simon McVittie]

Control: tags 801425 + moreinfo

On 10/10/15 00:51, Gabriel Filion wrote:
> I'm running sid and this morning I performed an apt-get upgrade and a
> dist-upgrade. This pulled in dbus 1.10.0-3.

I'm surprised by the upgrade from 1.10.0-2 to 1.10.0-3 having an effect,
because very little changed between these versions - I changed how the
special "debug build" in dbus-1-dbg is set up, but that build is not on
$PATH, and should never be used unless you specifically set it up to be
used. I'll double-check the diff to see if anything is wrong there...

I wouldn't have been so surprised if upgrading from 1.8 to 1.10 caused
issues, because that was quite a large jump. Because dbus-daemon
--system doesn't support being restarted at runtime, it is fairly likely
that any issues caused by the upgrade would either persist until the
next reboot, or not be noticed until after the next reboot.

<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794723> looks vaguely
similar, and indicates that there's some bad interaction going on
between recent systemd, policykit-1 and dbus; but I haven't seen that
happen on my systems, so I'll need some more information to track down
where.

Please check /var/log/dpkg.log* and /var/log/syslog*, and tell me:

* any lines from dpkg.log* involving dbus, going back to the upgrade
  from 1.8 to 1.10 if you can
* the next reboot (use syslog) after each dbus upgrade
* any lines from dpkg.log* involving systemd, going back as far as
  the upgrade from <= 219 to >= 220 if you can
* any lines from dpkg.log* involving policykit-1 over the same range
  of dates/times

> Upon restart, systemd was hanging for a bunch of time with messages like the
> following:

When you say "Upon restart", do you mean you rebooted after upgrading
dbus, as the postinst recommends? As noted above, I'm interested in the
order of events and the versions involved.

> Downgrading dbus and libdbus-1-3 to 1.10.0-2 fixed the issue, so it is clearly
> a regression in the -3 version.

What else, if anything, did you do between this problem appearing, and
this problem being solved? I'm interested in: reboots, and upgrading,
downgrading or reinstalling systemd, dbus or policykit-1.

> Versions of policykit:
> ii  policykit-1        0.113-1
> ii  policykit-1-gnome  0.105-2

I notice you're running policykit-1 from experimental. Has that been
true since before you had any problems with systemd/policykit-1/dbus?

Thanks,
    S