Ubuntu
open-vm-tools package

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

Bug #1379273 reported by Janos on 2014-10-09

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

Error occured during/after upgrading hardware support via the update manger

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: open-vm-dkms 2011.12.20-562307-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-37.64~precise1-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu17.7
Architecture: amd64
DKMSKernelVersion: 3.13.0-37-generic
Date: Thu Oct 9 17:09:37 2014
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 2011.12.20-562307-0ubuntu1
SourcePackage: open-vm-tools
Title: open-vm-dkms 2011.12.20-562307-0ubuntu1: open-vm-tools kernel module failed to build
UpgradeStatus: Upgraded to precise on 2014-06-23 (107 days ago)

Tags:

Revision history for this message

Janos (janosbeaumont) wrote on 2014-10-09:

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

Apport retracing service (apport) on 2014-10-09

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-10-10:

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.