[Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.

Launchpad Bug Tracker 1943160 at bugs.launchpad.net
Mon Sep 13 15:09:26 UTC 2021


This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu2

---------------
nvidia-settings (470.57.01-0ubuntu2) impish; urgency=medium

  * debian/patches/17_do_not_read_config_on_power_saving_mode.patch:
    - Do not read config on Power Saving mode. (LP: #1943160).

 -- Shengyao Xue <shengyao.xue at canonical.com>  Fri, 10 Sep 2021 00:42:38
+0800

** Changed in: nvidia-settings (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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:
  In Progress

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




More information about the Ubuntu-sponsors mailing list