Can't install any packages with ubuntu-drivers using ubuntu-drivers when invoked from ubiquity

[Iain Lane]

We are in the process of switching ubuntu-drivers to installing linux-restricted-modules versions of NVidia drivers when it can, but this fails when Ubiquity invokes ubuntu-drivers, like:

Setting up linux-modules-nvidia-440-5.4.0-25-generic (5.4.0-25.29) ...
 /var/lib/dpkg/info/linux-modules-nvidia-440-5.4.0-25-generic.postinst: 44: 3: B
ad file descriptor
 dpkg: error processing package linux-modules-nvidia-440-5.4.0-25-generic (--con
figure):
  installed linux-modules-nvidia-440-5.4.0-25-generic package post-installation
script subprocess returned error exit status 2
 dpkg: dependency problems prevent configuration of linux-modules-nvidia-440-gen
eric-hwe-20.04:
  linux-modules-nvidia-440-generic-hwe-20.04 depends on linux-modules-nvidia-440
-5.4.0-25-generic (= 5.4.0-25.29); however:
   Package linux-modules-nvidia-440-5.4.0-25-generic is not configured yet.

 dpkg: error processing package linux-modules-nvidia-440-generic-hwe-20.04 (--configure):
  dependency problems - leaving unconfigured

It's a problem with the nesting of debconf: Ubiquity itself is using debconf, and ubuntu-drivers is installing -nvidia- packages which themselves also use debconf, and we don't know how to connect ubuntu-drivers use of debconf with the ubiquity one.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-restricted-modules - 5.4.0-26.30+1

---------------
linux-restricted-modules (5.4.0-26.30+1) focal; urgency=medium

  * Can't install any packages with ubuntu-drivers using ubuntu-drivers when
    invoked from ubiquity (LP: #1874278)
    - [Packaging] work around lack of debconf in the installer host

 -- Andy Whitcroft <email address hidden> Wed, 22 Apr 2020 17:03:46 +0100

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-restricted-modules - 5.4.0-26.30+2

---------------
linux-restricted-modules (5.4.0-26.30+2) focal; urgency=medium

  * /bin/in-target check is flawed as it does not tell the difference
    between live-session and in-target chroot. (LP: #1874278)

 -- Dimitri John Ledkov <email address hidden> Wed, 22 Apr 2020 22:43:55 +0100