nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build

[Charlito G. Piao Jr.]

While updating, this error came up.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.104-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.driver.nvidia.gpus.0000.04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017
 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
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.4.0-121-generic
Date: Tue Apr 24 05:06:56 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DuplicateSignature: dkms:nvidia-340:340.104-0ubuntu0.16.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Haswell-ULT Integrated Graphics Controller [1025:0854]
   Subsystem: Acer Incorporated [ALI] GeForce 820M [1025:0854]
InstallationDate: Installed on 2017-12-19 (125 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Acer TravelMate P245-MG
PackageVersion: 340.104-0ubuntu0.16.04.1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4d12c7af-9f07-43b8-9750-e6126b6ba612 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.26
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia-340 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.04
dmi.board.asset.tag: No Asset Tag
dmi.board.name: BA40_HW
dmi.board.vendor: Acer
dmi.board.version: V2.04
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.04
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.04:bd10/14/2013:svnAcer:pnTravelMateP245-MG:pvrV2.04:rvnAcer:rnBA40_HW:rvrV2.04:cvnAcer:ct9:cvrV2.04:
dmi.product.family: TravelMate P245-MG
dmi.product.name: TravelMate P245-MG
dmi.product.version: V2.04
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Apr 23 23:36:00 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
 NVIDIA(0): Failed to initiate mode change.
 NVIDIA(0): Failed to complete mode change
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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