Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 873260 - Current mount point is not highlighted
Summary: Current mount point is not highlighted
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora19rtt
TreeView+ depends on / blocked
 
Reported: 2012-11-05 13:20 UTC by Jan Stodola
Modified: 2013-04-10 19:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-10 19:10:40 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
no mountpoint highlighted (94.64 KB, image/png)
2012-11-05 13:20 UTC, Jan Stodola 		no flags Details
View All

Description Jan Stodola 2012-11-05 13:20:07 UTC 
Created attachment 638586 [details]
no mountpoint highlighted

Description of problem:
When modifying a mount point in custom partitioning screen, current mount point should be highlighted. But when user clicks to any configuration field (for example size of the mount point), highlighting of current mount point gets lost.

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

How reproducible:
always

Steps to Reproduce:
1. start installation in graphical mode
2. go to custom partitioning
3. select/create partition
4. click to any field on the right (mount point, desired capacity,...)
  
Actual results:
No mount point is highlighted

Expected results:
Current mount point I'm editing is highlighted

Additional info:
To demonstrate this issue, look at attached screenshot and guess which mount point will be removed after clicking at "-" button (You have only one attempt!)
Comment 1 Chris Lumens 2013-04-10 19:10:40 UTC 
This ends up being vastly more work than it's really worth, so I can't see that we're going to get to it any time soon.  Sorry.
Note You need to log in before you can comment on or make changes to this bug.