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

[Gabriel Filion]

On 10/10/15 08:17 AM, Simon McVittie wrote:
> 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...

>> 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?

oh! right I hadn't seen that part when reporting. judging from the
timestamp that must've been something that I tried when looking at
possible resolution avenues from other issues.

> 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
> * 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

those are attached to the email.

I can see that systemd was upgraded to 227-1 before the shutdown/boot
that showed errors.

> * the next reboot (use syslog) after each dbus upgrade

The best marker I could find in syslog for this was rsyslogd start tags.
I'm attaching those that I found.

>> 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.

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.

after that I tried a couple of things to fix the issue and wasn't
successful. I later downloaded packages dbus and libdbus-1-3 1.10.0-2
for downgrading them. They were installed around 19:something, then I
rebooted and things were back in order (e.g. gdm3 was able to start)


fwiw there's a bug report that is very similar to mine:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788178

but I don't recall seeing the same error while upgrading. Also, I was
not running policykit from experimental when the problems showed up, and
the issues receded when downgrading dbus and libdbus.

-- 
Gabriel Filion
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dbus_dpkg.log
Type: text/x-log
Size: 239520 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151010/602e2da6/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: reboots.log
Type: text/x-log
Size: 1800 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151010/602e2da6/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20151010/602e2da6/attachment-0001.sig>