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)

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

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

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.

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.

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.