Possibly a dependency conflict of some kind. Maybe try updating from the terminal to see if it works or at least gives a useful error message sudo apt update && sudo apt upgrade && sudo apt full-upgrade
You could also check the contents of the /boot directory to see if the kernel is actually there. If the kernel is there on the drive but not being used to boot, then you could try running "sudo update-grub" and then rebooting. On Tue, 2 Feb 2021 at 18:14, D. R. Evans <doc.ev...@gmail.com> wrote: > I went to update one of my machines running debian stable today, using (as > usual) synaptic [which I think is basically a wrapper for various apt > functions]. The machine is running: > > ---- > > [Z:~] uname -a > Linux zserver 4.19.0-13-amd64 #1 SMP Debian 4.19.160-2 (2020-11-28) x86_64 > GNU/Linux > [Z:~] > > ---- > > But I see that synaptic lists 4.19.0-14-amd64 as being available in the > repository; and, indeed, on another machine I updated earlier in the day > the > kernel was updated from -13 to -14. > > How might I be able to diagnose why the files relating to the -14 kernel > are > not selected when I hit synaptic's "Mark All Upgrades" button? > > Doc > > -- > Web: http://enginehousebooks.com/drevans > >
