| 2022-01-11 15:40:32 |
jeremyszu |
bug |
|
|
added bug |
| 2022-01-11 15:40:39 |
jeremyszu |
ubuntu-drivers-common (Ubuntu): assignee |
|
jeremyszu (os369510) |
|
| 2022-01-12 04:16:58 |
jeremyszu |
bug task added |
|
oem-priority |
|
| 2022-01-12 04:17:05 |
jeremyszu |
oem-priority: assignee |
|
Dirk Su (dirksu) |
|
| 2022-01-12 04:22:23 |
jeremyszu |
ubuntu-drivers-common (Ubuntu): status |
New |
In Progress |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
bug task added |
|
ubuntu-drivers-common (Ubuntu Jammy) |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
nominated for series |
|
Ubuntu Impish |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
bug task added |
|
ubuntu-drivers-common (Ubuntu Impish) |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
nominated for series |
|
Ubuntu Focal |
|
| 2022-01-12 15:50:31 |
Alberto Milone |
bug task added |
|
ubuntu-drivers-common (Ubuntu Focal) |
|
| 2022-01-12 15:53:27 |
Alberto Milone |
ubuntu-drivers-common (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-01-12 16:06:51 |
Alberto Milone |
bug task deleted |
ubuntu-drivers-common (Ubuntu Focal) |
|
|
| 2022-01-12 16:07:10 |
Alberto Milone |
ubuntu-drivers-common (Ubuntu Impish): status |
New |
Triaged |
|
| 2022-01-17 09:30:04 |
Rex Tsai |
tags |
|
oem-priority |
|
| 2022-01-17 14:49:00 |
jeremyszu |
attachment added |
|
18-lp1957094-adjust-on-demand-mode-description.patch https://bugs.launchpad.net/oem-priority/+bug/1957094/+attachment/5554939/+files/18-lp1957094-adjust-on-demand-mode-description.patch |
|
| 2022-01-17 14:49:37 |
jeremyszu |
bug task added |
|
nvidia-settings (Ubuntu) |
|
| 2022-01-17 14:56:46 |
jeremyszu |
attachment added |
|
0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554940/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.patch |
|
| 2022-01-17 15:00:58 |
jeremyszu |
attachment added |
|
0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554941/+files/0001-lp1957094-fall-back-from-on-demand-to-ON-if-nvidia-l.focal.patch |
|
| 2022-01-17 15:07:22 |
jeremyszu |
attachment added |
|
18-lp1957094-adjust-on-demand-mode-description.focal.patch https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1957094/+attachment/5554942/+files/18-lp1957094-adjust-on-demand-mode-description.focal.patch |
|
| 2022-01-17 16:19:15 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority |
oem-priority patch |
|
| 2022-01-17 16:19:21 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Review Team |
| 2022-01-19 13:35:27 |
jeremyszu |
description |
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
|
| 2022-01-21 12:36:06 |
Robie Basak |
bug |
|
|
added subscriber Robie Basak |
| 2022-01-21 12:36:12 |
Robie Basak |
bug |
|
|
added subscriber Alberto Milone |
| 2022-01-25 13:19:26 |
Alberto Milone |
description |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
* While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
|
| 2022-02-02 03:34:15 |
Chris Halse Rogers |
ubuntu-drivers-common (Ubuntu Impish): status |
Triaged |
Fix Committed |
|
| 2022-02-02 03:34:18 |
Chris Halse Rogers |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-02-02 03:34:20 |
Chris Halse Rogers |
bug |
|
|
added subscriber SRU Verification |
| 2022-02-02 03:34:25 |
Chris Halse Rogers |
tags |
oem-priority patch |
oem-priority patch verification-needed verification-needed-impish |
|
| 2022-02-02 03:34:59 |
Chris Halse Rogers |
description |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
* While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
* install nvidia-450 on nvidia-450 supported system.
* prime-select on-demand
* <CHECK THAT ON-DEMAND HAS STUCK>
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
* While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
|
| 2022-02-02 04:24:34 |
Chris Halse Rogers |
ubuntu-drivers-common (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2022-02-02 04:24:41 |
Chris Halse Rogers |
tags |
oem-priority patch verification-needed verification-needed-impish |
oem-priority patch verification-needed verification-needed-focal verification-needed-impish |
|
| 2022-02-02 13:05:36 |
Alberto Milone |
description |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
* install nvidia-450 on nvidia-450 supported system.
* prime-select on-demand
* <CHECK THAT ON-DEMAND HAS STUCK>
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
* While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
[Impact]
* In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly.
[Test Plan]
* install nvidia-390 on nvidia-390 supported system.
* prime-select on-demand
* reboot
* glxinfo
* after applying this patch, it will fall back to "ON" mode after reboot.
* install nvidia-450 on nvidia-450 supported system.
* prime-select on-demand
* reboot the system
* prime-select query (and check that on-demand mode is still in use).
[Where problems could occur]
* Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode.
* From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is.
* While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX.
---
The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1942789.
It impacts Jammy and Impish so far.
[Steps to reproduce]
1. Find a GPU supports nvidia-390
2. ubuntu-drivers install nvidia:390
3. prime-select on-demand
4. glxinfo
[Expected result]
Shows intel or nvidia drives monitor
[Actual result]
Error: couldn't find RGB GLX visual or fbconfig
Since we are all agree "on-demand" mode as default mode.
Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3).
We could consider to make it as performance mode and leave a note on nvidia-settings.
I'll prepare some test packages. |
|
| 2022-02-03 18:32:16 |
Launchpad Janitor |
nvidia-settings (Ubuntu Jammy): status |
New |
Fix Released |
|
| 2022-02-11 15:00:52 |
Timo Aaltonen |
nvidia-settings (Ubuntu Impish): status |
New |
Fix Committed |
|
| 2022-02-11 15:22:16 |
Timo Aaltonen |
nvidia-settings (Ubuntu Focal): status |
New |
Fix Committed |
|
| 2022-02-14 08:56:18 |
Dirk Su |
tags |
oem-priority patch verification-needed verification-needed-focal verification-needed-impish |
oem-priority patch verification-done-focal verification-needed verification-needed-impish |
|
| 2022-02-14 10:00:14 |
Dirk Su |
tags |
oem-priority patch verification-done-focal verification-needed verification-needed-impish |
oem-priority patch verification-done verification-done-focal verification-done-impish |
|
| 2022-02-17 00:32:16 |
Launchpad Janitor |
nvidia-settings (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-02-17 00:32:22 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-02-17 00:32:45 |
Launchpad Janitor |
ubuntu-drivers-common (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2022-03-01 10:21:48 |
Launchpad Janitor |
ubuntu-drivers-common (Ubuntu Impish): status |
Fix Committed |
Fix Released |
|
| 2022-03-01 10:22:50 |
Launchpad Janitor |
nvidia-settings (Ubuntu Impish): status |
Fix Committed |
Fix Released |
|
| 2022-03-06 09:20:19 |
Mathew Hodson |
ubuntu-drivers-common (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-06-03 08:27:17 |
Yuan-Chen Cheng |
oem-priority: status |
New |
Fix Released |
|
