QtWayland applications appear to all inexplcably hang, usually after creating and destroying a few parent windows, but it doesn't seem to be the direct cause

I saw some glib poll stuff in the stack trace, setting QT_NO_GLIB=1 still results in a hang, but different things in the stack

I did the best of getting a stack trace, of randomly pressing CTRL+C after a hang.... what's odd is that when I export WAYLAND_DEBUG=client, once the application hangs (Weston shows the wait cursor, the window stops responding), moving the cursor over the window when it is still active still causes things to scroll in the terminal

I got a stack trace of two different applications kdialog and dolphin, because I can replicate it easier after creating child windows.... One stack trace has all the threads of the application, one just has the default thread