Hi all. I have a default set in GRUB2 bootloader which normally works nicely, booting to my Windows partition. However when auto update includes a new kernel version, after the update the bootloader defaults back to LEAP 15.4. It’s only a minor thing but is the expected behaviour?
One thing did occur to me, though it may be nonsense. When a software update is performed via YAST auto-update which " requires" a reboot (like kernel versions) , might some sort of flag get set somewhere to force boot to come back to Suse to complete the installation (overriding default boot option)?
Right, I’ll see how it goes. I think I did rather compromise the investigation as I re-entered the default in YAST following the problem, so that grb.cfg probably got updated after the problem occurred.
As I said originally, it’s not that big a deal so I’m grateful that you committed your time to it.