Additional reproduction detail after changing the primary monitor: Original setup was Dell AW3420DW on DP-3 at 3440x1440@120Hz as primary, with LG ULTRAGEAR on HDMI-1 at [email protected] as secondary. In that setup, GNOME Shell overlay/compositor UI reliably triggered the visible flicker/ghosting, especially Settings > Displays > Identify Screens, the top-bar date/time menu, polkit/auth prompts, notifications, and window/titlebar dragging.
Test performed: changed the primary display to the LG while leaving the same two monitors connected and both still around 120Hz. No GRUB/kernel parameters, cables, or GNOME experimental features were changed for this test. Result: Settings > Displays > Identify Screens, which had previously triggered the issue consistently, did not trigger the flicker during this test with the LG as primary. This makes the issue look less like a failing panel and more like something in the GNOME Shell/Mutter overlay/compositor path for the primary monitor, interacting with Intel i915/GBM and this dual high- refresh monitor setup. The earlier gbm_surface_lock_front_buffer / buffer age errors are still the main relevant user-session logs from the failure case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155412 Title: Wayland desktop flicker with gbm_surface_lock_front_buffer failed on Intel i915 dual high-refresh monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2155412/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
