https://bugs.kde.org/show_bug.cgi?id=395381
--- Comment #12 from James <ja...@nurealm.net> --- > Martin is right, it is a Xwayland bug, and nothing to do with kwin or plasma. > I'm able to use plasma-5.13.1 without this issue by setting QT_QPA_PLATFORM > to QT_QPA_PLATFORM=wayland. Thanks for the work-around. Still, would you please help me to understand what is going on here? First, how does selecting a button on the Plasma Panel - presumably a Wayland-based app - have anything to do with calling-out to Xwayland, an X11 server emulator? Am I basically misunderstanding kwin_wayland? Is kwin_wayland actually just kwin running over Xwayland? Second, if kwin_wayland is *not* simply kwin running over Xwayland, then why would a call to Xwayland not simply be run in a non-blocking manner? And third, how does setting QT_QPA_PLATFORM=wayland bypass the Xwayland bug, in this particular instance, for example, with selection of the Application Launcher from the Panel? Is the KDE Panel an X11 application? I did find "Progress on Plasma Wayland for 5.13" by Roman Gilg, and Martin's "Unsetting QT_QPA_PLATFORM environment variable by default". My more selfish take-away from Martin's comments would be that everyone is dealing with a work-around for a Qt bug, one that has not been resolved even in Qt 5.11. Even then, though, that does not explain why kwin_wayland is making blocking calls to Xwayland, to say nothing of the security implications, the chance of completely locking the user interface. -- You are receiving this mail because: You are watching all bug changes.
