Public bug reported:
On Ubuntu 26.04 with GNOME Shell 50.1, Mutter 50.1, GDM 50.0, NVIDIA
driver 595.71.05 open, and dual NVIDIA RTX A4500 GPUs, the Wayland
graphical session repeatedly fails to recover from the locked state.
The affected user session is Wayland and has appeared on tty2 previously
and tty5 in the current incident. I can switch to a text console, but
the graphical session/greeter often remains unusable.
journalctl repeatedly shows:
gnome-shell: Failed to lock front buffer on /dev/dri/card2:
gbm_surface_lock_front_buffer failed
gnome-shell: meta_frame_native_release: assertion '!frame_native->kms_update'
failed
gnome-shell: Failed to query buffer age, got error 300d
nvidia-smi shows the display GPU nearly full and gnome-shell holding
enormous GPU memory. Current example:
GPU 1: 19330 MiB / 20470 MiB used
gnome-shell PID 1613912: 18331 MiB
Chrome was running with a Wayland GPU process in the current incident.
Killing Chrome removed all Chrome processes, but GPU 1 remained high at
18669 MiB, indicating gnome-shell retained the GPU memory.
In a later check during the same incident, Chrome had restarted. Killing
Chrome again reduced GPU 1 memory from the previously high state to
about 903 MiB, and the user was able to log in again. This makes Chrome
a strong trigger or contributing factor, although the compositor/GDM
logs still show the failure as GNOME Shell being unable to lock front
buffers on /dev/dri/card2.
This appears to be a GNOME Shell / Mutter / Wayland / NVIDIA DRM-KMS
issue involving /dev/dri/card2. Chrome may trigger or worsen it, but the
compositor memory remains after Chrome exits.
1) Ubuntu release:
Ubuntu 26.04 LTS
Release: 26.04
Codename: resolute
2) Package versions:
gnome-shell 50.1-0ubuntu1
mutter 50.1-0ubuntu2
gdm3 50.0-0ubuntu1
ubuntu-session 50.0-0ubuntu3.1
nvidia-driver-595-open 595.71.05-0ubuntu0.26.04.1
xwayland 2:24.1.10-1
3) What I expected:
After locking the GNOME Wayland session, I expected the lock screen or GDM
greeter to remain responsive and allow me to unlock and return to the existing
graphical session without losing state.
4) What happened instead:
The graphical session repeatedly failed to recover from the locked state. I
could switch to a text console, but the Wayland session/greeter often remained
unusable.
journalctl repeatedly showed:
gnome-shell: Failed to lock front buffer on /dev/dri/card2:
gbm_surface_lock_front_buffer failed
gnome-shell: meta_frame_native_release: assertion '!frame_native->kms_update'
failed
gnome-shell: Failed to query buffer age, got error 300d
nvidia-smi showed the display GPU nearly full, with gnome-shell holding
very high GPU memory, for example:
GPU 1: 19330 MiB / 20470 MiB used
gnome-shell PID 1613912: 18331 MiB
Chrome was running with a Wayland GPU process during the incident.
Killing Chrome sometimes helped recovery, but GNOME Shell/GDM still
showed the front-buffer errors on /dev/dri/card2.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: gnome-shell 50.1-0ubuntu1
ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0
Uname: Linux 7.0.0-15-generic x86_64
ApportVersion: 2.34.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue May 26 14:39:54 2026
DisplayManager: gdm3
InstallationDate: Installed on 2026-05-15 (11 days ago)
InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1)
RelatedPackageVersions: mutter-common 50.1-0ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lockscreen nvidia regression resolute wayland
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2154316
Title:
GNOME Shell Wayland NVIDIA lock screen recovery fails with
gbm_surface_lock_front_buffer and high gnome-shell GPU memory
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2154316/+subscriptions
--
desktop-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
