Sadly, I recently had to switch back from Wayland to xorg because clients are getting so memory hungry. My eight year old gpu only has 2gb of vram, which I constantly run out of. Some part of the gfx stack should handle swapping out vram to main ram but it apparently isn't.
GNOME 50 completes the migration to Wayland, dropping X11 backend code
21–30 of 190 posts
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#22X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
x11 is in maintenance mode at this point and Gnome is not going anywhere. Gnome is used (and financed) by major distributions. Nothing new is being created with x11 and the people from freedesktop don't seen to be thrilled to maintain it. I don't think should change just for the sake of changing, but I'd start looking to migrate whatever you use that depends on x11.
The problem is that I find Wayland to be a lot buggier than x11.
For example, terminal transparency using Konsole on KDE flickers for me.
Its nearly there, but not quite. Maybe Gnome has no such issues?
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#23X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
X11 isn't going anywhere because distros will ship XWayland for a long time to ensure compatibility with existing X11-only applicatin.
xorg-server is gone from the linux desktop. Gnome and KDE use wayland shells by default, and that's what users get when they download a Debian/Ubuntu/Fedora/whatever ISO.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#24Earlier quoted context omitted.
x11 is in maintenance mode at this point and Gnome is not going anywhere. Gnome is used (and financed) by major distributions. Nothing new is being created with x11 and the people from freedesktop don't seen to be thrilled to maintain it. I don't think should change just for the sake of changing, but I'd start looking to migrate whatever you use that depends on x11.
> x11 is in maintenance mode at this point and Gnome is not going anywhere True. But does not address the fact that Wayland is a bad solution to X11's problems, and that its architecturally broken from inception.
I don't know the implementation details but I can't really complain about the state of wayland today. It used to be annoying to get working many years ago (worse because I had a nvidia gpu). But today I drive a nigthly build of niri, run it by just spawning an dbuss session and everything works. Bluetooth audio, screen sharing, fractional scaling, no tearing, no font blurring. Every utility I needed has been created and works quite nicely (e.g.: wdisplay). I can even play video games with HDR support.
I have a more stable experience with wayland today than I had with x11. Which to be fair was not only because of wayland but because desktop linux as a whole has made a lot of progress in the last years
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#25I've been using Gnome for years, but, honestly, it just isn't good: seems like it's optimized for very basic use. Something as simple as adding launcher to a panel now requires an extension.
Also Wayland has some problem on my system (Thinkpad / Intel Xe) where it randomly just goes slow, this makes it an easy choice to try things other than Gnome.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#26Earlier quoted context omitted.
Goodbye to any trace of freedom left on Linux when you combine this with proprietary graphics drivers.
I don't think I understand what you mean. Do you mean wayland is not usable with nvidia proprietary driver? I remember that being annoying but possible many year ago (with sway --my-next-gpu-wont-be-nvidia thingy). But if you use really old nvidia gpu you can have a mixed experience with wayland. Which is a fair problem to complain, but you can't blame that on wayland and call that lack of freedom. That problem was c…
The “what’s the harm” here is the systemd conversation all over again basically. If you pipe everything through a single point of failure black box users have already lost, when you combine it binary blob drivers that shouldn’t exist it’s worse. Linux is doomed in achieving its most important goals which are user freedom, not someone’s idea of pretty UI imposed at the expense of that. If that’s what users want they should buy a Mac. If you want to get locked out of your OS for eye candy we have that.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#27X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
x11 is in maintenance mode at this point and Gnome is not going anywhere. Gnome is used (and financed) by major distributions. Nothing new is being created with x11 and the people from freedesktop don't seen to be thrilled to maintain it. I don't think should change just for the sake of changing, but I'd start looking to migrate whatever you use that depends on x11.
And wayland is in broken mode. KDE keep changing the default back to wayland after each update, and every time my linux systems are broken until I switch back to x11.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#28Site is blocked by origin server in India.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#29X11 is not going anywhere. If anything it's Gnome adding another nail to its coffin
Wayland was created by X11 developers, as they decided keeping X11 going was beyond hope.
Feel free to find volunteers to fulfill their shoes.
Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code
#30Transition to Wayland opened so many user experience regressions. Many are solved today, or at least partially solved but...
There is still no possibility to have proper remote sessions when using Wayland. On any Window Manager and any distro. It's such a shitshow when you go into details. Nothing works, including third party tools (like NoMachine) and I could find no real hope for actual solutions being designed.
The best you can go with "remote session" on Wayland is viewing a desktop session that was already opened by someone directly on the computer. You can partially work around this by... setting your account to be automatically logged in with no password :D And even then it's a crippled experience.
A basic feature I used for the past 25 years and helped me to learn linux and offer safe space for others to learn it as well. To work around work computer limitations. To use your best hardware wherever and whenever you want.
I currently had to ditch both my favorite distro and WM because of that. But at least we can make screenshots nowadays, so I guess it could be worse.