Ubuntu
virtualbox-ose package

package virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1~lucid1 failed to install/upgrade: virtualbox-ose kernel module failed to build

Bug #896542 reported by shailesh99 on 2011-11-26

This bug report is a duplicate of: Bug #705593: package virtualbox-ose-dkms * failed to install/upgrade: virtualbox-ose kernel module failed to build (types.h:97:31: fatal error: linux/autoconf.h: No such file or directory). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	virtualbox-ose (Ubuntu)	New	Undecided	Unassigned

Bug Description

Every time I try installing Virtual Box the system gives me this error:
"No suitable module for running kernel found"
I tried to search for a solution to fix the problem but wasn't lucky enough to do so.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1~lucid1
ProcVersionSignature: Ubuntu 2.6.38-13.52~lucid1-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
Architecture: i386
Date: Sat Nov 26 04:27:22 2011
ErrorMessage: virtualbox-ose kernel module failed to build
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
PackageArchitecture: all
PackageVersion: 3.2.8-dfsg-2ubuntu1~lucid1
SourcePackage: virtualbox-ose
Title: package virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1~lucid1 failed to install/upgrade: virtualbox-ose kernel module failed to build
VirtualBoxOse.ModInfo:

Tags:

Revision history for this message

shailesh99 (shailesh99) wrote on 2011-11-26:

DKMSBuildLog.txt Edit (1.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (822 bytes, text/plain; charset="utf-8")
LsMod.txt Edit (2.0 KiB, text/plain; charset="utf-8")
VirtualBoxOse.DpkgList.txt Edit (3.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-11-27:

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 705593, 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.