The bug doesn't happen if I build mutter/gnome-shell from git. The bug still doesn't happen if I build the Ubuntu 42.1 tags (jammy) from salsa, with all Ubuntu patches.
Using the jammy release binaries the bug still occurs consistently. I am not getting any results from gjs_dumpstack anymore (like above), but earlier in the day I did get: == Stack trace for context 0x56139f48b4a0 == gnome-shell[10091]: #0 7ffc53926a00 I resource:///org/gnome/shell/ui/windowManager.js:314 (2b03e27293d0 @ 78) gnome-shell[10091]: #1 7ffc53926a50 I self-hosted:1181 (2e95f68b0a10 @ 454) So actually that's the same as Marco mentioned in comment #13. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1976204 Title: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
