It would not have made any sense to me for Ubuntu to patch Mutter with risky backported code in order for a broken Flatpak runtime to work again anyway. The GNOME 49 runtime introduced this bug, not Ubuntu.
But looking at the communication style in the upstream bug report, after which it was immediately closed and locked, I'm not very hopeful that these legacy code paths will be reintroduced. I hope I'm wrong of course, but they have not particularly left a good impression with this disregard for backward compatibility with stable base distros. (Which I think was one of the things Flatpak intended to solve?) This bug really affects me too, and also a lot of my customers. And I can only assume that Flatpak application maintainers expect their software to work properly on the most widely used distribution (Ubuntu LTSes). So for GNOME to then cause this kind of breakage in a runtime many application developers depend upon and say the users should "look at some other distribution" if the distro won't backport changes with big regression potential leaves quite a bad aftertaste.. Perhaps insiders can influence this better, but for me trying to explain to GNOME developers that introducing a regression like this for something as important as a Flatpak runtime and then shrugging about it and saying you will never fix it and that users should go and distro hop isn't really exactly professional to say the least didn't bring me anywhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2131696 Title: giant cursor in flatpaks that use gnome platform 49 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2131696/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
