Bug 429940

Summary: Usability: Expert Partitioner Must Be Left with Cancel
Product: [openSUSE] openSUSE 11.1 Reporter: Tanja Roth <taroth>
Component: YaST2Assignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None CC: aschnell
Version: Beta 1   
Target Milestone: ---   
Hardware: i386   
OS: Other   
Whiteboard:
Found By: Documentation Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Bug Depends on: 385315    
Bug Blocks:    

Description Tanja Roth 2008-09-25 15:02:57 UTC
+++ This bug was initially created as a clone of Bug #385315 +++

...to close the partitioning dialog, even if changes were made in the fstab for a partition. E.g. after enabling quota support for a partition, a nearly unreadable  message pops up (white text on a light green background, see attachment), asking the user if he really wants to execute these changes. After clicking Apply the pop-up closes, leaving the Expert Partitioner still open (so far everything OK except of the unreadable pop-up message). 

If the user now clicks OK to close the partitioner, a new message pops up "No unsaved changes exist". So the user has no other choice than to leave the partitioner with "Cancel". I guess every user would expect that upon "Cancel" his changes have been canceled, but in fact, his changes have been saved - when checking again, the quota support is enabled.

IMO, this is very confusing and doesn't make sense at all from a usability point of view - even if the changes to the fstab are already saved when closing the pop-up, users should be able to leave the partitioner with OK (and not get a message that there have been no changes when, in fact, there have been changes, even if it was only to the fstab and not to the partitioner itself).
Comment 1 Tanja Roth 2008-09-25 15:07:25 UTC
Sorry, Katharina's answer and my opening of this new bug were happening at the same time, so closing this again as duplicate of #385315.

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