Bug 588771 - Double clicking a disk in the right clear disk pane also clears the bootdev selection
Summary: Double clicking a disk in the right clear disk pane also clears the bootdev s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-04 13:38 UTC by Hans de Goede
Modified: 2010-07-01 20:58 UTC (History)
3 users (show)

Fixed In Version: anaconda-14.5-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-01 20:58:28 UTC
Type: ---


Attachments (Terms of Use)

Description Hans de Goede 2010-05-04 13:38:24 UTC
To reproduce:

1) Do an interactive install on a machine with at least 3 disks
2) Select all 3 disks in the filter UI
3) In the clear disk UI move all disks to the right pane
4) double click on a disk in the right pane which is not selected as
   bootdevice

Result:
The disk which is double clicked gets moved to the left pane (ok) and
the disk which was selected as bootdevice is no longer selected as
bootdevice (not ok)

Expected:
The disk which is double clicked gets moved to the left pane, no other
changes.


Note we may want to fix this for RHEL-6 too.

Comment 1 Chris Lumens 2010-05-04 19:07:36 UTC
DOES NOT reproduce:

(1) Select all three devices in the left hand side and move to the right.
(2) Double click on a device in the right hand side which is not the boot device.


DOES reproduce:

(1) Select all three devices in the left hand side and move to the right.
(2) Change which device is selected as the boot device via the radio button.
(3) Double click on a device in the right hand side which is not the boot device.

Does this match up with what you guys are seeing?  A related problem here is if you double click on the boot device in the right hand side, no other device gets selected for you.  Is that actually a problem?

Comment 2 James Laska 2010-05-04 19:29:16 UTC
(In reply to comment #1)
> DOES NOT reproduce:
> 
> (1) Select all three devices in the left hand side and move to the right.
> (2) Double click on a device in the right hand side which is not the boot
> device.

My experiences match yours.  I've retested with 2 devices.  Double clicking (without changing the default boot device), does not trigger the reported behavior.

> DOES reproduce:
> 
> (1) Select all three devices in the left hand side and move to the right.
> (2) Change which device is selected as the boot device via the radio button.
> (3) Double click on a device in the right hand side which is not the boot
> device.

My experiences match yours.  Using the procedure above, I'm able to trigger the reported behavior.
 
> Does this match up with what you guys are seeing?  A related problem here is if
> you double click on the boot device in the right hand side, no other device
> gets selected for you.  Is that actually a problem?    

I don't think that's bad, just as long as the UI doesn't allow you to proceed until *something* is selected.

Comment 3 Hans de Goede 2010-05-04 19:43:18 UTC
(In reply to comment #1)
> DOES NOT reproduce:
> 
> (1) Select all three devices in the left hand side and move to the right.
> (2) Double click on a device in the right hand side which is not the boot
> device.
> 
> 
> DOES reproduce:
> 
> (1) Select all three devices in the left hand side and move to the right.
> (2) Change which device is selected as the boot device via the radio button.
> (3) Double click on a device in the right hand side which is not the boot
> device.
> 

Ah, it could very well be that is actually what I was seeing. I believe you when you say that this does not happen when the default boot device is selected.

> Does this match up with what you guys are seeing?  A related problem here is if
> you double click on the boot device in the right hand side, no other device
> gets selected for you.  Is that actually a problem?    

Yes and no, if the default boot device gets removed by double clicking no device should be selected for booting (if the system is not going to boot from bios dev 80, no guess is better then a random guess). OTOH if a device which is not the default boot device, but was selected for boot gets removed the default boot device should be selected. IOW after the double click _autoSelectBootDisk() should be called (it is a no-op if some device is already selected).


Note You need to log in before you can comment on or make changes to this bug.