On 10/16/2018 06:28 AM, Carlos E. R. wrote:
Why are you so complicated? :-)
Just edit "/etc/default/grub":
GRUB_DISABLE_OS_PROBER="true"
It is that simple. And yes, it has to work, else it is a bug and report in bugzilla.
I will test that upgrade later in the day.
I'm just difficult.... ;) I've already added GRUB_DISABLE_OS_PROBER="true" to /etc/default/grub before posting this thread. My point what "What changed?" I have not had GRUB_DISABLE_OS_PROBER="true" since my install of 42.3 over a year ago, and os-prober has never run adding win10 to grub.cfg before, so why now? Whatever the grub2 update on Oct 2, 18 was it created: l /etc/default total 60 drwxr-xr-x 2 root root 4096 Oct 13 14:55 . drwxr-xr-x 142 root root 12288 Oct 16 07:50 .. -rw-r--r-- 1 root root 1836 Oct 13 14:55 grub <=== -rw-r--r-- 1 root root 1392 Mar 6 2018 grub.old <=== -rw-r--r-- 1 root root 76 Apr 2 2018 grub_installdevice (the grub file was dated Oct 2, 2018 before I changed GRUB_DISABLE_OS_PROBER="true") So this new grub2 package replaced my defaults and added the following lines: GRUB_BACKGROUND=/boot/grub2/themes/openSUSE/background.png GRUB_THEME=/boot/grub2/themes/openSUSE/theme.txt SUSE_BTRFS_SNAPSHOT_BOOTING="true" # GRUB_DISABLE_OS_PROBER="false" GRUB_DISABLE_OS_PROBER="true" GRUB_ENABLE_CRYPTODISK="n" GRUB_CMDLINE_XEN_DEFAULT="vga=gfx-1024x768x16" (I commented the "false" that was addeded to set GRUB_DISABLE_OS_PROBER="true") If this overwrote my prior defaults -- then what the heck is going to prevent the next nonsensical change from overwriting them again? Why the hell would I want SUSE_BTRFS_SNAPSHOT_BOOTING="true", when my system is ext4?? At least the system was smart enough to limit the damage to grub_installdevice this time and not wipe my win10 bootloader as it did on 42.2 when this problem was fixed the last time. os-prober should not be running on update, unless I tell it to. New /etc/default/grub should not set os-prober to run by default and it should not replace or add options. I can't believe the /etc/defaults/grub was not installed as a .rpmnew instead of adding options without doing so. This is what prompted the question -- What changed? -- David C. Rankin, J.D.,P.E.