Comment 3 for bug 1699110

I just logged into my system, the update-manager popped up and said there where a number of updates. When I told it to install them it went ahead, but in the middle of the update it reported that Ubuntu had experienced a problem (the update went on though) and when I reported it it offered me a largish number of issues that might be duplicates. I chose this one because it had the exact same subject line as the bug report generated for me.

I searched under /var/lib/dkms/ and there where no files named DKMSBuildLog.txt there. However, the was /var/lib/dkms/nvidia-375/375.66/4.4.0-83-generic/x86_64/log/make.log with a timestamp matching approximately when the error occurred. However, it didn't appear to have any errors in it.

/var/log/apt/term.log was slightly more interesting. It had the following in it:

Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
Error! Bad return status for module build on kernel: 4.4.0-83-generic (x86_64)
Consult /var/lib/dkms/nvidia-375/375.66/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-83-generic
W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that theme.
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-83-generic /boot/vmlinuz-4.4.0-83-generic

I'll attach it as well. The log file mentioned (/var/lib/dkms/nvidia-375/375.66/build/make.log) however, does not exist.