Previously we started installation (restarted debconf and so on) after committing the partition changes to disk. We changed that to be after both the timezone step and partitions were committed, because installation needs to have debconf answers from the timezone stuff.
This bug happens because we do that multiple times if you go between the step after timezone (user setup) back to timezone itself, and then forward again. We didn't do anything to prevent installation happening multiple times. You can't go back to partition committing once you've been past it (unless it fails), so this bug couldn't happen with the previous logic. Another thing could be to move timezone before partitioning, which would solve the initial bug and not be prone to this regression - in that case you would lose the parallelisation of doing partitioning while selecting the timezone. That's why we didn't do it first off. I'm not sure what "which isn't a much better solution than the two here" is meant to mean in that sense I'm afraid. Sounds like you're criticising what we did to fix that bug? Anyway, if you have smarter ideas, let's hear them. Hopefully you can understand what the problem is now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799097 Title: Install selected time zone city (Seattle) hit next hit back hit next then crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1799097/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
