** Description changed:

- There is a sequence of events that can cause the Ubiquity installer in
- Hardy Herron (8.04) to loop at step 4, the partitioning step.
+ The installer fails to reset the variable that causes it to stay on a
+ page when an error is triggered when returning to a previous page,
+ causing it to stay on the previous page that it just returned to despite
+ any attempts to proceed.
  
- Steps to reproduce are:
+ This will occur if a user enters an invalid password, then presses back
+ to change their partition layout.  If they try to proceed forward to the
+ user setup page again, they will remain on the partitioning page.
+ 
+ This is a one line change that should have no regressions.
+ 
+ A diff of the proposed change as included in the ubiquity 1.8.9 upload
+ can be found here:
+ 
+ TEST CASE:
  1) Run the installer, click "Forward" until you get to Step 5, Who are you?
  2) Enter all data correctly except for the "What is the name of this 
computer?" field - enter a name with an underscore (or presumably any other 
non-valid character) and press "Forward"
  3) The installer will complain that the computer name is invalid.
  4) Click "Back" to go back to Step 4, the partition editor
  5) Press "Forward" - partition editor rescans the disk and step 4 starts 
again (this will happen every time you press "Forward", and happens regardless 
of what settings you choose for the partitions.)
  
- My guess is the invalid variable is not cleared when "Back" is pressed,
- and there is a validation error when an attempt is made to re-insert the
- bad value into step 5, causing step 4 to repeat.
+ Original report:
+ There is a sequence of events that can cause the Ubiquity installer in Hardy 
Herron (8.04) to loop at step 4, the partitioning step.

** Attachment added: "235374-reset-error.patch"
   http://launchpadlibrarian.net/14910138/235374-reset-error.patch

-- 
Ubiquity installer in Hardy can loop at partition editing step
https://bugs.launchpad.net/bugs/235374
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to