Screen blank except for Steam Overlay when using OpenGL on Ubuntu 22.04, GNOME Wayland

[smcv]

To reproduce:

• Steam beta 1672959571 (2023-01-05 19:23:52)
  • Steam Runtime 0.20221019.0
• Not currently using Steam Linux Runtime compatibility tool (but I have also reproduced this with SLR)
• GNOME in Wayland mode
  • I'm currently using Ubuntu's customized GNOME but I've also seen this on Debian's mostly-upstream GNOME
• The machine I'm using right now is Ubuntu 22.04 with NVIDIA 510.108.03 driver on GP104 (GeForce GTX 1080)
  • I've also reproduced this on Debian 12 alpha with Mesa on an AMD GPU
• Launch Portal 2 with no special options

Expected result:

• Valve logo video plays
• Steam overlay popup advertising Remote Play appears in bottom right corner and then slides out of view
• Portal menu
• I can load a saved game

Actual result:

• I hear the soundtrack of the Valve logo video, but the screen remains black
• The mouse pointer remains visible and I can move it around
• The Steam overlay popup appears and slides out of view, but the outline of each position remains on the screen, as though the buffer isn't being cleared before each frame (see screenshot)
• After the Valve logo video has finished, the screen remains black
• I can move the mouse around and hear sounds as it moves over where the main menu items ought to be
• Alt+F4 exits correctly

Workaround:

• If I set the launch options to %command% -vulkan, Portal 2 works as expected, even in Wayland
• Or, if I log out, and log back in with GNOME in Xorg mode (this might be labelled "... on Xorg" if Wayland is the default, or with no special suffix if Xorg is the default), Portal 2 works as expected

Logs:

• System Information under Wayland
• GL, Wayland (bug visible)

Logs with workarounds, for comparison:

• Vulkan, Wayland (works)
• System Information under Xorg
• GL, Xorg (works)
• Vulkan, Xorg (works)

[smcv]

Note that I am not using SDL_VIDEODRIVER=wayland: Portal should be rendering via X11 in all cases (either native X11, or Xwayland).

Xwayland is version 2:22.1.1-1ubuntu0.4 from Ubuntu 22.04.

[smcv]

Trying this again on Debian 12 alpha (with GNOME 43, Mesa 22.3.1-1 and xwayland 2:22.1.6-1 among other significant components), I can no longer reproduce this bug there, so this might be solved by using a newer version of some component than the ones in Ubuntu 22.04.