This bug was fixed in the package dkms - 2.3-3ubuntu1
---------------
dkms (2.3-3ubuntu1) zesty; urgency=medium
* 0013-postinst-Fix-newest-kernel-detection.patch: dkms_common.postinst: We
were passing a list of kernels to get_newest_kernel(), when it expected a
single kernel as its first argument - the currently running kernel. This
in turn meant that the sometimes (if the first thing in the list was
itself the newest kernel), the wrong kernel was passed into
_get_newest_kernel_debian(). As a result this falsely reported that there
was no 'newest' kernel available and then didn't build modules for it.
Drop the parameter to get_newest_kernel(), and instead rely on
CURRENT_KERNEL being set to $(uname -r). (LP: #1681566)
-- Iain Lane <[email protected]> Thu, 13 Apr 2017 15:50:18
+0100
** Changed in: dkms (Ubuntu Zesty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681566
Title:
nvidia-375 DKMS module not recompiled on upgrade to 17.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1681566/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
