Comment 8 for bug 1783023

Still seeing this (haven't updated, neither using apt nor update-manager because this bug annoys me).

Digged for when this was introduced in update-manager and found the package was updated in June:

$ zgrep update-manager /var/log/apt/hi*2* -B3 -A1
/var/log/apt/history.log.2.gz:Start-Date: 2018-06-26 13:34:44
/var/log/apt/history.log.2.gz:Commandline: apt upgrade
/var/log/apt/history.log.2.gz:Requested-By: miki (1000)
/var/log/apt/history.log.2.gz:Upgrade: update-manager-core:amd64 (1:16.04.12, 1:16.04.13), unity-control-center-faces:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), update-manager:amd64 (1:16.04.12, 1:16.04.13), gnome-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), virtualbox-dkms:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), virtualbox:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), unity-control-center:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11), python3-update-manager:amd64 (1:16.04.12, 1:16.04.13), libunity-control-center1:amd64 (15.04.0+16.04.20170214-0ubuntu2, 15.04.0+16.04.20171130-0ubuntu1), virtualbox-qt:amd64 (5.0.40-dfsg-0ubuntu1.16.04.2, 5.1.34-dfsg-0ubuntu1.16.04.2), gnome-software-common:amd64 (3.20.5-0ubuntu0.16.04.10, 3.20.5-0ubuntu0.16.04.11)
/var/log/apt/history.log.2.gz:End-Date: 2018-06-26 13:36:58

Seems like the bug is introduced in 1:16.04.13: https://launchpad.net/ubuntu/+source/update-manager/1:16.04.13

Full patch here: https://launchpadlibrarian.net/370576411/update-manager_1%3A16.04.12_1%3A16.04.13.diff.gz

Though, looking through the path I can't identify any connection with phased updates. The changes seems to relate to autoremoving only.