Bug 155276

Fresh installation or update? (worked for me as update)

I guess the y2logs will help here, so please attach them ;-)

Created attachment 71251 [details]
the requested YaST2 logs

The MBR problem happened after a fresh installation, not an update.

There is a add-on bug included here: When usng YaST2 bootloader you get "Section Management" and "Boot Loader Installation". Whatever you specify in "Boot Loader Installation" as boot loader location gets overwritten if you change something in "Section Management" before you finish this module. In case one wants to preserve the boot loader location it needs to be respecified as last item before finishing the YaST2 module.

No, only the radio button gets unchecked, but in the combobox at the bottom of the frame, you still have the chose device. (This is not the best solution,  I admit, but it should work.
If that's not the case, could you please open a separate bug for this?
Other than that, I don't understand the original description:
You install a system, then later, you call yast2 bootloader, and then 
the displayed configuration is different?

There hasn't been any progress on this bug for a couple of weeks -> what's the status? Frank-Michael?

No change: I've chosen the MBR as location during install, after a couple of reboots I start "yast2 bootloader". Without even changing anything, the "Boot Loader Installation" tab shows "Other: /dev/sda" as location, not the "MBR of /dev/sda". So when I change something in section management, yast2 will use the "Other" setting on exit, unless I pick the MBR of /dev/sda as location manually.

I already explained in comment #4, that this is the expected behaviour.
The boot sector of a _disk_ is the MBR of this disk.

This would need to change the the interface handling in yast2-bootloader
ATM it only displays the device for the bootloader, but doesn't
differentiate any special cases, represented with radio buttons.

This won't be changed for 10.1, closing 'later'

I am sorry, but I govern only about five languages. When you have one row and radio button "Master Boot Record" and another one well below as "Other" this means in each of these languages: "Not Master Boot Record". If it would mean "Master Boot Record" it would not be called "Other" than "Master Book Record" in any language.

Therefore either you set the right radio button: if "MBR" then "MBR", or you add a line to the help text saying: "MBR on /dev/sda" is the same as "Other: /dev/sda". Or if is not the same then please, where will YaST2 put the bootloader then?

In any case, in an OpenSUSE environment your action is not "resolving", it's "don't bother me".

I think we should discuss it on the mailing list now.

(In reply to comment #8)
> In any case, in an OpenSUSE environment your action is not "resolving", it's
> "don't bother me".
> 
> I think we should discuss it on the mailing list now.

Frank-Michael, let's get this straight right now: We are very late in the release cycle and resolving this bug "LATER", is totally valid. 

Your understanding of an "openSUSE environment" puzzles me, by the way. If you are keen on getting this fixed, troll^Wmailing to the mailinglist doesn't help at all. Providing a patch would be the way to go. Or, just waiting and leaving the prioritization up to us. Thanks.

reevaluate for SLE11

this has been fixed in the meanwhile, just check openSuse factory