This bug was fixed in the package ubuntu-drivers-common - 1:0.10
---------------
ubuntu-drivers-common (1:0.10) plucky; urgency=medium
[ Kuba Pawlak]
* Add --include-dkms option to listing drivers (LP: #2090924)
* fix searching for lrm drivers matching linux-image-virtual (LP: #2085962)
* Don't remove SimpleDRM if nvidia has fbdev
* Don't remove SimpleDRM if nvidia does not have modesetting
* fix install --gpgpu handling (LP: #2083709)
* Sort the output list of matching nvidia drivers (LP: #2081970)
* NVIDIA 560 release should suggest -open variant first (LP: #2081967)
* Skip a test that fails after update of aptdaemon
[ Dann Frazier ]
* Add more useful help text for --gpgpu (LP: #2081881)
[ Alessandro Astone ]
* Improve SimpleDRM+NVIDIA fix across kernel versions (LP: #2060268)
[ Timo Aaltonen ]
* gpu-manager: Drop unused functions
* copyright: Fix a lintian warning.
* Drop obsolete constraints.
* rules: Remove built objects directly instead of running make clean.
* control, rules: Migrate to debhelper-compat 13 and pybuild.
* control: Migrate to pkgconf.
* control: Drop obsolete Breaks/Conflicts/Provides/Replaces.
* control: Drop ancient transitional packages fglrx-pxpress and nvidia-common.
-- Kuba Pawlak <kuba.paw...@canonical.com> Fri, 06 Dec 2024 16:51:26
+0100
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/2090924
Title:
introduce --include-dkms optional flag
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Bug description:
[ Impact ]
listing available drivers shows nvidia drivers that match the current
hardware installed, but it contains both drivers that are LRM prepared and the
ones that are DKMS only. This can happen in a time window between releasing new
drivers and respining LRM modules with these drivers. A user can therefore
select a driver that is DKMS only, which will break secure boot, as signed
drivers are provided in LRM package. A fix is to introduce a flag
'--include-dkms' that when not enabled will make u-d-c not show nvidia drivers
that have no LRM
[ Steps to reproduce ]
1. Add a PPA with nvidia-drivers that are not yet LRM prepared, in my case
2. Call 'ubuntu-drivers list'
3. observe the list of packages that is installed
a typical list would llook like this:
nvidia-driver-560-open, (kernel modules provided by nvidia-dkms-560-open)
nvidia-driver-550, (kernel modules provided by linux-modules-nvidia-550-aws)
nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-aws)
nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-aws)
First entry shows 'kernel modules provided by nvidia-dkms-560-open',
while all the others have: 'kernel modules provided by linux-modules-
nvidia-470-aws'. when a user chooses to install 560-open, by hand by
providing the version or by using '--recommended', his system will
have a broken Secure Boot as nvidia drivers are not signed.
[ Test plan ]
1. simulate the issue by adding a PPa with a driver line that is not yet LRM
prepare, in my case it's
https://launchpad.net/~kuba-t-pawlak/+archive/ubuntu/nvidia-560
2. Call 'ubuntu-drivers list' with and without '--include-dkms'
[ Expected result ]
without '--include-dkms' the list of available drivers should not contain any
entry that has (kernel modules provided by nvidia-dkms-YYY-ZZZ) in it, only the
ones with (kernel modules provided by linux-modules-nvidia-XXX-YYY)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2090924/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
