Public bug reported:

If I install or update virtualbox-dkms, dpkg needs to ask me to
configure Secure Boot. This works fine using apt-get (or a GUI), but not
apt. When installing via apt, whiptail(1) doesn't show, and the
installation/upgrade process gets stuck, forcing me to kill dpkg then
run "dpkg --configure -a", then reinstall virtualbox-dkms using apt-get.

Example process tree snippet attached.

** Affects: apt (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  If I install or update virtualbox-dkms, dpkg needs to ask me to
  configure Secure Boot. This works fine using apt-get (or a GUI), but not
  apt. When installing via apt, whiptail(1) doesn't show, and the
  installation/upgrade process gets stuck, forcing me to kill dpkg then
  run "dpkg --configure -a", then reinstall virtualbox-dkms using apt-get.
  
- Example process tree snippet below:
- 
- root      8986  0.0  0.0  72720  4408 pts/1    S+   10:56   0:00              
|   |   |   \_ sudo apt -y upgrade
- root      8987  0.1  0.5 146512 87620 pts/1    S+   10:56   0:04              
|   |   |       \_ apt -y upgrade
- root     12061  0.0  0.0  32216  9528 pts/6    Ss+  11:07   0:00              
|   |   |           \_ /usr/bin/dpkg --status-fd 81 --configure --pending
- root      8537  0.0  0.0   4628   808 pts/6    S+   11:09   0:00              
|   |   |               \_ /bin/sh 
/var/lib/dpkg/info/linux-headers-4.15.0-50-generic.postinst configure
- root      8538  0.0  0.0   4520   828 pts/6    S+   11:09   0:00              
|   |   |                   \_ run-parts --report --exit-on-error 
--arg=4.15.0-50-generic /etc/kernel/header_postinst.d
- root      8541  0.0  0.0   4628  1788 pts/6    S+   11:09   0:00              
|   |   |                       \_ /bin/sh /usr/lib/dkms/dkms_autoinstaller 
start 4.15.0-50-generic
- root      8547  0.0  0.0  23000  6372 pts/6    S+   11:09   0:00              
|   |   |                           \_ /bin/bash /usr/sbin/dkms autoinstall 
--kernelver 4.15.0-50-generic
- root      8911  0.0  0.0  23112  5568 pts/6    S+   11:09   0:00              
|   |   |                               \_ /bin/bash /usr/sbin/dkms autoinstall 
--kernelver 4.15.0-50-generic
- root     13251  0.0  0.1 110864 22384 pts/6    S+   11:09   0:00              
|   |   |                                   \_ /usr/bin/perl -w 
/usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key
- root     13265  0.0  0.0   4628  1848 pts/6    S+   11:09   0:00              
|   |   |                                       \_ /bin/sh 
/usr/sbin/update-secureboot-policy --enroll-key
- root     13280  0.0  0.0  32432  4584 pts/6    S+   11:09   0:00              
|   |   |                                       \_ whiptail --backtitle Package 
configuration --title Configuring Secure Boot --output-fd 12 --nocancel 
--msgbox Your system has UEFI Secure Boot enabled.  UEFI Secure Boot requires 
additional configuration to work with third-party drivers.  The system will 
assist you in configuring UEFI Secure Boot. To permit the use of third-party 
drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs 
to be enrolled in your system's  firmware.  To ensure that this change is being 
made by you as an authorized user, and not by an attacker, you must choose a 
password now and then confirm the change after reboot using the same password, 
in both the "Enroll MOK" and "Change Secure Boot state" menus that will be 
presented to you when this system reboots.  If you proceed but do not confirm 
the password upon reboot, Ubuntu will still be able to boot on your system but 
any hardware that requires third-party drivers to work correctly may not be 
usable. 17 208
+ Example process tree snippet attached.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1829776

Title:
  apt tries to use whiptail, which won't show

Status in apt package in Ubuntu:
  New

Bug description:
  If I install or update virtualbox-dkms, dpkg needs to ask me to
  configure Secure Boot. This works fine using apt-get (or a GUI), but
  not apt. When installing via apt, whiptail(1) doesn't show, and the
  installation/upgrade process gets stuck, forcing me to kill dpkg then
  run "dpkg --configure -a", then reinstall virtualbox-dkms using apt-
  get.

  Example process tree snippet attached.

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

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

Reply via email to