** Description changed: - Summary: Continuous gbm_surface_lock_front_buffer failed on AMD Cezanne APU with dual monitor + Xwayland Electron app - Description: - On Ubuntu 26.04 LTS with GNOME 50.1 and Mutter 50.1-0ubuntu2, launching any Electron-based application via Wine 11.0 under Xwayland while a second monitor is connected causes continuous gbm_surface_lock_front_buffer failed errors on /dev/dri/card1, resulting in visible rainbow pixel corruption at the monitor boundary. - Hardware: Lenovo ThinkPad T14 Gen 2 AMD, Cezanne APU (Radeon Vega, PCI 1002:1638), single GPU driving internal eDP-1 (laptop display) + external HDMI-A-1 simultaneously. - Trigger: Electron app running under Wine 11.0 via Xwayland with dual monitors connected. Corruption stops immediately when second monitor is disconnected. No corruption occurs with non-Electron Wine apps under the same conditions. - Errors from journalctl: + [ Impact ] + + Some multi-monitor setups using GNOME 50 in Ubuntu 26.04 experience + corruption on one monitor and/or repeating log messages: + gnome-shell[5444]: Failed to lock front buffer on /dev/dri/card1: gbm_surface_lock_front_buffer failed gnome-shell[5444]: Failed to query buffer age, got error 3003 - These fire hundreds of times per minute during the affected session. - Notes: PSR is disabled (psr_state: 0), Panel Replay is disabled, amdgpu.dcdebugmask=0x10 is set. Mutter 50.1 GPU fixes are all Nvidia-specific and do not address this AMD single-GPU dual-monitor Xwayland path. - ProblemType: Bug - DistroRelease: Ubuntu 26.04 - Package: mutter (not installed) - 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: pass - CurrentDesktop: ubuntu:GNOME - Date: Mon May 11 14:07:24 2026 - InstallationDate: Installed on 2026-04-14 (27 days ago) - InstallationMedia: Ubuntu 24.04.4 LTS "Noble Numbat" - Release amd64 (20260210) - ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> - SourcePackage: mutter - UpgradeStatus: Upgraded to resolute on 2026-04-27 (14 days ago) + The problem sometimes starts slowly with just the "Failed to lock front + buffer" message a few times. + + [ Test Plan ] + + Known prerequisites for the bug: + * Mesa version <= 26.0.9 + * Using multiple monitors (seems to be required but maybe not in all cases) + * Using Intel or AMD graphics for some or all displays + + There is no known test case that can reproduce it with certainty even + with the above prerequisites, so we currently rely on affected users to + give us feedback on what works. + + [ Where problems could occur ] + + The fix affects front buffer management in Mesa so could potentially + affect any graphics users in any desktop environment in unpredictable + ways. + + [ Other Info ] + + Potential overlap with AMD bug 2148088 could confuse some users. People + might be affected by one bug and be commenting in the other, or could be + affected by both bugs simultaneously.
** Description changed: [ Impact ] Some multi-monitor setups using GNOME 50 in Ubuntu 26.04 experience corruption on one monitor and/or repeating log messages: gnome-shell[5444]: Failed to lock front buffer on /dev/dri/card1: gbm_surface_lock_front_buffer failed gnome-shell[5444]: Failed to query buffer age, got error 3003 The problem sometimes starts slowly with just the "Failed to lock front buffer" message a few times. [ Test Plan ] Known prerequisites for the bug: - * Mesa version <= 26.0.9 + * Mesa version < 26.2 * Using multiple monitors (seems to be required but maybe not in all cases) * Using Intel or AMD graphics for some or all displays There is no known test case that can reproduce it with certainty even with the above prerequisites, so we currently rely on affected users to give us feedback on what works. [ Where problems could occur ] The fix affects front buffer management in Mesa so could potentially affect any graphics users in any desktop environment in unpredictable ways. [ Other Info ] Potential overlap with AMD bug 2148088 could confuse some users. People might be affected by one bug and be commenting in the other, or could be affected by both bugs simultaneously. ** Description changed: [ Impact ] Some multi-monitor setups using GNOME 50 in Ubuntu 26.04 experience corruption on one monitor and/or repeating log messages: gnome-shell[5444]: Failed to lock front buffer on /dev/dri/card1: gbm_surface_lock_front_buffer failed gnome-shell[5444]: Failed to query buffer age, got error 3003 The problem sometimes starts slowly with just the "Failed to lock front buffer" message a few times. [ Test Plan ] Known prerequisites for the bug: * Mesa version < 26.2 * Using multiple monitors (seems to be required but maybe not in all cases) * Using Intel or AMD graphics for some or all displays There is no known test case that can reproduce it with certainty even with the above prerequisites, so we currently rely on affected users to give us feedback on what works. [ Where problems could occur ] The fix affects front buffer management in Mesa so could potentially - affect any graphics users in any desktop environment in unpredictable + impact any graphics users in any desktop environment in unpredictable ways. [ Other Info ] Potential overlap with AMD bug 2148088 could confuse some users. People might be affected by one bug and be commenting in the other, or could be affected by both bugs simultaneously. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2152207 Title: Failed to lock front buffer on /dev/dri/card1: gbm_surface_lock_front_buffer failed | Failed to query buffer age, got error 3003 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2152207/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
