Hello Shengyao, or anyone else affected, Accepted nvidia-settings into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/nvidia- settings/470.57.01-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943160 Title: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running. Status in OEM Priority Project: In Progress Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Committed Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: [Impact] On some I+N configs, It will take about 90+ seconds to open the 'Nvidia settings' window when 'Power Saving mode' running. [Fix] do not read config file if Nvidia driver did not loaded: change nvidia-settings/src/nvidia-settings.c if (!op->no_load) { ret = nv_read_config_file(op, op->config, op->ctrl_display, p, &conf, &systems); to if (!op->no_load && systems.n != 0) { ret = nv_read_config_file(op, op->config, op->ctrl_display, p, &conf, &systems); [Test] 1. Install Ubuntu image. 2. Boot and login the system. 3. Open 'Nvidia Settings' app 4. Select the prime is 'Power saving' mode 5. Reboot system and login 6. Open 'Nvidia Settings' app 7. Verify the result [Where problems will occur] the "systems.n" gets from NvCtrlConnectToSystem(op->ctrl_display, &systems); If there is a possibility that systems.n is zero and we still need to read nvidia config file, then it will be a problem. I tried and cannot find a situation like that. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
