https://bugs.kde.org/show_bug.cgi?id=488208
--- Comment #2 from Sergio <sergio.calleg...@gmail.com> --- To work around the issue, it is enough to run plasma with the X11 session or to force Xpra to run working in X11 mode (using XWayland). So once more there is a regression in the wayland session. Given the importance of Xpra in providing network transparency for graphic applications, I would say this is a serious issue and a wayland showstopper in many scenarios. >From the external observer, all this is rather weird. Removing mechanisms in Wayland to anyway providing them in Xwayland leads developers put an effort in making their application work with wayland to then observe it was simply much better with Xwayland. Please, if possible, try to interact with the xpra developer to see what is going on in gnome to make xpra work (since I tend to think that kwin respects the standard here). I might be wrong, but my feeling is that the xpra developer might be experiencing some sense of frurstration in interaction with anything regarding wayland. Showing collaboration might be truly useful to fix this. -- You are receiving this mail because: You are watching all bug changes.
