[Bug 1793671] Re: Proprietary drivers are installed locally and not on the target system

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 18.04.14.11

---------------
ubiquity (18.04.14.11) bionic; urgency=medium

  [ Steve Langasek ]
  * scripts/plugininstall.py: don't hard-code a resume partition in
    /etc/initramfs-tools/conf.d/resume at install time.  In bionic and later,
    initramfs-tools will autodetect an appropriate resume partition at
    initramfs generation time, so ubiquity's resume setting is redundant and
    possibly wrong.  LP: #1768230.

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Mon, 21 Jan 2019 20:25:03
+0000

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1793671

Title:
  Proprietary drivers are installed locally and not on the target system

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

Bug description:
  [Impact]

   * Installing systems with nvidia graphics card, and opting to use it,
  does not end up setting it up in the installed system

  [Test Case]

   * Install on a system with nvidia graphics card
   * Opt to use 3rd party & proprietary drivers
   * Observe that nvidia dkms modules are installed in the target system

  [Regression Potential]

   * Installation of 3rd party drivers was not attempted before, and thus may now fail, however that is non-default codepath (opt-in).
   * there are updates to flash-kernel & shim-signed which may regress that functionality under ubiquity, but shouldn't (see changelogs for those package updates)

  [Other Info]
   
   * original bug report:

  On a system with hardware requiring proprietary drivers (eg nVidia graphics card), when the user selects to install restricted add-ons and proprietary drivers, ubuntu-drivers runs immediately when the installer exits the prepare step.
  Doing so it installs the drivers on the live session. However this step is not executed in the target filesystem afterward, once its ready.
  Therefore, after installation, the proprietary drivers are not installed on the system.

  The installation of proprietary drivers must happen in the live
  session, for network drivers for example, and in the target system for
  all the drivers supported by the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 21 09:49:29 2018
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper --
  InstallationDate: Installed on 2013-09-03 (1843 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to cosmic on 2018-01-26 (237 days ago)

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