virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I was installing "virtualbox-dkms" with apt-get at the terminal, and suddenly the terminal wrote:
Loading new virtualbox-4.1.12 DKMS files...
First Installation: checking all kernels...
Building only for 3.13.0-32-generic
Building initial module for 3.13.0-32-generic
Error! Bad return status for module build on kernel: 3.13.0-32-generic (i686)
Consult /var/lib/
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules
* No suitable module for running kernel found
invoke-rc.d: initscript virtualbox, action "restart" failed.
----
It was strange for me, because normally, when I install "virtualbox-dkms", there are no errors, but now there are some.
I hope, that they aren't fatal errors, which will cause the system to crash... but I also hope, that you, or the VirtualBox-team, can fix those errors.
I'm using Ubuntu 12.04.5 LTS (Release: 12.04), and the version of the defective program (virtualbox-dkms) is "4.1.12-
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-
ProcVersionSign
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
DKMSKernelVersion: 3.13.0-32-generic
Date: Sun Oct 5 18:31:39 2014
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1)
MarkForUpload: True
PackageArchitec
PackageVersion: 4.1.12-
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1292118, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.