Bug 846102 - openSUSE 13.1 RC1 i586 Up-Button for Disk order settings not working
Summary: openSUSE 13.1 RC1 i586 Up-Button for Disk order settings not working
Status: RESOLVED FIXED
Alias: None
Product: openSUSE 13.1
Classification: openSUSE
Component: Installation (show other bugs)
Version: RC 1
Hardware: i586 SUSE Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Josef Reidinger
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-15 20:55 UTC by Forgotten User PoQ9LLo9Cj
Modified: 2015-02-05 07:35 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User PoQ9LLo9Cj 2013-10-15 20:55:02 UTC 
User-Agent:       Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Firefox/24.0

I try to install the i586 version of openSUSE 13.1 RC1 to a vitualbox system with two harddisk drives
/dev/sda
/dev/sdb
I want to change the disk order in
Installation Settings option Booting
Boot Loader Installation Details
Disk order settings.
If I try to move an entry (/dev/sdb in my case) up with the Up button nothing happens. 
However I can move an entry down (/dev/sda in my case) with the Down button.


Reproducible: Always

Steps to Reproduce:
1. Install i586 version openSUSE 13.1 RC1 to system with two or more harddisk drives
2. Select Option Booting for Installation Settings
3. Klick Button Boot Loader Installation Details
4. Try to move last entry up in the disk order list with the up button.
5. Try to move first entry down in the disk order list with the down button
Actual Results:  
Up Button does nothing.
Down Button moves entry down in the list.

Expected Results:  
Up Button moves entry up in the list.
Comment 1 Forgotten User PoQ9LLo9Cj 2013-10-16 17:24:55 UTC 
The x86_64 version of openSUSE 13.1 RC1 has this bug too.
Comment 3 Josef Reidinger 2015-02-05 07:35:19 UTC 
should be already fixed in 13.2. If not, please reopen and I will recheck.