nvidia-304 304.132-0ubuntu2: nvidia-304 kernel module failed to build

[Karma Dorje]

this is an automated bug report.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: nvidia-304 304.132-0ubuntu2
ProcVersionSignature: Ubuntu 4.9.0-6.7-generic 4.9.0-rc7
Uname: Linux 4.9.0-6-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
BootLog:
 [ OK ] Started Run Click system-level hooks.
 [ OK ] Started Detect the available GPUs and deal with any system changes.
          Starting Light Display Manager...
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 4.9.0-6-generic
Date: Sat Dec 3 20:51:14 2016
DistUpgraded: 2016-10-30 16:17:00,307 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Не удалось выполнить процесс-потомок «./xorg_fix_proprietary.py» (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
DuplicateSignature: dkms:nvidia-304:304.132-0ubuntu2:/var/lib/dkms/nvidia-304/304.132/build/nv-mlock.c:53:55: error: passing argument 5 of ‘get_user_pages’ from incompatible pointer type [-Werror=incompatible-pointer-types]
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:1652]
 NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
InstallationDate: Installed on 2015-08-05 (486 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: ASUSTeK Computer Inc. K53SD
PackageVersion: 304.132-0ubuntu2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-generic root=UUID=345666d5-2bc5-4e79-ac8e-98aaf57127e1 ro persistent resume=/dev/sda7 apparmor=1 security=apparmor
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.4~beta1
SourcePackage: nvidia-graphics-drivers-304
Title: nvidia-304 304.132-0ubuntu2: nvidia-304 kernel module failed to build
UpgradeStatus: Upgraded to zesty on 2016-10-30 (34 days ago)
dmi.bios.date: 03/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53SD.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K53SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK53SD.205:bd03/06/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.13.1+17.04.20161114.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.74-1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
xserver.bootTime: Sat Dec 3 22:25:43 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu7
xserver.video_driver: modeset

[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 1642241, 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.