virtualbox-dkms 4.1.12-dfsg-2: virtualbox kernel module failed to build

[OCaml]

ubuntu13.10 upgrade to ubuntu14.04
Linux OCamel 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
linux-image-3.11.0-13-generic - Linux kernel image for version 3.11.0 on 64 bit x86 SMP

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: virtualbox-dkms 4.1.12-dfsg-2
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
DKMSKernelVersion: 3.14.0-031400-generic
Date: Mon Jun 9 10:22:40 2014
DuplicateSignature: dkms:virtualbox-dkms:4.1.12-dfsg-2:/var/lib/dkms/virtualbox/4.1.12/build/vboxdrv/linux/SUPDrv-linux.c:226:5: error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected
InstallationDate: Installed on 2013-11-26 (194 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
PackageArchitecture: all
PackageVersion: 4.1.12-dfsg-2
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-dfsg-2: virtualbox kernel module failed to build
UpgradeStatus: Upgraded to trusty on 2014-04-28 (42 days ago)
VirtualBox.ModInfo:

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Daniel van Vugt (vanvugt)]

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