Ubuntu
open-vm-tools package

open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module failed to build

Bug #1461105 reported by John Duggins on 2015-06-02

This bug report is a duplicate of: Bug #1312855: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build [error: implicit declaration of function 'create_proc_entry']. Edit Remove

This bug affects 1 person

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

Bug Description

Base build and installation/build of modules fails.
Installation of linux-headers-server and reinstallation of open-vm-tools and open-vm-dkms not found to fix the problem.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: open-vm-dkms 2011.12.20-562307-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.13.0-45.74~precise1-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.9
Architecture: amd64
DKMSKernelVersion: 3.13.0-45-generic
Date: Tue Jun 2 04:49:54 2015
InstallationMedia: SecurityOnion 12.04 - Release amd64
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 2011.12.20-562307-0ubuntu1.1
SourcePackage: open-vm-tools
Title: open-vm-dkms 2011.12.20-562307-0ubuntu1.1: open-vm-tools kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

John Duggins (jduggins) wrote on 2015-06-02:

DKMSBuildLog.txt Edit (14.8 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (829 bytes, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (14.7 KiB, text/plain; charset="utf-8")

Apport retracing service (apport) on 2015-06-02

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2015-06-03:

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