I am not in KDE SIG, but as person who has been testing Plasma on
Wayland since many months, my opinion is that Plasma is not ready at all
for Wayland as default option. The concrete risk is that this decision
will push a lot of Fedora users away from Fedora KDE Spin, seriously.
Forcing Wayland as default session only for innovation sake, is not a
Some of problems I experienced:
- **very, very** frequent plasma crashes;
- **very** frequent crashes of applications, even KDE applications like
Konsole, Konversation, etc.
- Qt and Gtk applications have two different copy&paste stacks;
- virtual desktops are not working;
- mouse pointer has an insane dimension (it got bigger);
- misplaced notification popups;
- sometimes when shutting down the system, the system does not poweroff,
forcing the user to unplug the power cable or use Magic Sys Req if the
user is so lucky to have it enabled. I have heard this has been fixed
but I haven't tested it yet;
- odd behaviour of various applications.
*Some* bugreport references:
Plasma crash: Crash in wl_proxy_create_wrapper in QtWayland after window
[Wayland] Konversation crash -
[Wayland] Konversation crash
(this=this@entry=0x555555f294b0) at qwaylanddisplay.cpp:200
[Wayland] Qt and Gtk applications have two different copy&paste stacks