nvidia-settings 387.22 or nvidia-settings 384.90 segfaults when trying to install

[Keith Myers]

Ubuntu is throwing a segfault when either it tries to retrieve and install the nvidia-settings for either 387.22 or 384.90.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-384 384.90-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
DKMSKernelVersion: 4.10.0-38-generic
Date: Wed Nov 8 12:27:10 2017
DuplicateSignature: dkms:nvidia-384:384.90-0ubuntu0.16.04.1:/var/lib/dkms/nvidia-384/384.90/build/conftest/functions.h:14:2: error: #error kmem_cache_create() conftest failed!
InstallationDate: Installed on 2017-07-26 (104 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageVersion: 384.90-0ubuntu0.16.04.1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
SourcePackage: nvidia-graphics-drivers-384
Title: nvidia-384 384.90-0ubuntu0.16.04.1: nvidia-384 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

[Cedric Viou (cedric-dv)]

With:
LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:printing-9.20160110ubuntu0.2-amd64:printing-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

I use this nvidia driver:
nvidia-384 384.90-0ubuntu0.16.04.1 amd64

I can boot with:
linux-image-4.10.0-37-generic 4.10.0-37.41~16.04.1 amd64

But it breaks (before I enter a passphrase to decrypt my drive) with this kernel:
linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 amd64

What logs can I provide or what test can I run to help confirm this bug?

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