group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1606393@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package ubiquity - 2.21.63.3

---------------
ubiquity (2.21.63.3) xenial; urgency=medium

  * ubi-prepare.py: default to disabling Secure Boot when third party drivers
    are being installed, since it's most likely what people will want. This
    will also avoid people skipping through this important part of the
    installer without noticing, only to find their systems not all working
    correctly. (LP: #1606393)
  * d-i/sources.list: add xenial-updates to sources.list to pick up any SRUs
    of d-i components that are no longer in flight.
  * Automatic update of included source packages: apt-setup
    1:0.104ubuntu4.1, base-installer 1.158ubuntu2.1, netcfg
    1.135ubuntu4.1. (LP: #1590358)
  * bin/ubiquity-dm: wait for the DBus signals telling us that xsettings are
    ready before continuing with preparing ubiquity-dm; this avoids starting
    too quickly and incorrectly applying scale ratios for HiDPI screens.
    (LP: #1560162)

 -- Mathieu Trudel-Lapierre <cyphermox@xxxxxxxxxx>  Fri, 02 Sep 2016
11:17:13 -0400

** Changed in: ubiquity (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1606393

Title:
  default should be to disable Secure Boot when installing third-party
  drivers

Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  Users choosing to install third-party drivers for their system at installation time.

  [Test case]
  1) Start ubiquity install
  2) On the prepare screen, pick "Install third-party drivers"

  The install should automatically have the "Disable Secure Boot"
  checkbox checked.

  [Regression Potential]
  Doing this will block the installer while users enter a password to use to disable Secure Boot, or go uncheck the checkbox. Possible failure cases might be crashes due to errors in mokutil or in the kernel handling of efi variables which might have ubiquity crash. This happens early in the installer process, before any changes are made to the system.

  ---

  The default behavior in ubiquity when installing third-party drivers
  should be to suggest disabling Secure Boot, as it may otherwise be
  missed due to confusion. Third-party drivers of the type installed in
  that option in ubiquity are typically dkms packages which will need
  Secure Boot disabled in shim to work correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1606393/+subscriptions