Ubuntu
virtualbox package

virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build

Bug #1157394 reported by Sh4d on 2013-03-19

This bug report is a duplicate of: Bug #1016165: virtualbox-guest-dkms 4.1.16-dfsg-2: virtualbox-guest kernel module failed to build [error: implicit declaration of function ‘do_mmap’]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	virtualbox (Ubuntu)	New	Undecided	Unassigned

Bug Description

no other info

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-25.39~precise1-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
DKMSKernelVersion: 3.5.0-25-generic
Date: Tue Mar 19 20:54:13 2013
InstallationMedia:

MarkForUpload: True
PackageArchitecture: all
PackageVersion: 4.1.12-dfsg-2ubuntu0.2
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

Tags:

Revision history for this message

Sh4d (sh4d0000) wrote on 2013-03-19:

DKMSBuildLog.txt Edit (1.9 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.3 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (1.8 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (2.4 KiB, text/plain; charset="utf-8")
VirtualBox.DpkgList.txt Edit (1.9 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2013-03-19

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2013-03-20:

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