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
dockerino@
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
libgsoap1 python-central virtualbox virtualbox-dkms virtualbox-
Suggested packages:
vde2
The following NEW packages will be installed:
libgsoap1 python-central virtualbox virtualbox-dkms virtualbox-
0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
Need to get 64.1 MB of archives.
After this operation, 121 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://
Get:2 http://
Get:3 http://
Get:4 http://
Get:5 http://
Get:6 http://
Get:7 http://
Fetched 64.1 MB in 1min 14s (862 kB/s)
Selecting previously unselected package libgsoap1.
(Reading database ... 240987 files and directories currently installed.)
Unpacking libgsoap1 (from .../libgsoap1_
Selecting previously unselected package python-central.
Unpacking python-central (from .../python-
Selecting previously unselected package virtualbox.
Unpacking virtualbox (from .../virtualbox_
Selecting previously unselected package virtualbox-dkms.
Unpacking virtualbox-dkms (from .../virtualbox-
Selecting previously unselected package virtualbox-qt.
Unpacking virtualbox-qt (from .../virtualbox-
Selecting previously unselected package virtualbox-
Unpacking virtualbox-
Selecting previously unselected package virtualbox-
Unpacking virtualbox-
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Processing triggers for shared-mime-info ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for bamfdaemon ...
Rebuilding /usr/share/
Processing triggers for gnome-menus ...
Setting up libgsoap1 (2.8.4-2) ...
Setting up python-central (0.6.17ubuntu2) ...
Setting up virtualbox (4.1.12-
* 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-
Setting up virtualbox-
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.13.0-37-generic
Building initial module for 3.13.0-37-generic
Error! Bad return status for module build on kernel: 3.13.0-37-generic (x86_64)
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
dockerino@
Description: Ubuntu 12.04.5 LTS
Release: 12.04
dockerino@
virtualbox-
Installed: 4.1.12-1
Candidate: 4.1.12-1
Version table:
*** 4.1.12-1 0
500 http://
100 /var/lib/
Expected install to succeed but it failed.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-
ProcVersionSign
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.7
Architecture: amd64
DKMSKernelVersion: 3.13.0-37-generic
Date: Tue Oct 21 17:36:51 2014
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204)
MarkForUpload: True
PackageArchitec
PackageVersion: 4.1.12-
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-
UpgradeStatus: No upgrade log present (probably fresh install)
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.