[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
First of all, sorry for the inconvenience. The problem was caused by some missing dependencies which were not yet available in the archive. We are going to look into ways to make the update process more robust. Thank you for reporting the problem. ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Triaged ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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
[Desktop-packages] [Bug 1966413] Re: [SRU] --no-oem option is broken
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Lunar) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress -- 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/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: In Progress Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** Tags removed: verification-needed verification-needed-focal verification-needed-jammy ** Tags added: verification-done verification-done-jammy verification-needed-done -- 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
Any reason for not releasing 0.9.6.2~0.22.04.3 to jammy-updates?
--
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/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Bionic:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Jammy:
Fix Committed
Status in ubuntu-drivers-common source package in Kinetic:
Fix Released
Bug description:
[ Impact ]
* The introduction of the -open NVIDIA drivers requires a change in
the way we detect driver series and flavours. Failing to do so, causes
the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the
-open drivers over the non-open ones (LP: #1988836).
* Furthermore, calling the ubuntu-drivers tool where the alsa-utils
package is not installed (mainly on servers), ubuntu-drivers (through
the sl-modem plugin) complains, unnecessarily about the missing aplay
binary.
[ Test Plan ]
* Install the new ubuntu-drivers-common from -proposed on a system
where the GPU is compatible with the 515 series (or higher).
* Run the ubuntu-drivers list command, and make sure that the 515
driver series (or higher) is listed.
* Try installing the driver using the following command:
sudo ubuntu-drivers install
* Check which driver series was installed (you can use the "sudo
ubuntu-drivers debug" command), and make sure that the installation
does not cause ubuntu-drivers to crash.
[ Where problems could occur ]
* A problem in the ubuntu-drivers tool can cause it to install a driver which
is not recommended for the detected hardware, or even cause the package
installation to fail, and prevent users from logging in through the
graphics interface.
[ Other Info ]
* To prevent failures of the test-suite on architectures such as armhf (as
seen
in Lunar), we are skipping the tests for any architectures other than amd64
and arm64 (which are the only ones actually using ubuntu-drivers).
This was already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
- Update regex in nvidia_desktop_pre_installation_hook. This prevents
ubuntu-drivers from crashing when dealing with the -open NVIDIA
drivers (LP: #1993019).
* tests/test_ubuntu_drivers.py:
- Add tests so we make sure to keep preferring non-open NVIDIA
modules over the -open ones, at least until the open modules catch up
feature wise and performance wise.
[ gongzhengyang ]
* UbuntuDrivers/detect.py:
- Fix local variable 'version' being referenced before assignment
when catching ValueError (LP: #1993019).
[ Jeff Lane ]
* detect-plugins/sl-modem.py:
- Add some error trapping when aplay is not installed (on servers).
=== Jammy only (left over from 1:0.9.6.2~0.22.04.1) ===
* UbuntuDrivers/detect.py:
- Make sure -open drivers have a lower priority (LP: #1988836).
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* debian/rules:
- Limit the tests to the selected architectures (amd64, arm64).
This prevents armhf builds from failing.
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
- Update regex and unify package name parsing in the following
functions by using the new NvidiaPkgNameInfo class:
nvidia_desktop_pre_installation_hook,
_get_headless_no_dkms_metapackage,
nvidia_desktop_pre_installation_hook,
get_linux_modules_metapackage,
This prevents ubuntu-drivers from crashing when dealing with
the -open NVIDIA drivers (LP: #1993019).
* tests/test_ubuntu_drivers.py:
- Add tests so we make sure to keep preferring non-open NVIDIA
modules over the -open ones, at least until the open modules catch up
feature wise and performance wise.
[ gongzhengyang ]
* UbuntuDrivers/detect.py:
- Fix local variable 'version' being referenced before assignment
when catching ValueError (LP: #1993019).
[ Jeff Lane ]
* detect-plugins/sl-modem.py:
- Add some error trapping when aplay is not installed (on servers).
=== Jammy only (left over from 1:0.9.6.2~0.22.04.1) ===
* UbuntuDrivers/detect.py:
- Make
[Desktop-packages] [Bug 2019016] Re: nvidia_desktop_pre_installation_hook raises on package names with suffixes
Hi Fox, can you try ubuntu-drivers 1:0.9.6.2~0.22.04.3 from proposed,
please?
The problem should be LP: #1993019
--
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/2019016
Title:
nvidia_desktop_pre_installation_hook raises on package names with
suffixes
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
The function nvidia_desktop_pre_installation_hook in
/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py on Ubuntu
22.04.2 LTS assumes that the driver package name ends with the driver
version as the suffix.
However this does not account for the '-open' drivers. The following
code from that function is at fault:
```
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1]) # <--- This here
with_nvidia_kms = version >= 470
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470 # <-- And this here, too,
which will never succeed.
```
The line `version = int(package_name.split('-')[-1])` assumes a
package name like `nvidia-driver-530` rather than `nvidia-
driver-530-open`, however `nvidia-driver-530-open` is the autoselected
package for my install.
This code could be fixed by switching to a regex, or else retrying
with index -2 rather than index -1.
Also, the `finally` clause will always fail-- there should only ever
be one matching `nvidia-driver-` prefixed package, and if that raises
a ValueError, then `version` will not be set, raising an
UnboundLocalError.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-drivers-common 1:0.9.6.1 [modified:
usr/lib/python3/dist-packages/UbuntuDrivers/detect.py]
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue May 9 10:47:07 2023
InstallationDate: Installed on 2022-08-20 (261 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/zsh
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2019016/+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
[Desktop-packages] [Bug 1966413] Re: --no-oem option is broken
** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1966413 Title: --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/bin/ubuntu-drivers", line 376, in greet config.no_oem = install_oem_meta NameError: name 'install_oem_meta' is not defined ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-drivers-common 1:0.9.0~0.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
@Brian: did you update the initramfs after blacklisting the module? sudo update-initramfs -u -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
@Brian: by default, the b43 driver won't override the bcma driver (unless you force it to, of course). As for ubuntu-drivers, it does things correctly, meaning that it lists the compatible proprietary driver (broadcom-sta-dkms), without recommending its installation (over the open driver). The "Additional Drivers" interface (software-properties-gtk) lies - even here on my 2011 Macbook Air (with a BCM43224 wifi card, which I am using though the bcma driver - showing the Broadcom device, and saying that the "device is not working", and having "Do not use the device" selected. This is very confusing, although not specific to Ubuntu 23.04. -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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
[Desktop-packages] [Bug 2015777] Re: Fix build for screen-resolution-extra 0.18.2 on Lunar
Uploaded. Thank you for your contribution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/2015777 Title: Fix build for screen-resolution-extra 0.18.2 on Lunar Status in screen-resolution-extra package in Ubuntu: In Progress Bug description: Build failure: https://launchpad.net/ubuntu/+archive/test- rebuild-20230324-lunar/+build/25796978. The attached patch fixes the build: https://launchpad.net/~nteodosio/+archive/ubuntu/rebuilds/+build/25972961. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/2015777/+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
[Desktop-packages] [Bug 2013236] Re: Failed to install bcmwl wireless driver during the install
1) On the firmware errors: they come from the open b43 driver, since the firmware is not installed. This is something the b43-fwcutter package can help with, if you want to use that. 2) As for the driver installation issue, I wonder if ubuntu-drivers is confused, finding both bcmwl-kernel-source (isn't this a transitional package in Lunar?) and broadcom-sta-source in the image (which, I assume, have overlapping modaliases)? 3) The actual lack of a network device sounds like the driver is not working, in which case, I would like to see the "dmesg" output. -- 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/2013236 Title: Failed to install bcmwl wireless driver during the install Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2013236/+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
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
Note: neither in Jammy nor in Kinetic was the -open driver preferred
over its non-open counterpart, which is one of the things that we want
for this SRU.
--
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/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Bionic:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Jammy:
Fix Committed
Status in ubuntu-drivers-common source package in Kinetic:
Fix Committed
Bug description:
[ Impact ]
* The introduction of the -open NVIDIA drivers requires a change in
the way we detect driver series and flavours. Failing to do so, causes
the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the
-open drivers over the non-open ones (LP: #1988836).
* Furthermore, calling the ubuntu-drivers tool where the alsa-utils
package is not installed (mainly on servers), ubuntu-drivers (through
the sl-modem plugin) complains, unnecessarily about the missing aplay
binary.
[ Test Plan ]
* Install the new ubuntu-drivers-common from -proposed on a system
where the GPU is compatible with the 515 series (or higher).
* Run the ubuntu-drivers list command, and make sure that the 515
driver series (or higher) is listed.
* Try installing the driver using the following command:
sudo ubuntu-drivers install
* Check which driver series was installed (you can use the "sudo
ubuntu-drivers debug" command), and make sure that the installation
does not cause ubuntu-drivers to crash.
[ Where problems could occur ]
* A problem in the ubuntu-drivers tool can cause it to install a driver which
is not recommended for the detected hardware, or even cause the package
installation to fail, and prevent users from logging in through the
graphics interface.
[ Other Info ]
* To prevent failures of the test-suite on architectures such as armhf (as
seen
in Lunar), we are skipping the tests for any architectures other than amd64
and arm64 (which are the only ones actually using ubuntu-drivers).
This was already the case with riscv, and we now have an easier way
to do so in the debian/rules file.
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* New upstream release:
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
- Update regex in nvidia_desktop_pre_installation_hook. This prevents
ubuntu-drivers from crashing when dealing with the -open NVIDIA
drivers (LP: #1993019).
* tests/test_ubuntu_drivers.py:
- Add tests so we make sure to keep preferring non-open NVIDIA
modules over the -open ones, at least until the open modules catch up
feature wise and performance wise.
[ gongzhengyang ]
* UbuntuDrivers/detect.py:
- Fix local variable 'version' being referenced before assignment
when catching ValueError (LP: #1993019).
[ Jeff Lane ]
* detect-plugins/sl-modem.py:
- Add some error trapping when aplay is not installed (on servers).
=== Jammy only (left over from 1:0.9.6.2~0.22.04.1) ===
* UbuntuDrivers/detect.py:
- Make sure -open drivers have a lower priority (LP: #1988836).
== Changelogs ==
=== Kinetic and Jammy ===
[ Alberto Milone ]
* debian/rules:
- Limit the tests to the selected architectures (amd64, arm64).
This prevents armhf builds from failing.
* UbuntuDrivers/detect.py:
- Make sure all -open drivers have a lower priority, regardless
of whether the --server parameter is passed in or not.
- Update regex and unify package name parsing in the following
functions by using the new NvidiaPkgNameInfo class:
nvidia_desktop_pre_installation_hook,
_get_headless_no_dkms_metapackage,
nvidia_desktop_pre_installation_hook,
get_linux_modules_metapackage,
This prevents ubuntu-drivers from crashing when dealing with
the -open NVIDIA drivers (LP: #1993019).
* tests/test_ubuntu_drivers.py:
- Add tests so we make sure to keep preferring non-open NVIDIA
modules over the -open ones, at least until the open modules catch up
feature wise and performance wise.
[ gongzhengyang ]
* UbuntuDrivers/detect.py:
- Fix local variable 'version' being referenced before assignment
when catching ValueError (LP: #1993019).
[ Jeff Lane ]
* detect-plugins/sl-modem.py:
- Add some error trapping when aplay is not installed (on servers).
=== Jammy only (left
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
The installation proceeded as expected in Jammy. :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.3 Candidate: 1:0.9.6.2~0.22.04.3 Version table: *** 1:0.9.6.2~0.22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages You can see the attached output of "ubuntu-drivers debug" ** Attachment added: "jammy" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+attachment/5654197/+files/jammy ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-driv
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
I did the same thing for Jammy, with the same results: :~$ ubuntu-drivers list ERROR:root:aplay command not found nvidia-driver-525-open nvidia-driver-515 nvidia-driver-510 nvidia-driver-470-server nvidia-driver-470 nvidia-driver-525-server nvidia-driver-515-server nvidia-driver-525 nvidia-driver-515-open :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.2~0.22.04.3 Candidate: 1:0.9.6.2~0.22.04.3 Version table: *** 1:0.9.6.2~0.22.04.3 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.6.1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+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
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
Removing the alsa-utils package in Kinetic, I don't get the traceback any more with the package in kinetic-proposed: :~$ ubuntu-drivers list ERROR:root:aplay command not found nvidia-driver-515-open, (kernel modules provided by nvidia-dkms-515-open) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-22.04) nvidia-driver-525-server, (kernel modules provided by linux-modules-nvidia-525-server-generic-hwe-22.04) nvidia-driver-525-open, (kernel modules provided by linux-modules-nvidia-525-open-generic-hwe-22.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-22.04) nvidia-driver-525, (kernel modules provided by linux-modules-nvidia-525-generic-hwe-22.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-22.04) nvidia-driver-515, (kernel modules provided by linux-modules-nvidia-515-generic-hwe-22.04) nvidia-driver-515-server, (kernel modules provided by linux-modules-nvidia-515-server-generic-hwe-22.04) ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+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
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
The installation proceeded as expected in Kinetic. :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.6.3.2 Candidate: 1:0.9.6.3.2 Version table: *** 1:0.9.6.3.2 400 400 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.6.3 500 500 http://it.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages You can see the attached output of "ubuntu-drivers debug" ** Attachment added: "kinetic" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+attachment/5654171/+files/kinetic ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -ope
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
Hey Timo, unfortunately I had left an unused variable in Jammy and in Kinetic, and that caused the test suite to trigger a FTBFS for both. The unused variable is not there in Lunar. Please accept my new uploads, so that we can proceed with the testing. -- 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/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Committed Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed, and make sure that alsa-utils is not installed. * Run the ubuntu-drivers list command. * Check that ubuntu-drivers does not complain about the missing aplay tool. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] - ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect aplay = subprocess.Popen( File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.9.0~0.20.04.1 Candidate: 1:0.9.0~0.20.04.1 Version table: *** 1:0.9.0~0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.5~0.20.04.1 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1:0.8.1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-drivers-common/+bug/1935070/+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
[Desktop-packages] [Bug 1935070] Re: Traceback during 'ubuntu-drivers list'
** Also affects: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Fix Committed => Fix Released ** Description changed: + [ Impact ] + + * Calling the ubuntu-drivers tool where the alsa-utils package is not + installed (mainly on servers), ubuntu-drivers (through the sl-modem + plugin) complains, unnecessarily about the missing aplay binary. + + [ Test Plan ] + + * Install the new ubuntu-drivers-common from -proposed, and make sure + that alsa-utils is not installed. + + * Run the ubuntu-drivers list command. + + * Check that ubuntu-drivers does not complain about the missing aplay + tool. + + [ Where problems could occur ] + + * A problem in the ubuntu-drivers tool can cause it to install a driver which +is not recommended for the detected hardware, or even cause the package +installation to fail, and prevent users from logging in through the +graphics interface. + + [ Other Info ] + - + ___ ubuntu@doubletusk:~$ sudo ubuntu-drivers list ERROR:root:could not open aplay -l Traceback (most recent call last): - File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect - aplay = subprocess.Popen( - File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ - self._execute_child(args, executable, preexec_fn, close_fds, - File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child - raise child_exception_type(errno_num, err_msg, err_filename) + File "/usr/share/ubuntu-drivers-common/detect/sl-modem.py", line 35, in detect + aplay = subprocess.Popen( + File "/usr/lib/python3.8/subprocess.py", line 858, in __init__ + self._execute_child(args, executable, preexec_fn, close_fds, + File "/usr/lib/python3.8/subprocess.py", line 1704, in _execute_child + raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'aplay' nvidia-driver-418-server, (kernel modules provided by nvidia-dkms-418-server) nvidia-driver-470, (kernel modules provided by nvidia-dkms-470) nvidia-driver-460-server, (kernel modules provided by nvidia-dkms-460-server) nvidia-driver-465, (kernel modules provided by nvidia-dkms-465) nvidia-driver-450-server, (kernel modules provided by nvidia-dkms-450-server) nvidia-driver-460, (kernel modules provided by nvidia-dkms-460) ubuntu@doubletusk:~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: - Installed: 1:0.9.0~0.20.04.1 - Candidate: 1:0.9.0~0.20.04.1 - Version table: - *** 1:0.9.0~0.20.04.1 500 - 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages - 100 /var/lib/dpkg/status - 1:0.8.6.5~0.20.04.1 500 - 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - 1:0.8.1 500 - 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages + Installed: 1:0.9.0~0.20.04.1 + Candidate: 1:0.9.0~0.20.04.1 + Version table: + *** 1:0.9.0~0.20.04.1 500 + 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages + 100 /var/lib/dpkg/status + 1:0.8.6.5~0.20.04.1 500 + 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + 1:0.8.1 500 + 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages ubuntu@doubletusk:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal -- 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/1935070 Title: Traceback during 'ubuntu-drivers list' Status in Ubuntu Drivers Common: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: In Progress Bug description: [ Impact ] * Calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: In Progress => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: In Progress => Triaged -- 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/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: In Progress Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not insta
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Description changed: + [ Impact ] + + * The introduction of the -open NVIDIA drivers requires a change in the + way we detect driver series and flavours. Failing to do so, causes the + ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open + drivers over the non-open ones (LP: #1988836). + + * Furthermore, calling the ubuntu-drivers tool where the alsa-utils + package is not installed (mainly on servers), ubuntu-drivers (through + the sl-modem plugin) complains, unnecessarily about the missing aplay + binary. + + [ Test Plan ] + + * Install the new ubuntu-drivers-common from -proposed on a system + where the GPU is compatible with the 515 series (or higher). + + * Run the ubuntu-drivers list command, and make sure that the 515 + driver series (or higher) is listed. + + * Try installing the driver using the following command: +sudo ubuntu-drivers install + + * Check which driver series was installed (you can use the "sudo + ubuntu-drivers debug" command), and make sure that the installation does + not cause ubuntu-drivers to crash. + + [ Where problems could occur ] + + * A problem in the ubuntu-drivers tool can cause it to install a driver which +is not recommended for the detected hardware, or even cause the package +installation to fail, and prevent users from logging in through the +graphics interface. + + + [ Other Info ] + + * To prevent failures of the test-suite on architectures such as armhf (as seen +in Lunar), we are skipping the tests for any architectures other than amd64 +and arm64 (which are the only ones actually using ubuntu-drivers). +This was already the case with riscv, and we now have an easier way +to do so in the debian/rules file. + + + == Changelogs == + + === Kinetic and Jammy === + + [ Alberto Milone ] + * New upstream release: + * UbuntuDrivers/detect.py: + - Make sure all -open drivers have a lower priority, regardless + of whether the --server parameter is passed in or not. + - Update regex in nvidia_desktop_pre_installation_hook. This prevents + ubuntu-drivers from crashing when dealing with the -open NVIDIA + drivers (LP: #1993019). + * tests/test_ubuntu_drivers.py: + - Add tests so we make sure to keep preferring non-open NVIDIA + modules over the -open ones, at least until the open modules catch up + feature wise and performance wise. + + [ gongzhengyang ] + * UbuntuDrivers/detect.py: + - Fix local variable 'version' being referenced before assignment + when catching ValueError (LP: #1993019). + + [ Jeff Lane ] + * detect-plugins/sl-modem.py: + - Add some error trapping when aplay is not installed (on servers). + + === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === + +* UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). + + == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === -* UbuntuDrivers/detect.py: - - Make sure -open drivers have a lower priority (LP: #1988836). + * UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). Hello, we received a drive-by complaint about the ubuntu-drivers autoinstall tool: < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command < Fhazal> this error appear when i try to auto install recommended driver < Fhazal> https://pastebin.com/ydZVFT24 The contents of the pastebin: Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 513, in greet() File
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Description changed: - Hello, we received a drive-by complaint about the ubuntu-drivers - autoinstall tool: + == Changelogs == + + === Kinetic and Jammy === + + [ Alberto Milone ] + * debian/rules: + - Limit the tests to the selected architectures (amd64, arm64). + This prevents armhf builds from failing. + * UbuntuDrivers/detect.py: + - Make sure all -open drivers have a lower priority, regardless + of whether the --server parameter is passed in or not. + - Update regex and unify package name parsing in the following + functions by using the new NvidiaPkgNameInfo class: + nvidia_desktop_pre_installation_hook, + _get_headless_no_dkms_metapackage, + nvidia_desktop_pre_installation_hook, + get_linux_modules_metapackage, + This prevents ubuntu-drivers from crashing when dealing with + the -open NVIDIA drivers (LP: #1993019). + * tests/test_ubuntu_drivers.py: + - Add tests so we make sure to keep preferring non-open NVIDIA + modules over the -open ones, at least until the open modules catch up + feature wise and performance wise. + + [ gongzhengyang ] + * UbuntuDrivers/detect.py: + - Fix local variable 'version' being referenced before assignment + when catching ValueError (LP: #1993019). + + [ Jeff Lane ] + * detect-plugins/sl-modem.py: + - Add some error trapping when aplay is not installed (on servers). + + + Hello, we received a drive-by complaint about the ubuntu-drivers autoinstall tool: < Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command < Fhazal> this error appear when i try to auto install recommended driver < Fhazal> https://pastebin.com/ydZVFT24 The contents of the pastebin: Traceback (most recent call last): - File "/usr/bin/ubuntu-drivers", line 513, in - greet() - File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__ - return self.main(*args, **kwargs) - File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main - rv = self.invoke(ctx) - File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke - return _process_result(sub_ctx.command.invoke(sub_ctx)) - File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke - return ctx.invoke(self.callback, **ctx.params) - File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke - return __callback(*args, **kwargs) - File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in new_func - return ctx.invoke(f, obj, *args, **kwargs) - File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke - return __callback(*args, **kwargs) - File "/usr/bin/ubuntu-drivers", line 432, in autoinstall - command_install(config) - File "/usr/bin/ubuntu-drivers", line 187, in command_install - UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install) - File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in nvidia_desktop_pre_installation_hook - with_nvidia_kms = version >= 470 + File "/usr/bin/ubuntu-drivers", line 513, in + greet() + File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__ + return self.main(*args, **kwargs) + File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main + rv = self.invoke(ctx) + File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke + return _process_result(sub_ctx.command.invoke(sub_ctx)) + File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke + return ctx.invoke(self.callback, **ctx.params) + File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke + return __callback(*args, **kwargs) + File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in new_func + return ctx.invoke(f, obj, *args, **kwargs) + File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke + return __callback(*args, **kwargs) + File "/usr/bin/ubuntu-drivers", line 432, in autoinstall + command_install(config) + File "/usr/bin/ubuntu-drivers", line 187, in command_install + UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install) + File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in nvidia_desktop_pre_installation_hook + with_nvidia_kms = version >= 470 UnboundLocalError: local variable 'version' referenced before assignment - Skimming the version on my system it sure feels plausible: def nvidia_desktop_pre_installation_hook(to_install): - '''Applies changes that need to happen before installing the NVIDIA drivers''' - with_nvid
[Desktop-packages] [Bug 2007563] Re: Update ubuntu-drivers-common 02/2023
** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => Won't Fix ** Description changed: - Kinetic + + == Changelogs == + + === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. - * tests/quirkreader-test.py: - - Fix E275 missing whitespace after keyword. - * Quirks/quirkreader.py: - - Handle UnicodeDecodeError. - - Line 55 fix E275 missing whitespace after keyword. - - [ Alex-S-H-P ] - * UbuntuDrivers/detect.py: - - Remove redundant variable. - - [ Jeremy Szu ] - * README, README.md, - UbuntuDrivers/detect.py, - tests/test_ubuntu_drivers.py: - - Add support for force installing the NVIDIA driver on unsupported - devices. - The device and its target driver branch are both specified in the - /etc/custom_supported_gpus.json file. - Support for runtimepm can also be set in the file. - - Support autokgstest for force install nvidia. - - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment - when catching ValueError. + when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). + + === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === + +* UbuntuDrivers/detect.py: + - Make sure -open drivers have a lower priority (LP: #1988836). -- 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/2007563 Title: Update ubuntu-drivers-common 02/2023 Status in ubuntu-drivers-common package in Ubuntu: Won't Fix Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Kinetic: In Progress Bug description: == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2007563/+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
[Desktop-packages] [Bug 2007563] [NEW] Update ubuntu-drivers-common 02/2023
Public bug reported: Kinetic [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. * tests/quirkreader-test.py: - Fix E275 missing whitespace after keyword. * Quirks/quirkreader.py: - Handle UnicodeDecodeError. - Line 55 fix E275 missing whitespace after keyword. [ Alex-S-H-P ] * UbuntuDrivers/detect.py: - Remove redundant variable. [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Add support for force installing the NVIDIA driver on unsupported devices. The device and its target driver branch are both specified in the /etc/custom_supported_gpus.json file. Support for runtimepm can also be set in the file. - Support autokgstest for force install nvidia. - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError. [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: Triaged -- 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/2007563 Title: Update ubuntu-drivers-common 02/2023 Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Kinetic [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. * tests/quirkreader-test.py: - Fix E275 missing whitespace after keyword. * Quirks/quirkreader.py: - Handle UnicodeDecodeError. - Line 55 fix E275 missing whitespace after keyword. [ Alex-S-H-P ] * UbuntuDrivers/detect.py: - Remove redundant variable. [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Add support for force installing the NVIDIA driver on unsupported devices. The device and its target driver branch are both specified in the /etc/custom_supported_gpus.json file. Support for runtimepm can also be set in the file. - Support autokgstest for force install nvidia. - Add autopkgtest in README section. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError. [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2007563/+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
[Desktop-packages] [Bug 1990341] Re: [FeatureFreeze Exceptions] Support to install nvidia driver by allowing list
@Brian, no, there was a misunderstanding, and this was not meant for
Lunar. Please unsubscribe the Release team, as I can't seem to be able
to do it.
--
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/1990341
Title:
[FeatureFreeze Exceptions] Support to install nvidia driver by
allowing list
Status in OEM Priority Project:
Incomplete
Status in ubuntu-drivers-common package in Ubuntu:
Incomplete
Bug description:
> If the upload is a new upstream microrelease, the relevant part of
the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-
common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new
version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom
file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and
_is_runtimepm_supported(). Both functions are important when "ubuntu-
driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which
contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest
test_system_driver_packages_force_install_nvidia() which not only secure this
FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in
the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of
ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as
"test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for
more details.
> state the reason why you feel it is necessary (other bugs it fixes,
etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for
production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a
specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u -{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the
tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your
request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows
"DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when
enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it
shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
Done
---
[Additional
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
I think we can safely remove this from -proposed, as I am going to upload a new release, including this one and more fixes. -- 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/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Also affects: ubuntu-drivers-common (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Kinetic)
Importance: Undecided => High
--
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/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Bionic:
In Progress
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in ubuntu-drivers-common source package in Jammy:
In Progress
Status in ubuntu-drivers-common source package in Kinetic:
In Progress
Bug description:
Hello, we received a drive-by complaint about the ubuntu-drivers
autoinstall tool:
< Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
< Fhazal> this error appear when i try to auto install recommended driver
< Fhazal> https://pastebin.com/ydZVFT24
The contents of the pastebin:
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
Skimming the version on my system it sure feels plausible:
def nvidia_desktop_pre_installation_hook(to_install):
'''Applies changes that need to happen before installing the NVIDIA
drivers'''
with_nvidia_kms = False
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
if with_nvidia_kms:
set_nvidia_kms(1)
If there was an exception splitting, indexing, or converting to an
int, that 'version' variable may not have a value.
Thanks
To manage no
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
--
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/1993019
Title:
UnboundLocalError: local variable 'version' referenced before
assignment
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
Hello, we received a drive-by complaint about the ubuntu-drivers
autoinstall tool:
< Fhazal> hye i have problem with ubuntu 22.04 nvidia auto install command
< Fhazal> this error appear when i try to auto install recommended driver
< Fhazal> https://pastebin.com/ydZVFT24
The contents of the pastebin:
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 432, in autoinstall
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
Skimming the version on my system it sure feels plausible:
def nvidia_desktop_pre_installation_hook(to_install):
'''Applies changes that need to happen before installing the NVIDIA
drivers'''
with_nvidia_kms = False
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
if with_nvidia_kms:
set_nvidia_kms(1)
If there was an exception splitting, indexing, or converting to an
int, that 'version' variable may not have a value.
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1993019/+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
[Desktop-packages] [Bug 1995618] Re: It seems to not login automatically or get X session after installing Nvidia-driver
The problem here is that ubuntu-drivers-common in Focal is too old, and does not include code to handle the -open driver series. This needs an SRU. ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-signed-hwe-5.15 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-520 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-signed-hwe-5.15 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-520 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-signed-hwe-5.15 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-520 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/1995618 Title: It seems to not login automatically or get X session after installing Nvidia-driver Status in linux-signed-hwe-5.15 package in Ubuntu: New Status in nvidia-graphics-drivers-520 package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: New Status in linux-signed-hwe-5.15 source package in Bionic: New Status in nvidia-graphics-drivers-520 source package in Bionic: New Status in ubuntu-drivers-common source package in Bionic: New Status in linux-signed-hwe-5.15 source package in Focal: New Status in nvidia-graphics-drivers-520 source package in Focal: New Status in ubuntu-drivers-common source package in Focal: New Status in linux-signed-hwe-5.15 source package in Jammy: New Status in nvidia-graphics-drivers-520 source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: New Bug description: During SRU testing, I found some machines kept failing to run switching graphic card test. According to the output from the test run, those machines seem to not login automatically or can't get X session somehow. Now I can't check the status of machines directly, but my guessing is base on the output from our test case, it showed "Can't open display :0" and "Gtk couldn't be initialized. Use Gtk.init_check() ". I met this issue on there different machine which I can get log from them so far, there are other machines have this issue but I can't get the log. Our testing always use ubuntu-driver install to install nvidia-driver. https://certification.canonical.com/hardware/202004-27810/ https://certification.canonical.com/hardware/202004-27811/ https://certification.canonical.com/hardware/201904-26941/ Kernel version:5.15.0-53-generic Nvidia driver: nvidia-driver-520-open ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-53-generic 5.15.0-53.59~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-53.59~20.04.1-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Nov 3 10:55:26 2022 InstallationDate: Installed on 2020-08-03 (821 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/1995618/+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
[Desktop-packages] [Bug 1965094] Re: "Additional Drivers" application crashes on startup
It seems like the apt_pkg.Cache is not fully initialised in SoftwarePropertiesGtk.py when this happens (no "packages" attribute can be found). ** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: New => Confirmed ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1965094 Title: "Additional Drivers" application crashes on startup Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Steps to reproduce: * Click on "Show applications" in the dock * Click on "Additional Drivers" Expected: It is possible to see and install additional drivers Actual: Application "software-properties-gtk" crashes Background: I installed 22.04 daily build from scratch on my new Samsung laptop just a few days ago and I have almost no custom settings. Output from screenfetch: ./+o+- [...] y- -yy+ OS: Ubuntu 22.04 jammy ://+//-yyo Kernel: x86_64 Linux 5.15.0-22-generic .++ .:/++/-.+sss/` Uptime: 1d 9h 37m .:++o: //:--:/- Packages: 1810 o:+o+:++.`..```.-/oo+/ Shell: bash 5.1.16 .:+o:+o/. `+sssoo+/Resolution: 3840x1080 .++/+:+oo+o:` /sssooo. DE: GNOME 41.4 /+++//+:`oo+o /::--:. WM: Mutter \+/+o+++`o++o ++. WM Theme: Adwaita .++.o+++oo+:` /dddhhh. GTK Theme: Yaru-dark [GTK2/3] .+.o+oo:. `odd+Icon Theme: Yaru \+.++o+o``-.:ohdh+ Font: Ubuntu 11 `:o+++ `oyo++os: Disk: 21G / 1,2T (2%) .o:`.syhhh/.oo++o` CPU: 11th Gen Intel Core i7-1165G7 @ 8x 4,7GHz [40.0°C] /osyyo++ooo+++/ GPU: Iris Xe Graphics ` +oo+++o\: RAM: 2627MiB / 15725MiB `oo++. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 16 08:34:57 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-03-14 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4 Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4'] PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965094/+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
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
Hi Chris, since we are dealing with LP: #1990835 now (for this kernel SRU cycle), perhaps we can put the two bug reports together. I will have to upload to the Canonical Kernel Team PPA first, though, because of the way we build the linux-restricted-modules. -- 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/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
Hi Chris, I had missed one commit, which caused a FTBFS. I have uploaded a new revision (515.65.01-0ubuntu0.20.04.3) for Focal. The fix is also in Jammy (515.65.01-0ubuntu0.22.04.3). I would be grateful if you could approve both. Thanks. -- 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/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
** Description changed: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] - * detailed instructions how to reproduce the bug + * [ubuntu-drivers-common]: +"sudo ubuntu-drivers install (to make sure the driver is not installed by default)" - * these should allow someone who is not familiar with the affected -package to reproduce the bug and verify that the updated package fixes -the problem. + * [nvidia driver] - * if other testing is appropriate to perform before landing this update, -this should also be described here. +"sudo ubuntu-drivers install nvidia:515-open" to make sure that the + driver can be installed manually. + +Please make sure that this installs the correct linux-restricted- + modules. + +Note: support for GeForce and Workstation GPUs is alpha-quality, and + is disabled by default. This means that desktop testing is not needed at + the moment. [ Where problems could occur ] - * Think about what the upload changes in the software. Imagine the change is -wrong or breaks something else: how would this show up? - - * It is assumed that any SRU candidate patch is well-tested before -upload and has a low overall risk of regression, but it's important -to make the effort to think about what ''could'' happen in the -event of a regression. - - * This must '''never''' be "None" or "Low", or entirely an argument as to why -your upload is low risk. - - * This both shows the SRU team that the risks have been considered, -and provides guidance to testers in regression-testing the SRU. + * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). + * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + - -- 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/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
** Description changed: - The 515 series introduced open kernel modules for the NVIDIA driver. - They come with an open source licence, and should be provided as an - option for datacenter GPUs: + [ Impact ] - https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- - kernel-modules/ + * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: + https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ + +Currently, this is only production-ready (and enabled) on datacenter + GPUs. + + * We should enable signed modules for the 515-open drivers, giving + users the option to try the drivers. + + * The ubuntu-drivers tool should set a lower priority for the -open + flavour, so that we do not end up recommending it over the plain 515 + flavour. + + [ Test Plan ] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + * if other testing is appropriate to perform before landing this update, +this should also be described here. + + [ Where problems could occur ] + + * Think about what the upload changes in the software. Imagine the change is +wrong or breaks something else: how would this show up? + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This must '''never''' be "None" or "Low", or entirely an argument as to why +your upload is low risk. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [ Other Info ] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance -- 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/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. * if other testing is appropriate to perform before landing this update, this should also be described here. [ Where problems could occur ] * Think about what the upload changes in the software. Imagine the change is wrong or breaks something else: how would this show up? * It is assumed that any SRU candidate patch is well-tested before upload and has a low overall risk of regression, but it's important to make the effort to think about what ''could'' happen in the event of a regression. * This must '''never''' be "None" or "Low", or entirely an argument as to why your upload is low risk. * This both shows the SRU team that the risks have been considered, and provides guidance to testers in regression-testing the SRU. [ Other Info ] * Anything else you think is useful to include * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board * and address these questions in advance To manage notifications about this bug go to:
[Desktop-packages] [Bug 1988836] Re: Enable the open NVIDIA kernel modules
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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
[Desktop-packages] [Bug 1988143] Re: 20.04.5 (20220829.1 build) has kernel 5.13 packages
** Description changed: + [Impact] + + * Linux-restricted-modules for the 390 drivers were disabled + temporarily back in January, however they were not re-enabled when + support for the new kernel was added. + + * Including the 390 release in the ISO causes the 5.13 packages to be + pulled in. + + [Test Plan] + + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + can be installed with its linux-restricted-modules. + + [Where problems could occur] + + * The addition of modules for an already existing driver series would not +cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + _ + Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated. ** Description changed: [Impact] - * Linux-restricted-modules for the 390 drivers were disabled + * Linux-restricted-modules for the 390 drivers were disabled temporarily back in January, however they were not re-enabled when support for the new kernel was added. - * Including the 390 release in the ISO causes the 5.13 packages to be + * Including the 390 release in the ISO causes the 5.13 packages to be pulled in. [Test Plan] - * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver + * Install the hwe-515 kernel and make sure that the NVIDIA 390 driver can be installed with its linux-restricted-modules. [Where problems could occur] - * The addition of modules for an already existing driver series would not -cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: + * The addition of modules for an already existing driver series would not + cause any regressions, since the whole package generation process is automated, and this is the only commit that we are going to revert: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-restricted-modules/+git/focal/commit/?h=hwe-5.15=0dfff8472e3e4e75e8effc5957ba6b89a9eaf020 [Other Info] - - * Anything else you think is useful to include - * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board - * and address these questions in advance + + * Other kernel releases support the 390 series. _ Examining the .list file for the amd64 image it contains various kernel 5.13 .deb packages. http://cdimage.ubuntu.com/focal/daily-live/20220829.1/focal-desktop- amd64.list e.g. /pool/main/l/linux-hwe-5.13/linux-modules-5.13.0-52-generic_5.13.0-52.59~20.04.1_amd64.deb /pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-common-515_515.65.01-0ubuntu0.20.04.1_all.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-objects-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-generic-hwe-20.04_5.13.0-52.59~20.04.1+1_amd64.deb /pool/restricted/l/linux-restricted-modules-hwe-5.13/linux-modules-nvidia-390-5.13.0-52-generic_5.13.0-52.59~20.04.1+1_amd64.deb This is a little unexpected given that 5.15 is the default kernel. Possibly nvidia-390 doesn't have 5.15 packages? This impacts all flavours as well that include nvidia stuff in their ISO - so if the solution is to change the meta file for a revised regexp for nvidia then all flavours that include nvidia will likewise need their meta packages updated.
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
@Brian: I have just re-uploaded the sources. Thanks. -- 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: [Impact] * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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
[Desktop-packages] [Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** No longer affects: ubuntu-drivers-common (Ubuntu) ** No longer affects: ubuntu-drivers-common (Ubuntu Jammy) -- 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/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in OEM Priority Project: New Status in update-notifier package in Ubuntu: Confirmed Status in update-notifier source package in Jammy: Confirmed Bug description: This bug occurred after install of Ubuntu Mate Jammy daily ISO 15-03-2022 Test machine Dell Optiplex 7060 in UEFI+secure boot mode. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.51 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Mar 15 10:21:14 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2022-03-15 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+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
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
I have re-uploaded, removing the bootvga fix, and including the bug report for the BrokenPipeError (LP: #1965520). Hopefully this is good to go now. ** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. - --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Don't check the current profile when setting + a profile (LP: #1946476). + - Handle BrokenPipeError (LP: #1965520). -- 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/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094.
[Desktop-packages] [Bug 1965520] Re: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-select@374:enable_profile:_disable_nvidia:_update_initramfs
** Description changed: + [Impact] + + * The progress bar that is drawn to keep track of the update-initramfs + process can result, sometimes, in a BrokenPipe error. In no way does + this affect the final result of the actual operation, yet it causes the + progress bar to crash. + + [Test Plan] + + * Install the nvidia-prime package and , and then execute "sudo prime- + select intel" so that NVIDIA can be disabled, and the update-initramfs + command is called. This might need repeating (i.e. going back and forth + from "sudo prime-select intel" to "sudo prime-select on-demand" until + the BrokenPipe error shows up. + + [Where problems could occur] + + * This can cause no regression, since it does not alter the actual + functioning on nvidia-prime, and the change has been in Impish since its + release. + + [Other Info] __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Tags removed: impish -- 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/1965520 Title: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime- select@374:enable_profile:_disable_nvidia:_update_initramfs Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-prime source package in Bionic: Triaged Status in nvidia-prime source package in Focal: In Progress Bug description: [Impact] * The progress bar that is drawn to keep track of the update- initramfs process can result, sometimes, in a BrokenPipe error. In no way does this affect the final result of the actual operation, yet it causes the progress bar to crash. [Test Plan] * Install the nvidia-prime package and , and then execute "sudo prime-select intel" so that NVIDIA can be disabled, and the update- initramfs command is called. This might need repeating (i.e. going back and forth from "sudo prime-select intel" to "sudo prime-select on-demand" until the BrokenPipe error shows up. [Where problems could occur] * This can cause no regression, since it does not alter the actual functioning on nvidia-prime, and the change has been in Impish since its release. [Other Info] __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1965520/+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
[Desktop-packages] [Bug 1965520] Re: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-select@374:enable_profile:_disable_nvidia:_update_initramfs
** Description changed: + + __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- 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/1965520 Title: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime- select@374:enable_profile:_disable_nvidia:_update_initramfs Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-prime source package in Bionic: Triaged Status in nvidia-prime source package in Focal: In Progress Bug description: __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1965520/+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
[Desktop-packages] [Bug 1965520] Re: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-select@374:enable_profile:_disable_nvidia:_update_initramfs
** Tags removed: groovy hirsute ** Changed in: nvidia-prime (Ubuntu) Status: New => Triaged ** Changed in: nvidia-prime (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: nvidia-prime (Ubuntu Impish) ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-prime (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu Bionic) Status: New => Triaged ** Changed in: nvidia-prime (Ubuntu Bionic) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1965520 Title: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime- select@374:enable_profile:_disable_nvidia:_update_initramfs Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-prime source package in Bionic: Triaged Status in nvidia-prime source package in Focal: In Progress Bug description: __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1965520/+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
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
I have just uploaded ubuntu-drivers-common_0.9.0~0.20.04.7 and ubuntu- drivers-common_0.9.2.4~0.21.10.2. Note: this will have to be verified together with LP: #1958488, if we want both fixes released at the same time. ** Description changed: [Impact] - * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). - * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. - * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. + * In Ubuntu 22.04, ubuntu-drivers install will install nvidia-470 instead of 510. (the ubuntu-drivers install is the best and recommended way to install nvidia driver). + * nvidia-470 is LTSB (although webpage shows PB) and nvidia-510 is PB, in this case, we need to chose the newer version since the support is fair in both version. + * Also, 22.04 announces Wayland supports but nvidia-470 doesn't support in Wayland scope at least from gdm upstream. [Test Plan] - * ubuntu-drivers debug + * Call "ubuntu-drivers debug" and check that 510 is marked as "(auto-install)" ``` ... === matching driver packages === - nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] + nvidia-driver-510: installed:available: 510.54-0ubuntu2 [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] ... - nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB + nvidia-driver-470: installed:available: 470.103.01-0ubuntu2 (auto-install) [distro] non-free modalias: pci:v10DEd25A0sv1028sd0A61bc03sc02i00 path: /sys/devices/pci:00/:00:01.0/:01:00.0 vendor: NVIDIA Corporation model: GA107M [GeForce RTX 3050 Ti Mobile] support level: LTSB ... ``` - * As you can see, "(auto-install)" is point to 470 because of it owns LTSB tag. + * As you can see, "(auto-install)" points to 470 because it owns LTSB tag. [Fix] - * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. + * Adjust the priority in UbuntuDrivers/detect.py, if the PB and LTSB versions found, then it needs to pick the newer version one. [Where problems could occur] - * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. - * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. + * It has less possible to introduce regression since the patch only changes _cmp_gfx_alternatives() which counts the priority of nvidia drivers be installed. + * In Ubuntu, we have nvidia-390, 470 and 510 so far as I known and these cases are listed in test_system_driver_packages_chroot_support_branch_pb. --- + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 -- 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: New => In Progress -- 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Impish: In Progress Bug description: + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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
[Desktop-packages] [Bug 1964747] Re: [Jammy][regression] u-d-c default to use 470 instead of 510
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Critical ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) -- 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/1964747 Title: [Jammy][regression] u-d-c default to use 470 instead of 510 Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: + nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) + + * New upstream release (LP: #1961075): + - Fixed a bug that could cause GPU exceptions when minimizing a + fullscreen Vulkan application on certain desktops, such as + Plasma. + * debian/templates/control.in: + - Set XB-Support to PB (production branch). + * debian/rules.defs: + - Add support for video ABI 25. --- Since * debian/templates/control.in: - Set XB-Support to PB (production branch). The u-d-c will choose LTS branch instead of PB branch. because `def _cmp_gfx_alternatives(x, y):` doesn't define PB. [Additional information] If installed 470 instead of 510, then it will cause https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1963701 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964747/+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
[Desktop-packages] [Bug 1964880] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
I have created a merge proposal for this. -- 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/1964880 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: Opened up "Software & Updates" and clicked the "Additional Drivers Tab", for the tab to crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 19:02:39 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-01-02 (72 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964880/+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
[Desktop-packages] [Bug 1964880] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress -- 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/1964880 Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: Opened up "Software & Updates" and clicked the "Additional Drivers Tab", for the tab to crash. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: software-properties-gtk 0.99.19 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 19:02:39 2022 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2022-01-02 (72 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 3.10.1-0ubuntu2 PythonArgs: ['/usr/bin/software-properties-gtk'] PythonDetails: N/A SourcePackage: software-properties Title: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1964880/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Ok, I have just uploaded the new u-d-c. Thanks -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Here is the output of ubuntu-drivers install, however I was not able measure the time here. The packages were installed correctly. ** Attachment added: "install" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+attachment/5567936/+files/install -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Output of ubuntu-drivers debug ** Attachment added: "debug" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+attachment/5567935/+files/debug -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Here is the output and the time it takes to run ubuntu-drivers list and ubuntu-drivers list --gpgpu ** Attachment added: "ubuntu-drivers-list.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+attachment/5567928/+files/ubuntu-drivers-list.log -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
I have addressed all the concerns in the PR, and I have uploaded the changes to the PPA. -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
I have also added a PPA in the description. ** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 + + [PPA] + https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 [PPA] https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-lp1963712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
Hi Łukasz, I have just attached the sbuild log. I can certainly upload to a PPA, so that, perhaps, testing the changes will be easier. As I wrote in the description, I saw the time for a simple "ubuntu- drivers list" go down from 13,751s to 2,673s, which is quite impressive. -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Attachment added: "Sbuild log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+attachment/5566587/+files/ubuntu-drivers-common_0.9.6_amd64-2022-03-07T16%3A44%3A03Z.build ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Incomplete => Confirmed -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. - This significantly improves performance. + This significantly improves performance (2,673s vs 13,751s , on my dated + Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s - :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s - New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s - :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s - [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance (2,673s vs 13,751s , on my dated Intel Ivy Bridge i7-3770K CPU). [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok + Old detection code: + + :~$ time ubuntu-drivers list + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + + real 0m13,751s + user 0m13,480s + sys 0m0,258s + + + :~$ time ubuntu-drivers list + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + + real 0m13,785s + user 0m13,578s + sys 0m0,196s + + + New detection code: + + :~$ time ubuntu-drivers list + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + + real 0m2,673s + user 0m1,749s + sys 0m0,914s + + + :~$ time ubuntu-drivers list + nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) + nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) + nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) + + real 0m2,645s + user 0m1,702s + sys 0m0,935s + + [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok Old detection code: :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) real 0m13,751s user 0m13,480s sys 0m0,258s :~$ time ubuntu-drivers list nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m13,785s user 0m13,578s sys 0m0,196s New detection code: :~$ time ubuntu-drivers list nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) real 0m2,673s user 0m1,749s sys 0m0,914s :~$ time ubuntu-drivers list nvidia-driver-470-server, (kernel modules provided by linux-modules-nvidia-470-server-generic-hwe-20.04) nvidia-driver-510, (kernel modules provided by linux-modules-nvidia-510-generic-hwe-20.04) nvidia-driver-470, (kernel modules provided by linux-modules-nvidia-470-generic-hwe-20.04) real 0m2,645s user 0m1,702s sys 0m0,935s [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] Re: FFE: Switch from apt to apt_pkg bindings
** Description changed: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] + system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok + system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok + + [PR] + https://github.com/tseliot/ubuntu-drivers-common/pull/68 -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] system_driver_packages() performance for a lot of modaliases ... [0.94 s] ok system_driver_packages() performance for a lot of modaliases ... [0.96 s] ok [PR] https://github.com/tseliot/ubuntu-drivers-common/pull/68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1963712] [NEW] FFE: Switch from apt to apt_pkg bindings
Public bug reported: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: Confirmed ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Medium -- 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/1963712 Title: FFE: Switch from apt to apt_pkg bindings Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Switch from the apt bindings to the apt_pkg bindings for the ubuntu- drivers tool. This significantly improves performance. [Attach sbuild log] [Performance data] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1963712/+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
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
@Chris: ok, we'll sort this out, and let you know, thanks. -- 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/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+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
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Also affects: gdm3 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus,
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Invalid -- 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/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Invalid Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
I have also fixed the part of the test-plan that Chris mentioned. -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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 * 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
I suppose I could simply detect the version in nvidia-settings. I already have code that does that in a different patch that I wrote for nvidia-settings. ** Description changed: [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 - * + * 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. -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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 * 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Description changed: [Impact] - * In any Ubuntu series, if user using a old GPU (which supported by + * 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-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. + * 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. -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
@Robie I am not sure what rejecting the uploads actually accomplished (other than forcing me to re-upload the exact same sources) for something that can be amended in the bug description on Launchpad. This said, I did not notice that the section was missing. While mistakes can happen, please restrain from implying that I "just sponsor and leave". Thank you. -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Impish: New Status in ubuntu-drivers-common source package in Impish: Triaged Status in nvidia-settings source package in Jammy: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** No longer affects: ubuntu-drivers-common (Ubuntu Focal) ** Changed in: ubuntu-drivers-common (Ubuntu Impish) Status: New => Triaged -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Impish: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
This should be fixed in Jammy now: ubuntu-drivers-common (1:0.9.4) jammy; urgency=medium [ Michael Hudson-Doyle ] * UbuntuDrivers/detect.py: - Optimize packages_for_modalias by compiling all the Modaliases into one big regexp that can be used to quickly reject most devices. [ Alberto Milone ] * UbuntuDrivers/kerneldetection.py: - Improve performance of _get_linux_metapackage. * gpu-manager.c: - Fall back from on-demand to on if nvidia < 450. [ Jeremy Szu ] * ubiquity/target-config/31ubuntu_driver_packages: - Install nvidia-prime in eariler stage. ** Also affects: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided Assignee: jeremyszu (os369510) Status: In Progress ** Also affects: ubuntu-drivers-common (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Impish: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug 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. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
Status: In Progress => Won't Fix
** No longer affects: ubuntu-drivers-common (Ubuntu)
** No longer affects: ubuntu-drivers-common (Ubuntu Focal)
** No longer affects: ubuntu-drivers-common (Ubuntu Hirsute)
--
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/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Triaged
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in nvidia-prime source package in Focal:
Incomplete
Status in nvidia-prime source package in Hirsute:
New
Bug description:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
performance
---
It's because ubiquity launches `ubuntu-drivers install --packages-list
...` in live system but install each package to target storage.
When installing nvidia-prime, the preinst set "on" to "/etc/prime-
discrete" which will be referred by gpu-manager. The gpu-manager will
set to performance mode.
After confirming with Alberto on Mattermost, since we don't have a
nvidia driver which lower than 450 version since focal.
I think we are ok to switch to on-demand mode.
---
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
* Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
* On non-laptop machine. Can set GPU mode to on-demand
* On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
* on-demand mode combined two features which are GPU offloading and RTD3.
Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and
only have GPU offloading feature.
* With GPU supported RTD3 not able enable runtime PM on non-laptop. But
based on the Nvidia README, this case shall not happened.
[Other Info]
X-HWE-Bug: Bug #1946434
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
- Catch BrokenPipeError.
- Use bootvga detection when last_gfx_boot is
not available.
nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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
[Desktop-packages] [Bug 1952147] Re: no way to list drivers "ubuntu-drivers list --gpgpu" will install
** Changed in: ubuntu-drivers-common (Ubuntu) Status: Triaged => In Progress -- 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/1952147 Title: no way to list drivers "ubuntu-drivers list --gpgpu" will install Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: I'm pretty sure that "ubuntu-drivers install --gpgpu" will install something if and only if "ubuntu-drivers list --gpgpu" has non-empty output, but the logic of which of the things list returns gets installed seems a bit non-trivial The context for this is in the server installer, I want to say "we think you should install nvidia-headless-no-dkms-470-server and linux- modules-nvidia-470-server-generic", shall we go ahead and install them? My current spike just says "there are some drivers you might want to install, shall we install them?" which just seems a bit opaque Alberto suggested a flag so that I could run "ubuntu-drivers list --gpgpu --recommended" in the installer. I should just make very clear that I'd want "ubuntu-drivers list --recommended" (i.e. without --gpgpu) to work the same way :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1952147/+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
[Desktop-packages] [Bug 1952147] Re: no way to list drivers "ubuntu-drivers list --gpgpu" will install
** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Medium -- 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/1952147 Title: no way to list drivers "ubuntu-drivers list --gpgpu" will install Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: I'm pretty sure that "ubuntu-drivers install --gpgpu" will install something if and only if "ubuntu-drivers list --gpgpu" has non-empty output, but the logic of which of the things list returns gets installed seems a bit non-trivial The context for this is in the server installer, I want to say "we think you should install nvidia-headless-no-dkms-470-server and linux- modules-nvidia-470-server-generic", shall we go ahead and install them? My current spike just says "there are some drivers you might want to install, shall we install them?" which just seems a bit opaque Alberto suggested a flag so that I could run "ubuntu-drivers list --gpgpu --recommended" in the installer. I should just make very clear that I'd want "ubuntu-drivers list --recommended" (i.e. without --gpgpu) to work the same way :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1952147/+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
[Desktop-packages] [Bug 1942208] Re: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers"
** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Status: New => In Progress ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1942208 Title: The nvidia-dkms will be installed when installing nvidia driver through "Additional Drivers" Status in OEM Priority Project: Confirmed Status in software-properties package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: [steps to reproduce] 1. Install Stock ubuntu 20.04.3 on XPS 15 9510 2. Installing without using "Third-party packages" 3. After installation completed, launch "Software & Updates" -> "Additional Drivers" -> "Using NVIDIA driver 470" 4. dpkg -l | grep nvidia [Expected result] It should use pre-signed nvidia driver instead of dkms e.g. linux-modules-nvidia-470-5.11.0-27-generic linux-modules-nvidia-470-generic-hwe-20.04 linux-objects-nvidia-470-5.11.0-27-generic linux-signatures-nvidia-5.11.0-27-generic [Actual result] ii nvidia-dkms-470 470.57.02-0ubuntu0.20.04.1 amd64 NVIDIA DKMS package --- $ lsb_release -rd Description: Ubuntu 20.04.3 LTS Release: 20.04 $ apt-cache policy software-properties-* software-properties-gtk: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages software-properties-kde: Installed: (none) Candidate: (none) Version table: software-properties-qt: Installed: (none) Candidate: 0.98.9.5 Version table: 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/universe i386 Packages 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/universe i386 Packages software-properties-common: Installed: 0.98.9.5 Candidate: 0.98.9.5 Version table: *** 0.98.9.5 500 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages 0.98.9 500 500 http://tw.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://tw.archive.ubuntu.com/ubuntu focal/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942208/+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
[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: Triaged => In Progress -- 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/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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
[Desktop-packages] [Bug 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
** Also affects: nvidia-prime (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: nvidia-prime (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-prime (Ubuntu Focal) Status: New => Triaged ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: New => Triaged ** Changed in: nvidia-prime (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-prime (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: nvidia-prime (Ubuntu Hirsute) Status: Triaged => In Progress ** Changed in: nvidia-prime (Ubuntu) Status: New => Invalid -- 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/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-prime source package in Focal: In Progress Status in nvidia-prime source package in Hirsute: In Progress Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946434/+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
[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
All uploaded. -- 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/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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
[Desktop-packages] [Bug 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
I added a couple of fixes that you missed in the debdiffs, and I uploaded the packages. I put the changelogs for the uploads in the bug description. ** Description changed: [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power + * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. + * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] + + Changelogs: + + nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium + + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) + + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. + + + nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium + + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) + + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). -- 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/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-prime source package in Focal: In Progress Status in nvidia-prime source package in Hirsute: In Progress Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when
[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: New => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Invalid -- 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/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
@jeremyszu I think you will also want LP: #1946476 -- 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/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: In Progress Status in nvidia-prime package in Ubuntu: Fix Released Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+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
[Desktop-packages] [Bug 1946476] [NEW] New on-demand default causes RTD3 never to be enabled
Public bug reported:
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.
** Affects: nvidia-prime (Ubuntu)
Importance: Critical
Assignee: Alberto Milone (albertomilone)
Status: In Progress
--
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:
In Progress
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 : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Also affects: nvidia-prime (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-prime (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-prime (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-prime (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
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/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
In Progress
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
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/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
In Progress
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+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
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on laptop
** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Summary changed: - Nvidia doesn't support RTD3 on laptop + Nvidia doesn't support RTD3 on non-laptops -- 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/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+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
[Desktop-packages] [Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop
** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-failed verification-failed-focal verification-failed-groovy verification-failed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Fix Committed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Fix Committed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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
[Desktop-packages] [Bug 1808874] Re: nvidia-detector doesn't seem to detect nvidia
@Daniel: I should know, since I am the author. Please don't use nvidia- detector for that. You can use the ubuntu-drivers tool instead. Have a look at the following wiki page on how to use ubuntu-drivers: https://help.ubuntu.com/community/NvidiaDriversInstallation -- 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/1808874 Title: nvidia-detector doesn't seem to detect nvidia Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: bdmurray@flash:~$ grep nvidia /proc/modules nvidia_uvm 757760 0 - Live 0x (POE) nvidia_drm 40960 1 - Live 0x (POE) nvidia_modeset 1110016 3 nvidia_drm, Live 0x (POE) nvidia 14360576 84 nvidia_uvm,nvidia_modeset, Live 0x (POE) drm_kms_helper 172032 1 nvidia_drm, Live 0x drm 401408 4 nvidia_drm,drm_kms_helper, Live 0x ipmi_msghandler 53248 2 nvidia,ipmi_devintf, Live 0x bdmurray@flash:~$ nvidia-detector none bdmurray@flash:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1808874/+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
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
Sorry but the NVIDIA 340 driver reached end of life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Focal: Fix Released Status in nvidia-graphics-drivers-340 source package in Groovy: Fix Released Bug description: SRU request: [Impact] * Installing the 340 driver will fail when running Linux 5.7 or newer. [Test Case] * Install nvidia-340 from -proposed. * Check that the modules was built and installed, using the following command: dkms status [Regression Potential] * The driver once built and installed could be not working and lead to have the desktop not starting for example. Check that you get a desktop loaded and decent performances Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+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
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
@Jeff The error that you see in groovy, which you can safely ignore, is because of the missing aplay. What's the output of the following command for both bionic and groovy, please? ubuntu-drivers debug -- 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/1898601 Title: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU Request [Impact] * ubuntu-drivers installs unnecessary packages when using the "-- gpgpu" argument. Also, it should not depend on alsa-utils, its relevant test should. [Fix] * Passing in "--no-install-recommends" by default with the "--gpgpu" argument will solve the problem. Also, moving the alsa-utils dependency into the test avoids installing an unneeded dependency on servers. [Test Case] * Install ubuntu-drivers-common from -proposed. * Make sure it doesn't pull in alsa-utils. * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", and check that the desktop related dependencies are not pulled in. [Regression Risk] Low, since it changes the amount of dependencies we install on servers. +++Update+++ I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2
[Desktop-packages] [Bug 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
I uploaded ubuntu-drivers-common_0.9.0~0.18.04.2 where I reverted the change that was causing the build failure (since we don't have the list- oem feature in bionic). -- 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/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Groovy: Fix Committed Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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
[Desktop-packages] [Bug 1930937] Re: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop
That is probably the reason why we picked gnome-shell as the first dependency. Packages in main should not depend on packages in universe. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Fix Committed Status in screen-resolution-extra source package in Groovy: Fix Committed Status in screen-resolution-extra source package in Hirsute: Fix Committed Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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
[Desktop-packages] [Bug 1898601] Re: 'ubuntu-drivers --gpgpu install' installs a lot of unnecessary packages, including a full desktop environment on Ubuntu Server
SRU team, please accept ubuntu-drivers-common 0.9.0~0.21.04.1, 0.9.0~0.20.10.1, 0.9.0~0.20.04.1, and 0.9.0~0.18.04.1 into -proposed. ** Description changed: + SRU Request + + [Impact] + + * ubuntu-drivers installs unnecessary packages when using the "--gpgpu" + argument. Also, it should not depend on alsa-utils, its relevant test + should. + + [Fix] + + * Passing in "--no-install-recommends" by default with the "--gpgpu" + argument will solve the problem. Also, moving the alsa-utils dependency + into the test avoids installing an unneeded dependency on servers. + + [Test Case] + + * Install ubuntu-drivers-common from -proposed. + + * Make sure it doesn't pull in alsa-utils. + + * Install the nvidia driver using "sudo ubuntu-drivers install --gpgpu", + and check that the desktop related dependencies are not pulled in. + + [Regression Risk] + Low, since it changes the amount of dependencies we install on servers. + + + +++Update+++ - I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. + I am in a position where I need to run regression testing using the nVidia drivers on systems configured for GPU compute. This bug prevents me from using ubuntu-drivers to ensure I have the latest Ubuntu Signed drivers. To resolve this, ubuntu-drivers would need to honor --no-install-recommends and not install all those unnecessary desktop environment packages that make no sense on a headless server - When I install the packaged nVidia drivers using --gpgpu, I expect that I am getting compute related GPGPU drivers. Instead, I find that on a fresh Focal installation of Ubuntu Server, I also get a full desktop environment. This sets us up nicely for this bug: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559 because this pulls in gdm3 and a whole host of unnecessary desktop packages but does nothing to mitigate the gdm3 propensity to autosuspend, which makes the server become unresponsive when there is no user activity (even when it's running workloads on the GPGPU, the server can still autosuspend). Additionally, this adds a software stack that causes unnecessary CPU and memory usage on a machine that is meant to run headless and devote all resources to handling GPGPU compute activities. This is gpgpu mode Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: apg aptdaemon aptdaemon-data aspell aspell-en avahi-daemon avahi-utils bluez bubblewrap colord colord-data cracklib-runtime cups-pk-helper dbus-x11 dconf-cli desktop-file-utils dictionaries-common docbook-xml emacsen-common enchant-2 evolution-data-server evolution-data-server-common fprintd gcr gdm3 geoclue-2.0 gir1.2-accountsservice-1.0 gir1.2-atspi-2.0 gir1.2-gck-1 gir1.2-gcr-3 gir1.2-gdesktopenums-3.0 gir1.2-gdm-1.0 gir1.2-geoclue-2.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 gir1.2-graphene-1.0 gir1.2-gweather-3.0 gir1.2-ibus-1.0 gir1.2-mutter-6 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-notify-0.7 gir1.2-polkit-1.0 gir1.2-rsvg-2.0 gir1.2-secret-1 gir1.2-soup-2.4 gir1.2-upowerglib-1.0 gir1.2-vte-2.91 gjs gkbd-capplet gnome-control-center gnome-control-center-data gnome-control-center-faces gnome-desktop3-data gnome-keyring gnome-keyring-pkcs11 gnome-menus gnome-online-accounts gnome-session-bin gnome-session-common gnome-settings-daemon gnome-settings-daemon-common gnome-shell gnome-shell-common gnome-startup-applications gnome-user-docs gstreamer1.0-clutter-3.0 hunspell-en-us ibus ibus-data ibus-gtk ibus-gtk3 iio-sensor-proxy im-config ippusbxd language-selector-gnome libappindicator3-1 libasound2-plugins libaspell15 libavahi-core7 libavahi-glib1 libcamel-1.2-62 libcanberra-gtk3-0 libcanberra-gtk3-module libcanberra-pulse libcheese-gtk25 libclutter-gtk-1.0-0 libcolord-gtk1 libcolorhug2 libcrack2 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 libebackend-1.2-10 libebook-1.2-20 libebook-contacts-1.2-3 libecal-2.0-1 libedata-book-1.2-26 libedata-cal-2.0-1 libedataserver-1.2-24 libedataserverui-1.2-2 libenchant-2-2 libexif12 libfontenc1 libfprint-2-2 libgail-common libgail18 libgck-1-0 libgcr-base-3-1 libgcr-ui-3-1 libgd3 libgdata-common libgdata22 libgdm1 libgee-0.8-2 libgeoclue-2-0 libgeocode-glib0 libgjs0g libgles2 libgnome-autoar-0-0 libgnome-bluetooth13 libgnome-desktop-3-19 libgnomekbd-common libgnomekbd8 libgoa-1.0-0b libgoa-1.0-common libgoa-backend-1.0-1 libgphoto2-6 libgphoto2-l10n libgphoto2-port12 libgsound0 libgssdp-1.2-0 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common libgtop-2.0-11 libgtop2-common libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libgweather-3-16 libgweather-common libharfbuzz-icu0
[Desktop-packages] [Bug 1931514] Re: SRU: The NVIDIA X server Settings is blank when under Intel mode
SRU team, please accept ubuntu-drivers-common 0.9.0~0.21.04.1, 0.9.0~0.20.10.1, 0.9.0~0.20.04.1, and 0.9.0~0.18.04.1 into -proposed. ** Summary changed: - The NVIDIA X server Settings is blank when under Intel mode + SRU: The NVIDIA X server Settings is blank when under Intel mode ** Description changed: + SRU Request + + [Impact] + + * The NVIDIA X server Settings does not show anything when the intel + mode(Power Saving Mode) is working, so that it cannot switch back to + Nvidia mode(Performance Mode) in the settings. + + [Fix] + + * Looking for the nvidia modules in the linux-restricted-modules path + will solve the problem. + + [Test Case] + + * Boot up the system and login. + + * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. + * Open the NVIDIA X Server Settings again. + + * Check that the panel is not blank. + + [Regression Risk] + Medium, since it changes the code which finds the kernel modules. + _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem -- 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/1931514 Title: SRU: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: SRU Request [Impact] * The NVIDIA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Fix] * Looking for the nvidia modules in the linux-restricted-modules path will solve the problem. [Test Case] * Boot up the system and login. * Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. * Open the NVIDIA X Server Settings again. * Check that the panel is not blank. [Regression Risk] Medium, since it changes the code which finds the kernel modules. _ [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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
[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
** Also affects: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu Bionic) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Alberto Milone (albertomilone) -- 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/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in ubuntu-drivers-common source package in Bionic: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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
[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop
@SRU team: please accept screen-resolution-extra 0.18.0.21.04.1, 0.18.0.20.10.1, and 0.18.0.20.04.1 into -proposed. ** Description changed: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome- shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia- settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. + + [Impact] + + * Installing the nvidia-settings package causes gnome-shell to be + installed. This is less than ideal on servers. + + [Fix] + + * Moving policykit-1-gnome ahead as the first of the polkit dependencies + will solve the problem. + + [Test Case] + + * Install screen-resolution-extra from proposed on a system where no + polkit-1-auth-agent provider is installed, and check that gnome-shell is + not installed as a dependency. + + [Regression Risk] + Low, as the change will still allow the dependency to be satisfied. ** Summary changed: - Default dependency resolution in Focal pulls in full GNOME Desktop + SRU: Default dependency resolution in Focal pulls in full GNOME Desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: SRU: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Triaged Status in screen-resolution-extra source package in Groovy: Triaged Status in screen-resolution-extra source package in Hirsute: Triaged Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. [Impact] * Installing the nvidia-settings package causes gnome-shell to be installed. This is less than ideal on servers. [Fix] * Moving policykit-1-gnome ahead as the first of the polkit dependencies will solve the problem. [Test Case] * Install screen-resolution-extra from proposed on a system where no polkit-1-auth-agent provider is installed, and check that gnome-shell is not installed as a dependency. [Regression Risk] Low, as the change will still allow the dependency to be satisfied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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
[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop
** No longer affects: screen-resolution-extra (Ubuntu Bionic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to screen-resolution-extra in Ubuntu. https://bugs.launchpad.net/bugs/1930937 Title: Default dependency resolution in Focal pulls in full GNOME Desktop Status in screen-resolution-extra package in Ubuntu: Triaged Status in screen-resolution-extra source package in Focal: Triaged Status in screen-resolution-extra source package in Groovy: Triaged Status in screen-resolution-extra source package in Hirsute: Triaged Bug description: In Bionic, screen-resolution-extra has a dependency on policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent. As a result, when install screen-resolution-extra (e.g. as a dependency of nvidia-settings) on a system that doesn't already have GNOME or another polkit auth agent installed, the default dependency resolution pulls in a full GNOME desktop in Focal, while it does not do so under the same circumstances in Bionic. This can be worked around by explicitly installing policykit-1-gnome (or another package which provides the polkit-1-auth-agent virtual package), but it would be nice to not pull in GNOME by default on a system that doesn't already have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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
[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => Critical -- 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/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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
[Desktop-packages] [Bug 1931514] Re: The NVIDIA X server Settings is blank when under Intel mode
I have integrated, modified, and uploaded the changes to this PPA: https://launchpad.net/~albertomilone/+archive/ubuntu/u-d-c-release Please give it a try and see if it solves the problem. If it does, I will proceed with the SRU. -- 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/1931514 Title: The NVIDIA X server Settings is blank when under Intel mode Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Summary] The VIIDA X server Settings does not show anything when the intel mode(Power Saving Mode) is working, so that it cannot switch back to Nvidia mode(Performance Mode) in the settings. [Steps to reproduce] 1. Boot up the system and login. 2. Open the NVIDIA X Server Settings. If it shows the NVIDIA display card is working, switch it to intel display card and reboot. 3. Open the NVIDIA X Server Settings again. It does not show anything, and just a blank dialog. mode [Expected result] The NVIDIA X Server Settings should show all configurations, and users can switch them in it. [Actual result] The dialog is blank. [Failure rate] 100% [Additional information] ubuntu: 20.04.2 kernel-version: 5.10.0-1029-oem To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1931514/+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
[Desktop-packages] [Bug 1930937] Re: Default dependency resolution in Focal pulls in full GNOME Desktop
** Changed in: screen-resolution-extra (Ubuntu)
Status: New => Triaged
** Changed in: screen-resolution-extra (Ubuntu)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Also affects: screen-resolution-extra (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: screen-resolution-extra (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: screen-resolution-extra (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: screen-resolution-extra (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: screen-resolution-extra (Ubuntu Bionic)
Status: New => Triaged
** Changed in: screen-resolution-extra (Ubuntu Focal)
Status: New => Triaged
** Changed in: screen-resolution-extra (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: screen-resolution-extra (Ubuntu Groovy)
Status: New => Triaged
** Changed in: screen-resolution-extra (Ubuntu Hirsute)
Status: New => Triaged
** Changed in: screen-resolution-extra (Ubuntu Bionic)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: screen-resolution-extra (Ubuntu Focal)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: screen-resolution-extra (Ubuntu Groovy)
Assignee: (unassigned) => Alberto Milone (albertomilone)
** Changed in: screen-resolution-extra (Ubuntu Hirsute)
Assignee: (unassigned) => Alberto Milone (albertomilone)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to screen-resolution-extra in Ubuntu.
https://bugs.launchpad.net/bugs/1930937
Title:
Default dependency resolution in Focal pulls in full GNOME Desktop
Status in screen-resolution-extra package in Ubuntu:
Triaged
Status in screen-resolution-extra source package in Bionic:
Triaged
Status in screen-resolution-extra source package in Focal:
Triaged
Status in screen-resolution-extra source package in Groovy:
Triaged
Status in screen-resolution-extra source package in Hirsute:
Triaged
Bug description:
In Bionic, screen-resolution-extra has a dependency on
policykit-1-gnome | polkit-1-auth-agent. Focal replaces this with a
dependency on gnome-shell | policykit-1-gnome | polkit-1-auth-agent.
As a result, when install screen-resolution-extra (e.g. as a
dependency of nvidia-settings) on a system that doesn't already have
GNOME or another polkit auth agent installed, the default dependency
resolution pulls in a full GNOME desktop in Focal, while it does not
do so under the same circumstances in Bionic. This can be worked
around by explicitly installing policykit-1-gnome (or another package
which provides the polkit-1-auth-agent virtual package), but it would
be nice to not pull in GNOME by default on a system that doesn't
already have it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/screen-resolution-extra/+bug/1930937/+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
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
I think we need better detection code upstream, since the NVIDIA 470 driver will have full Wayland (and accelerated XWayland) support, and the udev rule should take this into account. -- 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/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
Here is the difference: DRIVER Match the driver name of the event device. Only set this key for devices which are bound to a driver at the time the event is generated. DRIVERS Search the devpath upwards for a matching device driver name. https://www.freedesktop.org/software/systemd/man/udev.html I assume the device is not always bound to the driver when the event is generated. -- 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/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
yes, it is the ubuntu session (I wasn't given a choice on login). Can you try replacing "DRIVER" with "DRIVERS" in /lib/udev/rules.d/61-gdm.rules , please? -- 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/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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
[Desktop-packages] [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session
I don't get that at all (see the attached screenshot). Detection seems to work well here: giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on Wayland... giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on X11... giu 01 16:05:52 dell-g7 systemd[1725]: app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Succeeded. giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: Control process exited, code=exited, status=2/INVALIDARGUMENT giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: Skipped due to 'exec-condition'. giu 01 16:05:52 dell-g7 systemd[1725]: Condition check resulted in GNOME Shell on Wayland being skipped. ** Attachment added: "Screenshot from 2021-06-01 16-08-04.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501675/+files/Screenshot%20from%202021-06-01%2016-08-04.png -- 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/1925238 Title: [nvidia-prime] switches between xorg and wayland session Status in ubuntu-drivers-common package in Ubuntu: New Status in ubuntu-drivers-common source package in Hirsute: New Status in ubuntu-drivers-common source package in Impish: New Bug description: I have noticed this on a hirsute install from today's RC media (20210420) with ubuntu-drivers-common 1:0.8.9.1. The first boot is always xorg, and nvidia mode is selected. After that reboots are *usually* wayland, but sometimes they are xorg too. Performance mode is selected in nvidia-settings, which is supposed to mean nvidia & therefore xorg but it's not working. Selecting it explicitly doesn't help either. What is the default meant to be - probably ondemand? Seems like it's somehow nondeterministic. Attaching some logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+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
