Ubuntu
virtualbox-ose package

package virtualbox-ose-guest-dkms 3.1.6-dfsg-2ubuntu2 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build

Bug #772764 reported by roke99 on 2011-04-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

Binary package hint: virtualbox-ose

installing the 2.6.38.8 kernel in lucid this package crash

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-guest-dkms 3.1.6-dfsg-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-31.61-generic 2.6.32.32+drm33.14
Uname: Linux 2.6.32-31-generic i686
Architecture: i386
Date: Fri Apr 29 00:25:33 2011
ErrorMessage: virtualbox-ose-guest kernel module failed to build
InstallationMedia: Ubuntu 10.04.2 LTS "Lucid Lynx" - Release i386 (20110211.1)
PackageArchitecture: all
PackageVersion: 3.1.6-dfsg-2ubuntu2
SourcePackage: virtualbox-ose
Title: package virtualbox-ose-guest-dkms 3.1.6-dfsg-2ubuntu2 failed to install/upgrade: virtualbox-ose-guest kernel module failed to build

Tags:

Revision history for this message

roke99 (roke99s-gmail) wrote on 2011-04-28:

DKMSBuildLog.txt Edit (1.1 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (803 bytes, text/plain; charset="utf-8")
LsMod.txt Edit (3.0 KiB, text/plain; charset="utf-8")
VirtualBoxOse.DpkgList.txt Edit (2.1 KiB, text/plain; charset="utf-8")
VirtualBoxOse.ModInfo.txt Edit (2.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-06-15:

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