package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)

[Vedant Aggrawal]

virtualbox installation getting stuck

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: virtualbox-dkms 5.2.10-dfsg-6
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Jun 10 19:11:06 2018
ErrorMessage: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
InstallationDate: Installed on 2018-06-10 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt 1.6.1
SourcePackage: virtualbox
Title: package virtualbox-dkms 5.2.10-dfsg-6 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess was killed by signal (Killed)
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Gianfranco Costamagna (costamagnagianfranco)]

hello cyphermox, do you have any clue about what might be wrong with DKMS now?

[Matt Harris (charrismatic)]

This has happened to me a couple times, I dont have a clear answer how to fix it yet, but the dkms install hangs waiting for input at the secure-boot update screen, but it seems to open in different tty so I end up having to kill the process to regain control of the terminal. You can see virtualbox-dkms getting stuck easily if you look at the process tree. I'll try to attach more useful information after my next attempt.

[Jack Hardcastle (jwhardcastle)]

Hey folks, just piping in that I am also having this problem. I am on an encrypted disk, and the build of the kernel modules just hangs. Please let me know if there is anything I can provide to assist in debugging.

Note that there appear to be two other related / duplicate bugs: 1769327 and 1775672.

[Jack Hardcastle (jwhardcastle)]

FWIW mine appears to have hung during a hidden (invisible to me) step where it was attempting to set a MOK. I had to first kill the existing dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh to #!/bin/bash (I was getting a local variable error), then manually run /usr/bin/perl -w /usr/share/debconf/frontend /usr/sbin/update-secureboot-policy --enroll-key, then reboot, install the key, finish booting, and dpkg --configure -a.

I have no idea if the terminal-gui app that is attempting to ask for a password for the MOK can be surfaced into the apt/dpkg configurating process, but that seems to be the missing link for me.