virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virtualbox (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Failure during installation.
* Stopping VirtualBox kernel modules [ OK ]
* Starting VirtualBox kernel modules * No suitable module for running kernel found
invoke-rc.d: initscript virtualbox, action "restart" failed.
Processing triggers for python-central ...
Setting up virtualbox-dkms (4.1.12-
Loading new virtualbox-4.1.12 DKMS files...
First Installation: checking all kernels...
Building only for 3.5.0-28-generic
Building initial module for 3.5.0-28-generic
Error! Bad return status for module build on kernel: 3.5.0-28-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.
Setting up virtualbox-qt (4.1.12-
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Processing triggers for menu ...
kim@kim-
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-
ProcVersionSign
Uname: Linux 3.5.0-28-generic i686
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
DKMSKernelVersion: 3.5.0-28-generic
Date: Tue May 7 08:24:30 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213)
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:
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1176825, so 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. Please continue to report any other bugs you may find.