Window receives old size in fullscreen configuration event

[Frank Praznik]

Ubuntu 24.04 with Wayland

A bug was reported to SDL regarding a client app sporadically not getting the correct dimensions when entering fullscreen. The original report is here: https://github.com/libsdl-org/SDL/issues/9999

The client application is initially creating a non-resizable window, then entering fullscreen. In this case, SDL first removes any min/max limits, commits, then makes the fullscreen request. The issues is that sometimes the corresponding configuration event contains the correct fullscreen dimensions, and other times it sends the old, constrained dimensions.

The full output of WAYLAND_DEBUG=1 is attached, but the relevant bit in a failure scenario is here:

[1653593.718] -> [e-mail]_min_size(0, 0)
[1653593.720] -> [e-mail]_max_size(0, 0)
[1653593.723] -> [e-mail]_window_geometry(0, -24, 1280, 744)
[1653593.726] -> [e-mail]()
[1653593.729] -> [e-mail]_fullscreen(wl_output@6)
[1653593.732] -> [e-mail](new id wl_callback@68)
[1653593.741] -> [e-mail](new id wl_callback@67)
[1653595.811] [e-mail]_id(55)
[1653595.836] [e-mail]_id(68)
[1653595.840] [e-mail]_id(67)
[1653595.843] [e-mail]_bounds(1920, 1048)
[1653595.846] [e-mail](1280, 744, array[8])
[1653595.850] [e-mail](6768)
[1653595.864] -> [e-mail]_destination(1280, 744)
[1653595.868] -> [e-mail]_region(new id wl_region@55)
[1653595.871] -> [e-mail](0, 0, 1280, 744)
[1653595.875] -> [e-mail]_opaque_region(wl_region@55)
[1653595.878] -> [e-mail]()
[1653595.883] -> [e-mail](nil, 0, 0)
[1653595.886] -> [e-mail]()
[1653595.889] -> [e-mail](nil, 0, 0)
[1653595.892] -> [e-mail]()
[1653595.895] -> [e-mail]_window_geometry(0, 0, 1280, 744)
[1653595.898] -> [e-mail]_configure(6768)

The constraints are zeroed and the changes are committed, but the old size is being sent in the fullscreen configuration event. SDL is respecting the reported fullscreen bounds, as it should. If the window is created as resizable and no constraints are ever set, this does not occur.

I'm reporting this here as Ubuntu 24.04 is the only report we've had on this matter, and I've never been able to replicate it on upstream GNOME/Mutter.

[Daniel van Vugt (vanvugt)]

I'm not aware of any Ubuntu-specifics that might cause this. I would suggest:

1. Testing the 46.0 upstream tag to see if it's just that Ubuntu hasn't released the fix yet; and

2. If 46.0 upstream did not have the bug (meaning it can't be bisected), then report an upstream bug anyway since they have more expertise and eyeballs available.