• @dean @kde @kde I guess so… but why? You’d be limited to the background layer, and this doesn’t really call for a nested Wayland compositor. It may be worth looking at simpler ways to tackle that (depending on exact requirements): screenlocker’s QML UI, a layer-shell client, KWin effect etc.