package virtualbox-dkms 6.0.6-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10

Bug #1857996 reported by GG
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
virtualbox (Ubuntu)
New
Undecided
Unassigned

Bug Description

Microsoft submachine during upgrade

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: virtualbox-dkms 6.0.6-dfsg-1
ProcVersionSignature: Microsoft 4.4.0-18362.476-Microsoft 4.4.35
Uname: Linux 4.4.0-18362-Microsoft x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
Date: Tue Dec 31 15:29:31 2019
Dmesg:
 [ 0.015026] Microsoft 4.4.0-18362.476-Microsoft 4.4.35
 [ 0.513193] <3>init: (1) ERROR: UtilCreateProcessAndWait:360: /bin/mount failed with status
 [ 0.513198] 2000
ErrorMessage: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
LsMod:
 Error: command ['lsmod'] failed with exit code 1: libkmod: ERROR ../libkmod/libkmod-module.c:1657 kmod_module_new_from_loaded: could not open /proc/modules: No such file or directory
 Error: could not get list of modules: No such file or directory
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1.1
 apt 1.8.3
SourcePackage: grub2
Title: package virtualbox-dkms 6.0.6-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10
UpgradeStatus: Upgraded to disco on 2019-12-31 (0 days ago)
VirtualBox.ModInfo: find: ‘/lib/modules/4.4.0-18362-Microsoft’: No such file or directory

Revision history for this message
GG (g-i-g) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Mate Kukri (mkukri) wrote :

It seems like the modules directory is not present for the kernel you are booted into. (I suspect due to being right after the kernel being autoremoved)

Rebooting into a kernel with a present modules directory should fix this.

Changed in grub2 (Ubuntu):
status: New → Invalid
no longer affects: grub2 (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.