Ubuntu
virtualbox package

virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed to build

Bug #869517 reported by spontex on 2011-10-06

This bug report is a duplicate of: Bug #860656: virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed to build (/bin/sh: Cannot fork). Edit Remove

This bug affects 1 person

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

Bug Description

Automatic reporting of a bug when upgrading to Ubuntu 11.10 Beta 2

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: virtualbox-dkms 4.1.2-dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
DKMSKernelVersion: 2.6.38-11-generic
Date: Thu Oct 6 22:09:19 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
PackageArchitecture: all
PackageVersion: 4.1.2-dfsg-1ubuntu1
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.2-dfsg-1ubuntu1: virtualbox kernel module failed to build
UpgradeStatus: Upgraded to oneiric on 2011-10-06 (0 days ago)
VirtualBox.ModInfo:

Tags:

Revision history for this message

spontex (spontex) wrote on 2011-10-06:

DKMSBuildLog.txt Edit (4.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.0 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (4.5 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (2.1 KiB, text/plain; charset="utf-8")
VirtualBox.DpkgList.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2011-10-06

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-10-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 860656, 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.