> arewewaylandyet is a good starting point
Annoyingly, they're out of date and ignore PRs, so not the best source of info.
An X11 apologist tries Wayland
191–200 of 453 posts
Re: An X11 apologist tries Wayland
#192Earlier quoted context omitted.
Nomachine's server and client are closed-source but work great. For open-source solution for quickly remoting into an existing display, I use freerdp-shadow-cli which is way more stable than x11vnc and uses the RDP protocol instead.
Nomachine used to be open source. X2Go is the open source continuation of that.
I think their current version is unrelated to what is now x2go
Re: An X11 apologist tries Wayland
#193TL;DR of comments
X works 6 out of 7 days of the week.
Wayland works 4-5 days of the week.
My 2c I still use X/i3 most things works without too much fiddle, whenever i try wayland less stuff works.
Re: An X11 apologist tries Wayland
#194The thing I dislike about Wayland is: Sometimes the server will crash. Video drivers or something. Hasn't happened much with 22.04, but used to happen more frequently before. Both with Intel and AMD. When this happens in X11, the server restarts, I see the screen go black for an instant, that's it. When this happens in Wayland, all my open programs are killed. No save prompts or anything, just insta-killed. This make…
If you have a GPU hang and reset, X11 isn't going to be any better. There is some WIP to make recovery from GPU hangs more robust. It's not there yet.
* https://www.youtube.com/watch?v=fRdnRwPBFBk
* https://invent.kde.org/plasma/kwin/-/wikis/Restarting
Though I'm not sure what's the current status of that is or how actively it's progressing. Hopefully it will turn into something usable, it's important.
Re: An X11 apologist tries Wayland
#195I've tried to use Sway a number of times, and the biggest reason I keep bouncing off it is environment variables. There's a bunch of environment variables I want set for every process in my desktop session, from basic things like $EDITOR and $LD_LIBRARY_PATH to more complex things like $MOZ_USE_XINPUT2 or $SSH_AUTH_SOCK. When I use i3 under X11, gdm runs my ~/.profile script so I get all my standard login environment…
Somehow all that works fine in KDE with Wayland. So may be it's a problem with Sway.
See also: https://invent.kde.org/plasma/plasma-workspace/-/wikis/Plasm...
Re: An X11 apologist tries Wayland
#196I've tried to use Sway a number of times, and the biggest reason I keep bouncing off it is environment variables. There's a bunch of environment variables I want set for every process in my desktop session, from basic things like $EDITOR and $LD_LIBRARY_PATH to more complex things like $MOZ_USE_XINPUT2 or $SSH_AUTH_SOCK. When I use i3 under X11, gdm runs my ~/.profile script so I get all my standard login environment…
This is not really a wayland or sway problem, but really a systemd problem. It's really annoying because the documentation around this is very scattered and contradictory. The advice used to be that you should use pam user environment (~/.environment and you need to edit pam configuration on some distributions to allow user environments). However, IIRC there are some possible security implications around this so this…
Yeah, I can create files in ~/.config/environment.d/ to set some environment variables. My problems are that (a) that syntax only allows very simple variable assignments, not complex things like "run ssh-agent and add the environment variables it prints to stdout" and (b) those environment variables aren't available to the Wayland compositor or applications it launches.
Re: An X11 apologist tries Wayland
#197Earlier quoted context omitted.
> While on the road, you can use your notebook to open a Gimp session on your home machine and edit an image stored there. That is, the Gimp runs on your home machine while your notebook has the GUI. But that's never where I want the split to be when working across the network. Remote storage? Sure, sign me up. (The POSIX APIs are horribly unsuitable for network filesystems, but I'm speaking about the concept more th…
I never had to do it myself, but I have a feeling it will work better with Wayland. The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota), so if your software doesn't lag itself, like X11 did, maybe it will work. You could also use something like Zerotier-one to recover from network being shortly disrupted. This service connects your machines into a virt…
> The delay of 50-80ms introduced by the network is not terribly much (everything under 110ms is fine for playing Dota)
I don't think you're giving the Dota client enough credit there. Game clients don't wait for network to pretend to respond to user input, because it absolutely is noticeable at 100ms latency. Instead, they predict as much as they can client side and display it as fast as possible. For this reason, the client is not at all thin. It knows how to run the whole program by itself. Not so with remote X11. With remote X programs, the client doesn't know what happens on click for anything, so the user really does get hit with a 100ms delay for every interaction with the program.
Re: An X11 apologist tries Wayland
#198I've tried to use Sway a number of times, and the biggest reason I keep bouncing off it is environment variables. There's a bunch of environment variables I want set for every process in my desktop session, from basic things like $EDITOR and $LD_LIBRARY_PATH to more complex things like $MOZ_USE_XINPUT2 or $SSH_AUTH_SOCK. When I use i3 under X11, gdm runs my ~/.profile script so I get all my standard login environment…
When you 'exec sway' it inherits the tty env vars... So just stuff your vars into whatever .profile the tty loads when you login after boot. This has never been a problem I spent any amount of time on. If you are doing something magical like auto starting sway or something, then you need to make sure that a .profile is loaded by whatever is starting sway if it doesn't inherit a .profile.
In addition to the reply, he mentions gdm so he likely doesn't login from the console. This is a bit extreme but one day they might (for security reasons) remove that too.
Re: An X11 apologist tries Wayland
#199From https://wiki.ubuntu.com/Wayland "The X11 protocol was designed around running graphical apps across the network. While some people use this feature, it's far from common. Wayland drops this requirement as a way to greatly simplify its architecture." X client and server are usually the same machine, but they don't have to be. While on the road, you can use your notebook to open a Gimp session on your home machine…
And any program not made with goddamn XMotif will be slow as fuck on anything non-ethernet.
It is a strictly worse solution to remote desktoping than what followed it — we are no longer drawing things with CPU and the things we draw are not 3 rectangles. A bitmap crossing the wire for an icon/image/whatever is insanely inefficient through the X protocol, you want to compress it with a modern compression algorithm for much better outcome.
Re: An X11 apologist tries Wayland
#200I recently tried switching to Linux with a few different distro's (Ubuntu, Elementary OS, etc.) and use Wayland. The thing that sticks out like a sore thumb to me, and which I've been unable to solve, is that apparently it's not possible to configure trackpad scroll speed. At all. From what I was able to gather, Wayland/libinput say they shouldn't be responsible for handling it and instead window managers should[0][1…
I’m puzzled by your comment because I observe precisely the opposite: in Sway (Wayland) I have `input * scroll_factor 0.35`, but in i3 (X) I can’t reduce the scroll speed.