package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1

[Alimzhan Amanov]

Failed to build package when installing nvidia drivers. Every time `Building initial module for 4.15.0-22-generic` is stuck. There is no antivirus on my machine.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: rfcomm bnep nouveau asus_nb_wmi asus_wmi sparse_keymap mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core ath3k btusb btrtl ath9k ath9k_common btbcm ath9k_hw uvcvideo btintel bluetooth videobuf2_vmalloc videobuf2_memops ath videobuf2_v4l2 videobuf2_core mac80211 videodev media mei_me mei rtsx_pci_ms memstick intel_cstate intel_rapl_perf cfg80211 shpchp lpc_ich ie31200_edac wmi mac_hid asus_wireless i915 rtsx_pci_sdmmc r8169 rtsx_pci
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Thu Jun 7 12:36:23 2018
ErrorMessage: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1
InstallationDate: Installed on 2018-06-05 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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: linux-signed
Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Joseph Salisbury (jsalisbury)]

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

[jamso (jdsherratt3)]

I had the exact same issue. It actual problem is stated here by someone else, with a solution:

https://devtalk.nvidia.com/default/topic/1036167/linux/stuck-trying-to-intall-nvidia-390-ubuntu-18-04-lts-/

The problem is a dialogue requesting to set a password (for secureboot stuff) never pops up. I think the password must be 8 or more characters (not sure if there's an upper limit).

A workaround given was when the update gets stuck, type a password in the terminal blindly and press return twice (using the same password both times). This worked for me, except I had to type the password in about 4 times. (This is not necessary in theory, but I think maybe you're supposed to press "return" at other occasions to pass "ok" checkpoints. Therefore, you have to type the password unnecessarily and press return because you don't know where the checkpoints are.)

[Alimzhan Amanov (simb4)]

[SOLVED] SEE comment #4.

[Alimzhan Amanov (simb4)]

Thanks jamso!

Hope this thread stimulate one to investigate the problem of Secure Bot in this case.

[Jurgen Mulder (korstmos)]

I had this issue as well when running anything dpkg related in the terminal, the "blindly entering your password" trick did not work for me, but I did find a fix.

Running the software updater completely fixed the issue. It actually came with a popup for the password, which seems to be the missing link that #4 is talking about, but pressing enter after adding passwords in it did not work for me, I had to press next, which explains why typing passwords and spamming enter did nothing.

[Alex Perez (aperez-6)]

I ran into this as well. Examining my system while this is hung, I see this process running:

"# ps ax | grep whiptail
11195 pts/1 S+ 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. --scrolltext 21 77"

[Alex Perez (aperez-6)]

As Jurgen experience in #7, for me, blindly typing passwords (a ton of times) didn't do anything, but bailing out of this at the command line and re-running it through Software Updater did the trick for me.