Bug 873693 - not clear page when you have to reclaim space on disk
Summary: not clear page when you have to reclaim space on disk
Keywords:
Status: CLOSED DUPLICATE of bug 866209
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-06 14:02 UTC by Gianluca Cecchi
Modified: 2012-11-06 14:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-11-06 14:51:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
space reclamation page during install (62.10 KB, image/png)
2012-11-06 14:02 UTC, Gianluca Cecchi
no flags Details

Description Gianluca Cecchi 2012-11-06 14:02:26 UTC
Created attachment 639390 [details]
space reclamation page during install

Description of problem:
If you have to overwrite a previous install or in general if the disk is not empty it is not sufficiently clear how to choose option

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. install from iso (I used netinst.iso from f18 TC7)
2. land to the section regarding hard disk target install
3. try to reclaim space
  
Actual results:
It is not so clear in my opinion (at list it took half a minute to me to
understand... forgive me ;-) to click on right most column of each line and
see a drop down list with "preserve, reclaim, delete".

Expected results:
It could be better to put an arrow in the page or to explain better in the text placed before the window

Additional info:

See the attaced screenshot of a pre-instaled F17 vm where I run the netinst.iso
for trying install of f18 tc7.


What do you think?

Comment 1 Chris Lumens 2012-11-06 14:51:11 UTC
Yes, agreed, we definitely want an arrow to appear in that drop down.

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


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