| Plasma |
Dialog might try to set PlasmaShellSurface before Wayland Server has sent
the PlasmaShell proxy to DialogShadows. This can be observed with KWin's
TabBox.
Connect to DialogShadows new signal waylandPlasmaShellInterfaceAnnounced
in case the PlasmaShell interface has not yet been announced.
Manual debug statement shows that DialogPrivate::shellSurface is set.
| No Linters Available |
| No Unit Test Coverage |
This doesn't make sense (assuming everything else works correctly, which clearly isn't the case)
registry->setup(); connection->roundtrip();
should mean the server will announce all the interfaces and we block all execution until we've processed it all.
which means we "know" by the time we finish DialogShadows::Private::setupWaylandIntegration() we know plasmaShellAnnounced will have been emitted and that the plasmashell has been set. That's how it works in the regular case.
roundTrip goes via the QPA, and that has been implemented in Kwin's QPA.
DialogShadows is created as Q_GLOBAL_STATIC. Maybe that's why it's not blocking for the Dialog object initializing it.
Also wouldn't it be a deadlock if execution of KWin is stopped until the Wayland server, i.e. KWin, has processed all events? Or is the Tabbox QML code running in a different thread?
I wouldn't change plasmaquick based on KWin's behavior. KWin is weird after all. We should rather work around inside KWin.