"Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

[Pierre Equoy]

Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
Image: Jammy daily (20220126 build)

Test steps
==========

Secure Boot enabled

Installation options:

- used ubiquity (not the new flutter installer)
- normal installation
- checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats"
- left "Configure Secure Boot" checked
- Setup a password for Secure Boot MOK enrollment
- Used "Erase disk and install Ubuntu" option

After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS.

At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers.

Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia-settings.

--------------------
$ switcherooctl
Device: 0
  Name: Intel® UHD Graphics
  Default: yes
  Environment: DRI_PRIME=pci-0000_00_02_0

Device: 1
  Name: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
  Default: no
  Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
--------------------

Expected result
===============

When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU.

Actual result
=============

However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
Uname: Linux 5.15.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu76
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 28 14:00:33 2022
DisplayManager: gdm3
InstallationDate: Installed on 2022-01-28 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
RelatedPackageVersions: mutter-common 41.3-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Please try:

* Updating the system (mutter and gnome-shell should be version 41 now).

* Adding kernel parameter: nvidia-drm.modeset=1

* nvidia-495 instead of nvidia-470.

[Pierre Equoy (pieq)]

After upgrading to the last version of the packages:

gnome-shell 41.3-1ubuntu1
mutter-common 41.3-1ubuntu1

the issue is gone and I can see the option when right-clicking on a desktop launcher.

[Ken VanDine (ken-vandine)]

I've confirmed that nvidia-470 is getting installed in jammy, not nvidia-495. AFAIK this is a bug, I thought nvidia-495 was in jammy? Without it we don't get a wayland session with nvidia.

[Daniel van Vugt (vanvugt)]

Nvidia-470 has Wayland support if you add kernel parameter nvidia-drm.modeset=1

Also the Nvidia web site (driver downloads) clarifies the difference between the two current driver branches. Defaulting to 470 might still be a good idea for LTS...

Production Branch (470):
Production Branch drivers provide ISV certification and optimal stability and performance for Unix customers. This driver is most commonly deployed at enterprises, providing support for the sustained bug fix and security updates commonly required.

New Feature Branch (495):
New Feature Branch drivers provide early adopters and bleeding edge developers access to the latest driver features before they are integrated into the Production Branches

[jeremyszu (os369510)]

yes, FWIK, we incline to provide the LTS branch (stable) for Ubuntu users.
For some cutting edge graphic cards, which will use 495 (since 470 doesn't support) and the 495 will eventually upgrade to next LTS version (FWIK, 510) in the future.

The installation logic is implemented in ubuntu-drivers-common.

[Sebastien Bacher (seb128)]

It is working on my lenovo test laptop with the current J daily and driver 470 (under xorg or wayland sessions), is anyone still seeing the problem and if so could you provide details on the configuration ahd a journal log?