Bug#771417: bogus dpkg error, now endless loop on dbus configuration

2014-11-29 Thread Eduard Bloch
Package: dpkg
Version: 1.17.22
Severity: grave

Hello,

today I tried to dist-upgrade my system (sid) starting from a package
state of a couple of weeks ago. First apt reported a failed dpkg right
in the middle of the upgrade process without displaying any visible
error messages. Now when I run apt-get -f install or attempt to
install some missing package explicitly, it ends up in a loop where dpkg
runs maintainer scripts on dbus without end. Here is dpkg.log and some
console output:

2014-11-29 11:23:24 startup archives unpack
2014-11-29 11:23:28 upgrade debianutils:amd64 4.4 4.4+b1
2014-11-29 11:23:28 status half-configured debianutils:amd64 4.4
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4
2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4
2014-11-29 11:23:28 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:28 status half-installed debianutils:amd64 4.4
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:28 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:28 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:28 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:31 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:32 startup packages configure
2014-11-29 11:23:32 configure debianutils:amd64 4.4+b1 keine
2014-11-29 11:23:32 status unpacked debianutils:amd64 4.4+b1
2014-11-29 11:23:32 status half-configured debianutils:amd64 4.4+b1
2014-11-29 11:23:32 status installed debianutils:amd64 4.4+b1
2014-11-29 11:23:32 startup archives unpack
2014-11-29 11:23:33 upgrade bash:amd64 4.3-11 4.3-11+b1
2014-11-29 11:23:33 status half-configured bash:amd64 4.3-11
2014-11-29 11:23:33 status unpacked bash:amd64 4.3-11
2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:33 status triggers-pending menu:amd64 2.1.47
2014-11-29 11:23:33 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:33 status triggers-pending install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:33 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:34 status half-installed bash:amd64 4.3-11
2014-11-29 11:23:34 status triggers-awaited menu:amd64 2.1.47
2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:34 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:34 trigproc menu:amd64 2.1.47 keine
2014-11-29 11:23:34 status half-configured menu:amd64 2.1.47
2014-11-29 11:23:36 status installed menu:amd64 2.1.47
2014-11-29 11:23:36 trigproc install-info:amd64 5.2.0.dfsg.1-5 keine
2014-11-29 11:23:36 status half-configured install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:38 status installed install-info:amd64 5.2.0.dfsg.1-5
2014-11-29 11:23:38 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:38 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:39 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:40 startup packages configure
2014-11-29 11:23:40 configure bash:amd64 4.3-11+b1 keine
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status unpacked bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status half-configured bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status installed bash:amd64 4.3-11+b1
2014-11-29 11:23:40 status triggers-pending menu:amd64 2.1.47
2014-11-29 11:23:40 status triggers-awaited menu:amd64 2.1.47
2014-11-29 11:23:40 trigproc menu:amd64 2.1.47 keine
2014-11-29 11:23:40 status half-configured menu:amd64 2.1.47
2014-11-29 11:23:42 status installed menu:amd64 2.1.47
2014-11-29 11:23:43 startup archives unpack
2014-11-29 11:23:44 upgrade bsdutils:amd64 1:2.25.2-2 1:2.25.2-3
2014-11-29 11:23:44 status half-configured bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status triggers-pending man-db:amd64 2.7.0.2-2
2014-11-29 11:23:44 status half-installed bsdutils:amd64 1:2.25.2-2
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:44 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:44 trigproc man-db:amd64 2.7.0.2-2 keine
2014-11-29 11:23:44 status half-configured man-db:amd64 2.7.0.2-2
2014-11-29 11:23:45 status installed man-db:amd64 2.7.0.2-2
2014-11-29 11:23:46 startup packages configure
2014-11-29 11:23:46 configure bsdutils:amd64 1:2.25.2-3 keine
2014-11-29 11:23:46 status unpacked bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 status half-configured bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 status installed bsdutils:amd64 1:2.25.2-3
2014-11-29 11:23:46 startup archives unpack
2014-11-29 11:23:47 upgrade libc-dev-bin:amd64 2.19-12 2.19-13
2014-11-29 11:23:47 status half-configured libc-dev-bin:amd64 2.19-12
2014-11-29 11:23:47 status unpacked libc-dev-bin:amd64 2.19-12
2014-11-29 11:23:47 status 

Bug#771417: bogus dpkg error, now endless loop on dbus configuration

2014-11-29 Thread Ira Rice
Could this just be related to bug 771290
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771290? Because holding
off on installing gnome-bluetooth, which would have caused me to trigger
that bug, made it so that I didn't encounter this bug, and dpkg appears to
work just fine.

To me, it just sounds like that update broke dbus, which in turn broke
dpkg, and because of that, dpkg is not what's causing the problem here.

Just my two cents, in any case.