Bug 1027081

Summary: Bootloader wont show other boot options
Product: [openSUSE] openSUSE Tumbleweed Reporter: Wayne Patton <wayne.patton>
Component: BootloaderAssignee: Michael Chang <mchang>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: bryan.gartner, wayne.patton
Version: Current   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: /etc/default/grub
zypper history from today Mar 8 2017

Description Wayne Patton 2017-02-27 14:33:11 UTC
After the latest Tumbleweed updates that I applied on 2/26/2017 the bootloader will not show other boot options. I have a triple boot setup with Leap 42.2 & SLSE 12SP2 along with Tumbleweed. When I run the  bootloader option in Yast, with the "Probe Foreign OS" option checked, it still doesn't fix it.  Before these updates, the TW bootloader did show all the boot options correctly.
Comment 1 Jiri Srain 2017-03-02 11:15:24 UTC
Can you attach /etc/default/grub so that we can be sure whether YaST configured GRUB correctly or not?
Comment 2 Wayne Patton 2017-03-02 14:14:44 UTC
Created attachment 716077 [details]
/etc/default/grub
Comment 3 Jiri Srain 2017-03-06 08:06:53 UTC
Thanks for the file. OS Prober is explicitly not disabled (which is correct if you want to include other systems). Michael, this looks similar to other bugs I've seen recently...
Comment 4 Wayne Patton 2017-03-08 18:53:23 UTC
I installed the latest updates for Tumbleweed this morning. Just now I rebooted my laptop and grub is showing me all the other OS boot choices. So something was fixed?
Comment 5 Wayne Patton 2017-03-08 19:00:12 UTC
Created attachment 716797 [details]
zypper history from today Mar 8 2017
Comment 6 Michael Chang 2017-03-09 08:24:13 UTC
> zypper history from today Mar 8 2017

Yes, from the history file the os-prober was updated and latest change fixed the problem. See. bsc#1024196.

Thank you.

*** This bug has been marked as a duplicate of bug 1024196 ***