I started working on Flyaway with the intention of becoming familiar with Wayland, its protocols and extensions, and the wlroots library. Instead, I ended up genuinely liking all three.
What I’m missing from wayland, it’s not really something from wayland itself. Examples are several needed electron based applications, which some will refuse to properly work (for meetings, desktop sharing, etc), wine, gtk4 applications not respecting GDK_DPI_SCALE (not sure if already addressed) when not using gnome (wayfire being used as compositor), no proper support for conky (or eventually equivalent wayland functionality) yet, and several nuances with waybar, and some other tools. Major issue is my work dependency over some non floss electron binary blobs, like teams, slack, and so on, which particularly for desktop sharing and meetings don’t yet work properly, no matter the electron options one can use for them, and some floss I use like signal, freetube, jitsi. Wine has a horrible hack, which I might live with, but it’s horrible…
So I’ll have to wait further for non wayland stuff to truly support wayland, and it has taken ages for that to happen, :(
I haven’t tried labwc, andit sounds interesting, though I don’t like openbox configs, and I really love fluxbox ways, which are also text files, but I never got used to openbox configs, perhaps just because I got way too familiar with fluxbox, which is what I use with Xorg (fluxbox + picom + tint2 + conky).
GTK does not use env vars for configuration, those are for development. There are some GSettings that control scaling like
org.gnome.desktop.interface text-scaling-factor
.Screen sharing also works once apps catch up.
The env var works fine on Xorg though. And yeap, several applications need to catch up. That’s what I meant when I said it’s not wayland fault itself. However it’s been years things have been trying to catch up. Every now and then I try, but a couple of months back I couldn’t routinely use wayland, given all missing functionality plus additional nuances… The hard part is that if not using gnome, or plasma for that matter, getting things working take a lot of time, just to find out some things, I depend on for work, don’t work yet. At any rate, I still pay attention as well, to forums like this, to see if there’s some news that might trigger another retrial…
Anyone have a nice “Will Wayland work and how to switch” guide? I haven’t used it ever, but the time will come soon enough.
There’s https://arewewaylandyet.com/
I love those “are we (thing) yet” sites. They’re amazingly helpful.
Now that is useful. I see that I might indeed wait a little longer.
What distro ?
Right now, Alpine. I’ve gone over the Wiki and don’t need to switch any time soon. It is more to have something bookmarked for later.
What feature is holding you back?
I didn’t have an opinion on this until I tried to disable right click on a ubuntu machine with Wayland. It needs an xmodmap style tool.
That’s not a common thing people do tho
True but it’s something that can easily be done in xorg because it has almost 20 years worth of tools created for it.
True. But Wayland will get there too, it just takes time.
Yeah but by that time people will be posting ‘relationship ended with Wayland, (next thing) is my new best friend.’
switched to sway on pinephone and main computer, and will never go back to xorg (i hope!)
so Budgie guys doing some work :)
Vamos
It’d be pretty cool if they implemented HDR soon, my debian Kodi box can’t display HDR movies correct on my TV.
Can’t be that good. I did a kde archinstall on a friends desktop just last week, 2070super with proprietary drivers, and wayland crashes on login. T_T
I’ve been using wayland for years but I’m running AMD.
Well yea it doesn’t work on Nvidia very well
The linux desktop experience in current day is honestly incredible to use. as long as you keep team green as far away from your hardware as possible. Not worth the headache to deal with Nvidia in my personal experience
Can Wayland tunnel through ssh?
Ya since I also run xwayland :P