@SRU team To add to this issue, it is timing related. We release nvidia dkms drivers, which can be installed by themselves, but this means module compilation on the machine so it breaks secure boot. Therefore we also create Linux Restricted Modules (LRM) that are nvidia drivers precompiled by us against all kernels and signed so when installed they don't break secure boot. Now, nvidia drivers are released to -proposed before LRMs are built. This creates a window when someone using ubuntu- drivers may install nvidia dkms drivers and not LRM drivers, resulting in their system having secure boot disabled, which is not an option for cloud environments. Another windows of opportunity to trigger this is during publication to the archives. A dkms drivers may already be published but LRMs for the specific kernel are not there yet. The decision was made that dkms drivers should not be available to be installed by accident so hidden behind a switch. An advanced user would use it, therefore ensuring that they know what they're doing.
Due to timing related nature of this issue, testing it in real world scenario would require timing the verification to a few hour window once a fortnight or so (varies), therefore to force it, an extra PPA with a newer driver is created. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2098674 Title: ubuntu-drivers install --include-dkms installs dkms only package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2098674/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
