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 #951949 reported by gra2uitous on 2012-03-11

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

While performing a System Update on Ubuntu 10.04 the package failed to update and generated this automatic response.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-dkms 3.2.8-dfsg-2ubuntu1~lucid1
ProcVersionSignature: Ubuntu 2.6.38-13.56~lucid1-generic 2.6.38.8
Uname: Linux 2.6.38-13-generic i686
Architecture: i386
Date: Sun Mar 11 09:45:15 2012
ErrorMessage: virtualbox-ose kernel module failed to build
InstallationMedia: Mythbuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
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

gra2uitous (gra2uitous) wrote on 2012-03-11:

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

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-03-11:

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.