What is your experience with Wayland on Void?

5 months ago by lnklnx to c/voidlinux

I'm (slowly) starting to migrate all my systems from Debian to Void. I'm not passionate about Wayland per se, but I understand it is where future development will be going so I'd like to move in that direction. But I'm having hit-or-miss luck getting going.

In practice, I'm still on X11 in most cases because that works out of the box, whereas Wayland XFCE sessions just die and fall back to lightdm.

Fellow Void-users, are you running Wayland? If so, is it working well for you?

ale 3 points 5 months ago

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

save

path: 0 23874796, hotness: undefined, score: 3, children: 1

caseyweederman 2 points 5 months ago

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.

save

path: 0 23874796 23902933, hotness: undefined, score: 2, children: 0

torsten 2 points 5 months ago

@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 ...

save

path: 0 23864048, hotness: undefined, score: 2, children: 0

juipeltje 2 points 5 months ago

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.

save

path: 0 23861396, hotness: undefined, score: 2, children: 0

wesker 2 points 5 months ago

Yes, no issues. Mango window manager/compositor, spawned from greetd > tuigreet using dbus-run-session. xorg-server-wayland ensures pretty good compatibility with random X programs I may use.

save

path: 0 23989806, hotness: undefined, score: 2, children: 0

fozid 2 points 2 months ago

Hi, yeah, I moved from arch Linux to void a while back and not had any real significant issues with Wayland. Although I was on Wayland on arch to. I moved to Wayland 2 years ago in arch, then moved to void 6 months ago. I've always been minimal in terms of desktops though. Haven't run a full de on my main pc in over 10 years. I was openbox on x11, then when I moved to Wayland, tried hyprland for a few weeks before settling on sway. I have had to adapt as x11 is not Wayland. But I haven't had any breaking issues. I don't use a DM either.

save

path: 0 25170862, hotness: undefined, score: 2, children: 0

ajar 1 point 4 months ago

For four years, swaywm with void was my daily driver. No problem at all. I was even using nvidia gpu.

save

path: 0 24346831, hotness: undefined, score: 1, children: 0

Haydar 1 point 5 months ago

@lnklnx #Wayland / #Sway on #Void requires some work, especially when you want things like screen sharing or waypipe to work.
Yesterday suddenly foot terminal had an odd font, because Void introduced a fontconfig rule which prohibited the terminus font to load.

save

path: 0 23888148, hotness: undefined, score: 1, children: 0