Ubuntu
open-vm-tools package

open-vm-dkms 2011.07.19-450511-0ubuntu2: open-vm-tools kernel module failed to build

Bug #902802 reported by Jerry on 2011-12-11

This bug report is a duplicate of: Bug #898289: open-vm-dkms 2011.07.19-450511-0ubuntu2: open-vm-tools kernel module failed to build [error: assignment of read-only member ‘i_nlink’]. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	open-vm-tools (Ubuntu)	New	Undecided	Unassigned

Bug Description

apt-get update upgrade said the kernel was Kept Back,
so used synaptic to try to install it...

will not install according to the error.
open-vm-tools package on some dkms
kernel module build

all trying to get testdrive-gtk to run
so I installed other virtualization stuff
and some of it's not working...

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: open-vm-dkms 2011.07.19-450511-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
DKMSKernelVersion: 3.2.0-4-generic
Date: Sun Dec 11 09:48:39 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
PackageArchitecture: all
PackageVersion: 2011.07.19-450511-0ubuntu2
SourcePackage: open-vm-tools
Title: open-vm-dkms 2011.07.19-450511-0ubuntu2: open-vm-tools kernel module failed to build
UpgradeStatus: Upgraded to precise on 2011-11-25 (15 days ago)

Tags:

Revision history for this message

Jerry (jerrywone) wrote on 2011-12-11:

DKMSBuildLog.txt Edit (26.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (775 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (26.4 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2011-12-11

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2011-12-12:

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