it's still very much linked to the hardware

With my previous laptop, a lenovo L440 with an i3, no issue with wayland (even full wayland)
With my Dell, ryzen 7, no thumbnails in the taskbar except with a kernel 5.10, and hibernation doesn't work

both are up to date

I've tried Wayland on a couple of occasions, but it impressed me for the first time today. Running fvwm on an Xwayland server, connecting and disconnecting the TV through HDMI caused the second display to turn on and off immediately with no fuss whatsoever. No rules, no xrandr, nothing. Never seen anything like it before. Granted, it's a laptop with Intel onboard graphics, which is about as easy as it gets as far as hardware is concerned.

To run the window manager, I opened a terminal emulator with a compositor called cage (kiosk-like setup that displays a single window). Then, "DISPLAY=:1 startx -- /usr/bin/Xwayland" did all the xinitrc stuff on a new Xwayland server. Having two servers at the same time causes slight overhead, so it isn't the most elegant solution, but everything seems to be working fine except for the mouse wheel (slow).

1 members found this post helpful.

Well that link pretty much sums up my short lived experience with Wayland. I will stick to X11 for now and the foreseeable future.

Does anyone know what user configuration files Wayland might touch, or would it be best to just wipe everything that is associated with KDE Plasma in the user folder. That is quite a lot of things.

There's quite a few files that are stored in '~/.config' and '~/.local/share' that are used for Plasma and all the KDE applications so I don't know for certain if/what gets changed when starting Plasma on Wayland.

On my Dell laptop I only have an integrated Intel graphics card and that machine has no problems with switching between Plasma on X11 and Plasma on Wayland. I've never had to manually edit or remove config files there. The only thing I notice there is that the touchpad defaults to using the libinput driver on Wayland, and the synaptics driver on X11.

My two monitor desktop rig with Nvidia graphics had more issues with Wayland and I keep it running X11 for now. I recall moving the '~/.local/share/kscreen' directory to a backup location (and later removing) and redoing all my display settings through Plasma's system settings application after my screen setup got messed up. It's been a while since that experiment so I'm not sure what has changed in the meantime with Plasma.

Thanks. My Acer laptop is Intel, this desktop is Nvidia. I think I will give Wayland another shot with the laptop. I'm using it now at runlevel 4, because of this logout issue I have in runlevel 3 with X11.