Bug#764926: gnome-software: Offline upgrades break boot

[Matthias Klumpp]

2014-10-25 12:22 GMT+02:00 Laurent Bigonville <bigon at debian.org>:
> On Fri, 24 Oct 2014 21:15:24 +0200 Matthias Klumpp
> <matthias at tenstral.net> wrote:
>> 2014-10-24 21:07 GMT+02:00 Laurent Bigonville <bigon at debian.org>:
>> > Package: gnome-software
>> > Followup-For: Bug #764926
>> >
>> > Hi,
>> >
>> > Just tried tonight and it still seems to fail.
>> >
>> > It start the upgrade, the progressbar shows 100% and then nothing is
>> > happening.
>> >
>> > I hit ctrl-alt-del and rebooted, after that gnome-software was
>> > showing a message telling that the transaction failed.
>> Did you find anything interesting in your /var/log/apt/term.log or the
>> systemd journal?
>
> In the apt logs I see no new entries at all.
>
> In the journal I see the progress going to 100%
>
>>
>> > But at least the machine has rebooted properly
>> >
>> > Shouldn't we downgrade the severity?
>> Maybe -but a non-working default upgrade method is still pretty bad
>> (although it's not fatal anymore).
>> We would need some more manpower to nail down this issue (which likely
>> is in PackageKit's aptcc backend), since I am pretty busy with a lot
>> of stuff, with a current focus on getting at least some AppStream data
>> into Debian (not sure if that will work though, many open questions
>> there, and a lot of code which isn't ready yet and needs to be fixed)
>>
>
> I've retried again (after enabling the debug-shell) an I can see the
> following ps output:
>
> root       729  0.0  0.2 239444 18256 ?        S<Lsl 11:55   0:00 /sbin/dmeventd -f
> systemd+   755  0.0  0.0 106220  2540 ?        Ssl  11:55   0:00 /lib/systemd/systemd-timesyncd
> root      1089  0.0  0.0 339696  5628 ?        Ssl  11:55   0:00 /usr/lib/packagekit/pk-offline-update
> root      1090  0.7  0.4 172488 28276 ?        Ssl  11:55   0:00 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid
> message+  1096  0.0  0.0  50600  3532 ?        Ssl  11:55   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
> root      1102  1.4  0.9 431440 59096 ?        Ssl  11:55   0:00 /usr/lib/packagekit/packagekitd
> polkitd   1106  0.0  0.2 520056 13448 ?        Ssl  11:55   0:00 /usr/lib/polkit-1/polkitd --no-debug
> root      1127  0.0  0.0  19848  2632 ?        Ss   11:55   0:00 /lib/systemd/systemd-logind
> root      1216  0.0  0.0  37068  2612 ?        Ss   11:55   0:00 /sbin/rpcbind -w
> root      1503  0.0  0.3 431436 18444 pts/1    Ss+  11:55   0:00 /usr/lib/packagekit/packagekitd
> root      1504  0.1  0.0      0     0 pts/1    Z+   11:55   0:00 [dpkg] <defunct>
> root      1926  0.0  0.0   4320   752 pts/1    S+   11:55   0:00 /bin/sh -c /usr/sbin/dpkg-preconfigure --apt || true
> root      1927  0.4  0.3  65868 19192 pts/1    S+   11:55   0:00 /usr/bin/perl -w /usr/sbin/dpkg-preconfigure --apt
> root      1929  0.0  0.0      0     0 pts/1    Z+   11:55   0:00 [dpkg-preconfigu] <defunct>
>
> Killing PID 1926 made the machine reboot properly. The updates where
> not applied.
This could be the aptcc backend not respecting the noninteractive flag
completely. I will take a look at that code, because from that
information, I am almost certain that dpkg/debconf wants some
user-interaction there, which doesn't happen.
Any help with this is of course appreciated :-)
Cheers,
    Matthias