Ubuntu
virtualbox-ose package

virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2.1: virtualbox-ose kernel module failed to build

Bug #1208856 reported by Nick Dickens on 2013-08-06

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 just upgraded from 10.04 to 12.04 and this package failed to build during that process.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2.1
ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14
Uname: Linux 2.6.32-31-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: amd64
DKMSKernelVersion: 3.2.0-51-generic
Date: Tue Aug 6 14:47:36 2013
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 3.1.6-dfsg-2ubuntu2.1
SourcePackage: virtualbox-ose
Title: virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2.1: virtualbox-ose kernel module failed to build
UpgradeStatus: Upgraded to precise on 2013-08-06 (0 days ago)

Tags:

Revision history for this message

Nick Dickens (nick-dickens) wrote on 2013-08-06:

DKMSBuildLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (828 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (1.1 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2013-08-06

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-08-07:

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.