The fix here breaks installing custom kernels, at least on xenial (dkms
(2.2.0.3-2ubuntu11.7) xenial): the redirection of stdout was to there to
fix a problem with dkms output contaminating debconf's input - see
#292606 for details. To be specific, during package install (either via
dpkg or apt-get) I'm now getting the following error from /usr/sbin
/update-grub-legacy-ec2 which is run from /etc/kernel/postinst.d/x-grub-
legacy-ec2 (after running /etc/kernel/postinst.d/dkms):

20 Unsupported command "*" (full line was " * dkms: running auto
installation service for kernel ...") received from confmodule.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1827697

Title:
  Enroll key whiptail prompt blocks kernel header package upgrades

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in dkms source package in Bionic:
  Fix Released
Status in dkms source package in Cosmic:
  Fix Released
Status in dkms source package in Disco:
  Fix Released
Status in dkms source package in Eoan:
  Fix Released

Bug description:
  I noticed that sometimes the system upgrade is blocked in the kernel
  header package's configure phase, in the process manager I found that
  it is blocked by the "Configuring Secure Boot" whiptail prompt started
  by `update-secureboot-policy --enroll-key` which doesn't surface to
  the terminal and hence not interactable.

  Refer the attached screenshot for the process status at the time.

  [Test Case]
  1. Install any out-of-tree dkms packages (like bbswitch-dkms)
  2. Un-enroll keys from MOK, ensure `mokutil --test-key 
/var/lib/shim-signed/mok/MOK.der` command returns 
"/var/lib/shim-signed/mok/MOK.der is not enrolled"
  3. Ensure SecureBoot is enabled
  4. Install any linux-headers-${version}-generic packages that is currently 
not installed, verify if it stucks at configurating state

  [Regression potential]
  Since this change will cause the output of dkms_autoinstaller to appear in 
the output of the kernel installs, this may surprise consumers of the dpkg log 
with its verbosity.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to