Bug 8082 - No "back" button for the "Format" option
Summary: No "back" button for the "Format" option
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: USABILITY
Depends on:
Blocks:
 
Reported: 2012-11-15 12:19 CET by Alejandro Lopez
Modified: 2014-12-01 12:02 CET (History)
2 users (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:

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

Description Alejandro Lopez 2012-11-15 12:19:26 CET 
Description of problem:
During the installation of Mageia 2, while partitioning the disks, I accidentally pressed "format" instead of the button I really wanted to press. So I tried to press the "back" button but there wasn't any. Once at this point, the only possible action is to format the partition.

Version-Release number of selected component (if applicable):
The package in the Mageia 2 ISO image.

How reproducible:
Everytime

Steps to Reproduce:
1. Start an installation of Mageia 2
2. In the screen for partitioning the disk, press "Format"
3. No "back" button is available, so you have no choice but to format the disk
Alejandro Lopez 2012-11-15 12:40:40 CET

CC: (none) => listas.apl

Alejandro Lopez 2012-11-15 12:41:10 CET

Hardware: i586 => x86_64

Comment 1 Sander Lepik 2012-11-15 13:03:53 CET 
Installer for Mageia 2 is frozen. Please test with Mageia 3 (Cauldron).

Keywords: (none) => NEEDINFO
CC: (none) => sander.lepik
Version: 2 => Cauldron

Manuel Hiebel 2012-11-28 22:53:14 CET

Keywords: NEEDINFO => USABILITY
Source RPM: (none) => drakxtools
Severity: normal => enhancement

Comment 2 Dick Gevers 2014-12-01 12:02:23 CET 
It would not be possible to undo a format once started, so it is also impossible to create a "back" button after "format" has already commenced.

Status: NEW => RESOLVED
Resolution: (none) => INVALID
Note You need to log in before you can comment on or make changes to this bug.