Today, I decided to switch my work (KDE) laptop from Wayland back to X11. Not bad for 2 months.
It was the little bugs like:
- Dragging files between apps to open them, did nothing.
- After unlocking and the monitor was asleep, Electron apps are blurry until resized.
- When sharing the screen in Firefox, it doesn't integrate that well any more. Firefox lets me share the "Use operating system" window, which opens a portal window to actually select the screen/window. Too many clicks.
- CTRL+SHIFT dragging didn't create the symlink as it should, it copied files.
- Menu rolling (click & hold over menus) didn't work in GTK apps, unless I used
GDK_BACKEND=x11. - My Git GUI client crashed with autocompletion pops up (Qt bug?), so ironically,
QT_QPA_PLATFORM=xcbto use X11 backend. Sometimes the window misplaced itself, depending where I started the app.
I'm happy to trade these nibbles for one bigger X11 (AMD?) bug affecting that machine: When locked, there is a chance the fans spin up because the compositor goes haywire with CPU. The workaround is to restart or stop the compositor - sounds good to me!
Granted, some/most of these are compositor (KWin) bugs. I'm sure they'll get fixed with time.
I haven't tried Wayland on other desktops (well, maybe briefly on Ubuntu/GNOME, but not serious work) so I am curious how things will pan out when MATE gains support. Rather then X11 being the thing everyone has in common, it's now largely the compositor's role to take care of this stuff.
Also: a link back to the original topic and a new x11-wayland tag to track this stuff!