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 on backported kernel (from natty)

Bug #817681 reported by adam_993 on 2011-07-28

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

Detected when I was installing kernel 2.6.38.10, backported from Ubuntu 11.04 (lucid-backports)

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1~lucid1
ProcVersionSignature: Ubuntu 2.6.32-33.71-generic 2.6.32.41+drm33.18
Uname: Linux 2.6.32-33-generic i686
Architecture: i386
Date: Thu Jul 28 21:07:50 2011
ErrorMessage: virtualbox-ose kernel module failed to build
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

Tags:

Revision history for this message

adam_993 (adamr) wrote on 2011-07-28:

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

Revision history for this message

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

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.