Ubuntu
virtualbox package

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

Bug #860843 reported by seppi huber on 2011-09-27

This bug report is a duplicate of: Bug #858279: linux header files not installed on Lubuntu 11.10 beta2. Edit Remove

This bug affects 1 person

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

Bug Description

install failed

ProblemType: Package
DistroRelease: Ubuntu 11.10
Package: virtualbox-guest-dkms 4.1.2-dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
DKMSKernelVersion: 3.0.0-11-generic
Date: Tue Sep 27 21:34:58 2011
DuplicateSignature:
DKMS make.log for virtualbox-guest-4.1.2 for kernel 3.0.0-11-generic (x86_64)
make: Entering directory `/usr/src/linux-headers-3.0.0-11-generic'
make: Makefile: No such file or directory
make: *** No rule to make target `Makefile'. Stop.
make: Leaving directory `/usr/src/linux-headers-3.0.0-11-generic'
PackageArchitecture: all
PackageVersion: 4.1.2-dfsg-1ubuntu1
SourcePackage: virtualbox
Title: virtualbox-guest-dkms 4.1.2-dfsg-1ubuntu1: virtualbox-guest kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

seppi huber (svrci) wrote on 2011-09-27:

DKMSBuildLog.txt Edit (334 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.0 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2011-09-27

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-09-28:

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