Upstream has already "fixed" it by reverting the change in a later release:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3030 Although this seems to be because they were waiting on a fix in Xwayland version 23.1.0 which Ubuntu 22.04 doesn't have yet. It looks like the downside they were trying to avoid was: > sending modifiers to clients prevents direct scanout for DRI3 clients via Xwayland so it was just to make full screen gaming performance better. If you can live without that optimization then you should keep MUTTER_DEBUG_SEND_KMS_MODIFIERS=1. Starting in 23.10 we have the best of both worlds so you won't need to choose anymore. ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
