i used sway a couple years back to test and i had no issues back then. As far as i know XFCE is starting to experiment with wayland recently so its normal for bugs to appear. I would use a DE with more mature wayland integration like Plasma or Gnome. I have a laptop with Gnome and no issues whatsoever
XFCE's had mainline Wayland support since 4.20 (well, experimentally anyway) for over a year now.
I've tinkered with it, with labwc, it's pretty good. I haven't checked back in to see if they've baked in a sensible set of defaults, I had to figure out the autostart and keybinds but it was mostly straightforward. Things like right-click on the desktop to open the menu, or blanking out window title bar click actions. The autostart mechanic was just a top-to-bottom shell script with some special parsing, kinda seemed like a step backwards to the monolithic init script days, but also refreshingly simple.
This is all commentary on labwc specifically (and not on Void but hopefully it's still helpful), but it's XFCE's top recommendation and I believe the one that they're testing with, so it's likely to be the most supported moving forward.
Not really using void anymore atm, but when i did wayland worked fine for me. In particular i really like River, probably my favorite wayland compositor atm. I think i recently heard that mangowc is also in the void repo now? That's a cool project as well.
@lnklnx as far as i can tell there is not much of a difference in using wayland on void compared to like on debian or arch, but i'm not tooo far into my wayland journey, so ...
Void Linux is an independent distribution, developed entirely by volunteers.Install once, update daily. Your system will always be up-to-date.Void use runit as the init system and service supervisor. xbps is the native system package manager. https://voidlinux.org/