New kernel update doesn't reconfigure nvidia package

[zaf]

I have had this bug for a while now but only figured out the fix recently.
Basically after each new kernel update in Ubuntu Gnome 17.04, when starting the computer, GDM doesn't start.
I have to go to a terminal using Ctrl - Alt - F2 and launch a

"sudo dpkg-reconfigure nvidia-375"

and then
"sudo service gdm3 restart"

And that's how I get my desktop back.
This has been happening regularly at least since I upgrade to 17.04 (maybe even since 16.10). I think it might be occuring in 16.04 LTS as well as I have a colleague who's experienced something similar.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017
 GCC version: gcc version 4.9.4 (Ubuntu 4.9.4-2ubuntu1)
ApportVersion: 2.20.4-0ubuntu4.1
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Thu Jul 6 09:36:31 2017
DistUpgraded: 2017-05-10 08:22:23,207 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK104 [GeForce GTX 760 OEM] [10de:118e] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company GK104 [GeForce GTX 760 OEM] [103c:6892]
InstallationDate: Installed on 2015-06-23 (743 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Acer Predator G3-605
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic.efi.signed root=UUID=da125261-3dd9-44ae-b88b-15634f861769 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to zesty on 2017-05-10 (57 days ago)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P11-C0
dmi.board.name: Predator G3-605
dmi.board.vendor: Acer
dmi.chassis.type: 3
dmi.chassis.vendor: Acer
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-C0:bd04/01/2014:svnAcer:pnPredatorG3-605:pvr:rvnAcer:rnPredatorG3-605:rvr:cvnAcer:ct3:cvr:
dmi.product.name: Predator G3-605
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1
xserver.bootTime: Thu Jul 6 09:33:02 2017
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.19.3-1ubuntu1

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.