Ubuntu
virtualbox package

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

Bug #1325022 reported by Sean Kennedy on 2014-05-30

This bug report is a duplicate of: Bug #1292118: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build [error: incompatible types when returning type ‘kuid_t’ but ‘RTUID’ was expected]. Edit Remove

This bug affects 1 person

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

Bug Description

VirtualBox DKMS build fails on 12.04 against the 3.13.0-27 backported kernel.

Here is the termnial output:
Loading new virtualbox-guest-4.1.12 DKMS files...
Building only for 3.13.0-27-generic
Building initial module for 3.13.0-27-generic
Error! Bad return status for module build on kernel: 3.13.0-27-generic (x86_64)

I'll include the whole log as an attachment (if it didn't happen automatically), but these are the build errors:
CC [M] /var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.o
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c: In function ‘sf_init_inode’:
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c:147:18: error: incompatible types when assigning to type ‘kuid_t’ from type ‘int’
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c:148:18: error: incompatible types when assigning to type ‘kgid_t’ from type ‘int’
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c: In function ‘sf_nlscpy’:
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c:575:13: warning: passing argument 3 of ‘utf8_to_utf32’ from incompatible pointer type [enabled by default]
include/linux/nls.h:53:12: note: expected ‘unicode_t *’ but argument is of type ‘wchar_t *’
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c: At top level:
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c:841:1: warning: initialization from incompatible pointer type [enabled by default]
/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.c:841:1: warning: (near initialization for ‘sf_dentry_ops.d_revalidate’) [enabled by default]
make[2]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf/utils.o] Error 1
make[1]: *** [/var/lib/dkms/virtualbox-guest/4.1.12/build/vboxsf] Error 2
make: *** [_module_/var/lib/dkms/virtualbox-guest/4.1.12/build] Error 2
make: Leaving directory `/usr/src/linux-headers-3.13.0-27-generic'

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6
ProcVersionSignature: Ubuntu 3.13.0-27.50~precise1-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-27-generic
Date: Fri May 30 12:30:05 2014
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
PackageArchitecture: all
PackageVersion: 4.1.12-dfsg-2ubuntu0.6
SourcePackage: virtualbox
Title: virtualbox-dkms 4.1.12-dfsg-2ubuntu0.6: virtualbox kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
VirtualBox.ModInfo:

Tags:

Revision history for this message

Sean Kennedy (sean-worker) wrote on 2014-05-30:

make.log Edit (9.7 KiB, text/plain)
DKMSBuildLog.txt Edit (2.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
DuplicateSignature.txt Edit (2.0 KiB, text/plain; charset="utf-8")
LsMod.txt Edit (4.6 KiB, text/plain; charset="utf-8")
VirtualBox.DpkgList.txt Edit (3.2 KiB, text/plain; charset="utf-8")

Revision history for this message

Sean Kennedy (sean-worker) wrote on 2014-06-17:

With the 3.13.0-29 kernel the problem persists.
See bug #1330954

Apport retracing service (apport) on 2014-07-01

tags:

removed: need-duplicate-check

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2014-07-01:

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.