Public bug reported:
The linux-restricted-modules package exists so that users who install
the nvidia drivers can get known-good, signed modules instead of having
to locally self-sign and enroll a signing key through MOK. But lrm in
eoan is only building driver packages for nvidia 390 and 430, and nvidia
435 is present in eoan.
So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
newest driver instead of using the signed 430 driver.
We should never allow the archive to get into this situation. We should
be enforcing that any version of the nvidia driver that we expect
ubuntu-drivers to install by default on any hardware is integrated into
linux-restricted-modules, and we should ensure that ubuntu-drivers
always prefers the signed drivers over other options.
** Affects: linux-restricted-modules (Ubuntu)
Importance: High
Status: New
** Affects: nvidia-graphics-drivers-435 (Ubuntu)
Importance: High
Status: New
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: High
Status: New
** Changed in: linux-restricted-modules (Ubuntu)
Importance: Undecided => High
** Also affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-435 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-435 (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856407
Title:
nvidia-435 is in eoan, linux-restricted-modules only builds against
430, ubiquity gives me the self-signed modules experience instead of
using the Canonical-signed modules
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1856407/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
