PrusaSlicer [2.7.4, 2.8.0] UI fails to open under WSL2

Description of the bug

Running prusa-slicer under WSL2 fails to open the UI. The exact error output follows:

$ prusa-slicer 
./src/gtk/msgdlg.cpp(278): assert ""m_widget"" failed in ShowModal(): failed to create GtkMessageDialog

(prusa-slicer:2375): GLib-GObject-CRITICAL **: 22:27:16.906: invalid (NULL) pointer instance

(prusa-slicer:2375): GLib-GObject-CRITICAL **: 22:27:16.906: g_signal_handlers_disconnect_matched: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

This used to work very well before, as recently as two months ago. It must have been broken by a recent sudo apt update && sudo apt upgrade.

Interestingly I am able to run prusa-slicer when manually running Xwayland:

Xwayland -geometry 1280x720 :1 &
DISPLAY=:1 prusa-slicer

But this doesn't seem to integrate at all with the display server WSL runs automatically.

Project file & How to reproduce

$ apt search prusa-slicer 
prusa-slicer/unstable,now 2.7.4+dfsg-1.1 amd64 [installed]
  G-code generator for 3D printers
$ sudo apt install prusa-slicer
# ...
$ prusa-slicer

Checklist of files included above

[ ] Project file
[ ] Screenshot

Version of PrusaSlicer

PrusaSlicer-2.7.4+UNKNOWN based on Slic3r (with GUI support) PrusaSlicer-2.8.0+UNKNOWN based on Slic3r (with GUI support)

Operating system

Windows 10, WSL2, Debian unstable

Printer model

LulzBot Mini 1.3

prusa3d / PrusaSlicer