Ubuntu
virtualbox-ose package

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

Bug #815961 reported by kumaresan on 2011-07-25

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

i do not know

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Sat Jul 23 15:04:30 2011
ErrorMessage: virtualbox-ose kernel module failed to build
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
PackageVersion: 3.2.8-dfsg-2ubuntu1
SourcePackage: virtualbox-ose
Title: package virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1 failed to install/upgrade: virtualbox-ose kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBoxOse.ModInfo:

Tags:

Revision history for this message

kumaresan (cskumaresan) wrote on 2011-07-25:

DKMSBuildLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1006 bytes, text/plain; charset="utf-8")
LsMod.txt Edit (1.7 KiB, text/plain; charset="utf-8")
VirtualBoxOse.DpkgList.txt Edit (1.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-07-26:

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.