This bug was fixed in the package nvidia-prime - 0.8.17.1
---------------
nvidia-prime (0.8.17.1) impish; urgency=medium
* prime-select:
- Don't check the current profile when setting
a profile (LP: #1946476).
-- Alberto Milone <[email protected]> Fri, 08 Oct 2021
14:25:10 +0200
** Changed in: nvidia-prime (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1946476
Title:
New on-demand default causes RTD3 never to be enabled
Status in nvidia-prime package in Ubuntu:
Fix Released
Bug description:
As per LP: #1942307 we now set on-demand as the default. This however,
causes "prime-select on-demand", called by ubuntu-drivers, not to even
try to detect RTD3 and to enable it, since "on-demand" is already set.
We cannot make informed choices about RTD3 in the postinstallation
script of nvidia-prime, therefore we should simply drop the check that
prime-select makes to abort if the new profile is determined to be the
same as the current profile.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1946476/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
