On Tue, Jan 9, 2018 at 6:15 PM, Germano Massullo <germano.massullo@xxxxxxxxx> wrote: > 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 > good decision. > > Some of problems I experienced: > - **very, very** frequent plasma crashes; > - **very** frequent crashes of applications, even KDE applications like > Konsole, Konversation, etc. I don't see many crashes but yes, it crashes time to time. > - Qt and Gtk applications have two different copy&paste stacks; > - virtual desktops are not working; > - mouse pointer has an insane dimension (it got bigger); Same here. > - misplaced notification popups; Same here. > - 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. Most of my issues with Plasma & Wayland are somehow related to external monitor setup. I switched from three screens to two screens setup and it's a bit better but I can see crashes when second monitor is disconnected, misplacements (krunner opens on second inactive screen). On the other hand, on single screen setup it progressed a lot and it's closer to be usable as a daily driver. To be honest, I'm really not sure how to help with Wayland - I have no idea how to debug things and a lot of issues are just some strange behavior that's difficult to explain and reproduce :(. One big missing feature is screen sharing - I already migrated a lot of folks here using Red Hat to G-S X11 session... I couldn't make Tuesday's meeting... Jaroslav > > *Some* bugreport references: > > Plasma crash: Crash in wl_proxy_create_wrapper in QtWayland after window > destruction > https://bugs.kde.org/show_bug.cgi?id=381630 > > [Wayland] Konversation crash - > QVector<KWayland::Client::ConnectionThread*>::reallocData > (this=this@entry=0x7fffde8016b0 > <KWayland::Client::ConnectionThread::Private::connections>, asize=21845 > https://bugs.kde.org/show_bug.cgi?id=387448 > > [Wayland] Konversation crash > https://bugs.kde.org/show_bug.cgi?id=386998 > > QtWaylandClient::QWaylandDisplay::exitWithError() > (this=this@entry=0x555555f294b0) at qwaylanddisplay.cpp:200 > https://bugreports.qt.io/browse/QTBUG-60170 > > [Wayland] Qt and Gtk applications have two different copy&paste stacks > https://bugs.kde.org/show_bug.cgi?id=378711 > _______________________________________________ > kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Jaroslav Řezník <jreznik@xxxxxxxxxx> Engineering Program Manager Office: +420 532 294 645 Mobile: +420 602 797 774 Red Hat, Inc. http://www.redhat.com/ _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
