History log:
Start-Date: 2018-11-14 17:21:44 Commandline: aptdaemon role='role-commit-packages' sender=':1.5400' Install: linux-headers-4.18.0-11:amd64 (4.18.0-11.12, automatic), linux-image-4. 18.0-11-generic:amd64 (4.18.0-11.12, automatic), linux-modules-extra-4.18.0-11-g eneric:amd64 (4.18.0-11.12, automatic), linux-modules-4.18.0-11-generic:amd64 (4 .18.0-11.12, automatic), linux-headers-4.18.0-11-generic:amd64 (4.18.0-11.12, au tomatic) Upgrade: evince:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-headers-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), linux-libc-dev:amd64 (4.18.0-10.11, 4.18.0-11.12), linux-libc-dev:i386 (4.18.0-10.11, 4.18.0-11.12), libevdocument3-4:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-image-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), linux-signed-image-generic:amd64 (4.18.0.10.11, 4.18.0.11.12), libpq5:amd64 (10.5-1, 10.6-0ubuntu0.18.10.1), evince-common:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), libevview3-3:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-tools-common:amd64 (4.18.0-10.11, 4.18.0-11.12), postgresql-client-10:amd64 (10.5-1, 10.6-0ubuntu0.18.10.1), linux-generic:amd64 (4.18.0.10.11, 4.18.0.11.12) End-Date: 2018-11-14 17:24:10
Start-Date: 2018-11-15 08:39:50 Commandline: apt autoremove --purge Requested-By: vorlon (1000) Purge: linux-modules-extra-4.15.0-36-generic:amd64 (4.15.0-36.39), linux-modules-4.15.0-36-generic:amd64 (4.15.0-36.39), linux-image-4.15.0-36-generic:amd64 (4.15.0-36.39) End-Date: 2018-11-15 08:40:08
So yes, it's possible that this was only a candidate for autoremoval /after/ the previous run of update-manager had finished.
History log:
Start-Date: 2018-11-14 17:21:44 commit- packages' sender=':1.5400' 4.18.0- 11:amd64 (4.18.0-11.12, automatic), linux-image-4. generic: amd64 (4.18.0-11.12, automatic), linux-modules- extra-4. 18.0-11- g 4.18.0- 11-generic: amd64 (4 4.18.0- 11-generic: amd64 (4.18.0-11.12, au generic: amd64 (4.18.0.10.11, 4.18.0.11.12), linux-libc- dev:amd64 (4.18.0-10.11, 4.18.0-11.12), linux-libc-dev:i386 (4.18.0-10.11, 4.18.0-11.12), libevdocument3- 4:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-image- generic: amd64 (4.18.0.10.11, 4.18.0.11.12), linux-signed- image-generic: amd64 (4.18.0.10.11, 4.18.0.11.12), libpq5:amd64 (10.5-1, 10.6-0ubuntu0. 18.10.1) , evince-common:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), libevview3-3:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-tools- common: amd64 (4.18.0-10.11, 4.18.0-11.12), postgresql- client- 10:amd64 (10.5-1, 10.6-0ubuntu0. 18.10.1) , linux-generic:amd64 (4.18.0.10.11, 4.18.0.11.12)
Commandline: aptdaemon role='role-
Install: linux-headers-
18.0-11-
eneric:amd64 (4.18.0-11.12, automatic), linux-modules-
.18.0-11.12, automatic), linux-headers-
tomatic)
Upgrade: evince:amd64 (3.30.1-1ubuntu1, 3.30.1-1ubuntu1.2), linux-headers-
End-Date: 2018-11-14 17:24:10
Start-Date: 2018-11-15 08:39:50 extra-4. 15.0-36- generic: amd64 (4.15.0-36.39), linux-modules- 4.15.0- 36-generic: amd64 (4.15.0-36.39), linux-image- 4.15.0- 36-generic: amd64 (4.15.0-36.39)
Commandline: apt autoremove --purge
Requested-By: vorlon (1000)
Purge: linux-modules-
End-Date: 2018-11-15 08:40:08
So yes, it's possible that this was only a candidate for autoremoval /after/ the previous run of update-manager had finished.