"Continue" is disabled by default on third-party software step

[Jeremy Bícha]

What happens
------------
I tested today's daily Ubuntu GNOME yakkety installer on a computer with Secure Boot enabled.

On the "Preparing to install Ubuntu" screen, these are the default options:
- Download updates (unchecked and active)
- Install third party software (unchecked and active)
  - Turn off Secure Boot (checked and inactive unless the above box is checked)
  - Secure Boot password (inactive unless both Install third party software is checked)

Quit Back Continue (inactive unless either Turn off Secure Boot is unchecked or a good password is entered)

Screenshot attached.

The Continue button is inactive by default. Enabling the Continue button requires enabling "Install third party software" and disabling "Turn off Secure Boot". This can be fixed by disabling "Turn off Secure Boot" by default. This matches the design spec found at https://wiki.ubuntu.com/Ubiquity

[Jeremy Bícha (jbicha)]

I think this is a regression caused by
http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/xenial-proposed/revision/6446

See also bug 1612449 where I propose changing the order of the options on this page.

[Jeremy Bícha (jbicha)]

and http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6461

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1612450

[Steve Langasek (vorlon)]

The bug here is not whether or not that box is checked, but with the fact that it's honored in any way when you haven't selected "install third-party software". It should be a no-op until third-party software is checked; it should not cause the 'Continue' button to be greyed out, and it should not trigger an actual attempt to disable secureboot.

Whether the greyed-out checkbox is ticked or not is a minor detail.

[Matthew Paul Thomas (mpt)]

It’s a relatively minor detail, yes, but the checkbox should be unchecked by default regardless. (First for more effective acknowledgement that you’re turning off a security feature, and second following the mostly-unwritten design rule that disabled controls should default to their effective value if they are disabled for being unalterable rather than being disabled for being inapplicable.) Mathieu do you want a separate bug report for that?