Simon McVittie wrote: > On Thu, 06 Jul 2017 at 09:58:35 -0400, Joey Hess wrote: > > I ran apt-get dist-upgrade to unstable today > > What state were you upgrading from? > > What version of `dbus-daemon --system` was running on your system? Your > apt logs might help to work this out - it will be whatever version was > present during the most recent boot before the problematic upgrade. > > I would also like to know the sequence of upgrades of the dbus package > since that boot (again, please look in your apt logs).
Last boot was 2017-06-06 16:45:08. 2017-05-30 15:20:42 trigproc dbus:amd64 1.10.18-1 <none> 2017-05-30 15:20:42 status half-configured dbus:amd64 1.10.18-1 2017-05-30 15:20:42 status installed dbus:amd64 1.10.18-1 2017-06-11 10:45:07 status triggers-pending dbus:amd64 1.10.18-1 2017-06-11 10:45:07 status triggers-pending dbus:amd64 1.10.18-1 2017-06-11 10:47:44 trigproc dbus:amd64 1.10.18-1 <none> 2017-06-11 10:47:44 status half-configured dbus:amd64 1.10.18-1 2017-06-11 10:47:44 status installed dbus:amd64 1.10.18-1 2017-06-22 16:55:10 status triggers-pending dbus:amd64 1.10.18-1 2017-06-30 14:50:01 upgrade dbus:amd64 1.10.18-1 1.10.20-1 2017-06-30 14:59:53 configure dbus:amd64 1.10.20-1 <none> -- see shy jo
signature.asc
Description: PGP signature
