nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build [cc: error: unrecognized command line option ‘-fstack-protector-strong’]

[Deepak Yadav]

I get system error screen on booting.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-384 384.130-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
DKMSKernelVersion: 4.4.0-108-generic
Date: Thu Jul 19 23:54:45 2018
DuplicateSignature: dkms:nvidia-384:384.130-0ubuntu0.14.04.1:cc: error: unrecognized command line option ‘-fstack-protector-strong’
InstallationDate: Installed on 2018-01-04 (196 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageVersion: 384.130-0ubuntu0.14.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt 1.2.27
SourcePackage: nvidia-graphics-drivers-384
Title: nvidia-384 384.130-0ubuntu0.14.04.1: nvidia-384 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Leonidas S. Barbosa (leosilvab)]

Hi,

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.

Seems this issue is caused by the version of your compiler (gcc/g++). See this line in DKMSBuildlog: "Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler". Check your gcc version, if it's not major than 4.8 that can be the root cause. This flag was added in version >= 4.9.

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