https://bugzilla.novell.com/show_bug.cgi?id=856789 https://bugzilla.novell.com/show_bug.cgi?id=856789#c Jiri Srain changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsrain@suse.com |mchang@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=856789 https://bugzilla.novell.com/show_bug.cgi?id=856789#c2 Nico Kruber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |nico.kruber@gmail.com InfoProvider|job_123@ngs.ru | --- Comment #2 from Nico Kruber 2014-03-08 18:44:47 UTC --- some more observations as I experienced this bug as well: (a BIOS sytem, i.e. no UEFI) 1) set default boot entry to Windows 2) install a kernel or grub2 update (e.g. the ones in the Update repo) 3) reboot an observe: openSUSE is pre-selected (default) and will be booted after timeout 4) go into Yast -> Boot Loader configuration -> Boot Loader Options, see that the default boot section is still the Windows selected in step 1 5) in order to restore the default in the boot screen, you actually have to change it to something else and let Yast store the new boot loaded configuration, then go back into it again and switch back to Windows yes, I'm using KDE but rebooting without selecting any entry so KDE should not change anything (also, since you can still see the windows boot entry as default in Yast which does not work though) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.