On my desktop, there are two LEAP systems, 15.0 and 15.1. grub is managed by the older version 15.0. Now, i found that on 15.1, an old version of the kernel is used rather than the latest patch: ~\:08:39:37 > uname -a Linux linux-riut 4.12.14-lp151.27-default #1 SMP Fri May 10 14:13:15 UTC 2019 (862c838) x86_64 x86_64 x86_64 GNU/Linux ~\:08:56:31 > uname -r 4.12.14-lp151.27-default ~\:08:56:39 > The kernel patch in use seems to be the first of LEAP 15.1. Auto-Update is active and the new kernel really is installed: ~\:09:59:26 > ls -l /boot | grep vmlinuz lrwxrwxrwx 1 root root 35 16. Aug 20:23 vmlinuz -> vmlinuz-4.12.14-lp151.28.13-default -rw-r--r-- 1 root root 7331952 15. Mai 02:26 vmlinuz-4.12.14-lp151.27-default -rw-r--r-- 1 root root 7340144 15. Jul 13:25 vmlinuz-4.12.14-lp151.28.10-default -rw-r--r-- 1 root root 7344240 11. Aug 10:54 vmlinuz-4.12.14-lp151.28.13-default ~\:09:59:26 > There are no such problems on the 15.0-system. I figured, I should let grub refresh its boot entries, so I started the boot configuration in Yast on 15.0, but had no success with it. Maybe, i could simply delete the old kernels manually? But how can i avoid this from happening every time a new patch is released? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org