I also checked bug 2152207. This issue seems related in that both
involve GNOME 50 / Wayland / multi-monitor setups and repeated:
gbm_surface_lock_front_buffer failed
However my case differs from bug 2152207 in some important ways:
* This system uses NVIDIA RTX A4500 GPUs with nvidia-driver-595-open, not
Intel/AMD Mesa graphics.
* The failure happens during lock-screen recovery.
* gnome-shell grows to very high VRAM usage on the display-attached NVIDIA
GPU.
* The kernel logs NVIDIA-specific allocation failures:
[nvidia-drm] Failed to allocate NVKMS memory for GEM object
* I also see:
Failed to post KMS update: drmModeAtomicCommit: Invalid argument
I tested DISABLE_DIRECT_SCANOUT as suggested, but it did not fix the
issue.
So this may share the same Mutter/GBM/front-buffer failure path as bug
2152207, but it may be a separate NVIDIA-specific failure mode or a case
where gnome-shell/NVIDIA VRAM exhaustion leads to similar front-buffer
failures.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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/mutter/+bug/2154316/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
