Ubuntu
virtualbox-ose package

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

Bug #1027473 reported by 陈伟琪 on 2012-07-21

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

尽管在ubuntu 10.04 上使用3.4.0的内核是非常冒险的，但因为这台机器的特殊，我目前别无选择。希望这个问题能尽快修复。

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2
Uname: Linux 3.4.0-030400-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Sun Jul 22 03:20:25 2012
ErrorMessage: virtualbox-ose kernel module failed to build
InstallationMedia: Ubuntu 10.04.4 LTS "Lucid Lynx" - Release amd64 (20120214)
PackageArchitecture: all
PackageVersion: 3.1.6-dfsg-2ubuntu2
SourcePackage: virtualbox-ose
Title: package virtualbox-ose-dkms 3.1.6-dfsg-2ubuntu2 failed to install/upgrade: virtualbox-ose kernel module failed to build
VirtualBoxOse.ModInfo:

Tags:

Revision history for this message

陈伟琪 (gameboy709494) wrote on 2012-07-21:

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

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2012-07-23:

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.