GNOME Bugzilla – Bug 781068
Fullscreen X application don't change resolution
Last modified: 2021-07-05 13:49:08 UTC
When I exit a game which is using Xwayland in lower resolution it changes the resolution of original desktop. This is problem with HiDPI setups as X applications need to be in lower resolution to be readable.
Sorry - distribution changed default under me. However under XWayland the window is displayed as part of screen. This is problem when gaming on 4K display when GPU is not powerful enough to drive it.
This is something that has to be solved across multiple projects, starting with the X server (Xwayland) and defining a protocol (wayland-protocols) for doing so. Only then will mutter have a chance to deal with this.
If there is nothing in Wayland protocol it might be bigger problem for games trying to be ported to wayland where the GPU is not powerful enough to drive games in correct resolution and/or UI elements are too small on 4K. Arguably a simpler, short term, fix might be for the Xwayland to expose more resolutions and provide rescalling internally i.e. if the Wayland resolution is 4K but game is in 1080p than XWayland performs rescalling before giving the result to wayland server.
(In reply to Maciej (Matthew) Piechotka from comment #3) > If there is nothing in Wayland protocol it might be bigger problem for games > trying to be ported to wayland where the GPU is not powerful enough to drive > games in correct resolution and/or UI elements are too small on 4K. It's not decided exactly how it'll look, but there are some ideas/plans. The question is rather, is it needed that the actual resolution is set to something, or is it enough to scale things using the graphics hardware. Either way, just because it doesn't exist, doesnt' mean we can't add it. > > Arguably a simpler, short term, fix might be for the Xwayland to expose more > resolutions and provide rescalling internally i.e. if the Wayland resolution > is 4K but game is in 1080p than XWayland performs rescalling before giving > the result to wayland server. That could be bad for performance, as Xwayland would need to scale. Adding a Wayland protocol is not the issue really here, it's just work that needs to be done.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/mutter/-/issues/ Thank you for your understanding and your help.