Live data from Hacker News

GNOME 50 completes the migration to Wayland, dropping X11 backend code

linuxiac.com

121–130 of 190 posts

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#121

I haven’t booted into an X11 environment in maybe 4 years. Wayland has been fine (Fedora + Gnome, Fedora / Arch + Niri). I think this is one of those issues where hardcore users overestimate how much anyone else cares or will notice.

Mouse warping does not work in XWayland. Thus, I still use X11.

David (UI details) beats Goliath.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#122

I haven’t booted into an X11 environment in maybe 4 years. Wayland has been fine (Fedora + Gnome, Fedora / Arch + Niri). I think this is one of those issues where hardcore users overestimate how much anyone else cares or will notice.

Wayland is buggy as hell for me. Im not particularly invested in X11 but at least it works.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#123
post #117

One of the big problem I am/was facing with Wayland is the performance when accessing a VM with SPICE and virt-viewer. You basically had to use X11 on the host and the guest for everything to work in an optimal way. Do anybody knows if any progress have been made on this front?

SPICE is slowly being phased out by Redhat, so I'm doubtful we'll see improvements on that front any time soon.

That would be a bummer !

And with X11 support gone we would have to downgrade to VNC to access our VMs?

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#124
post #71

Earlier quoted context omitted.

X11 is far more stable now since they stopped improving it! I haven't had a crash in 15 years.

Hardware-accelerated x11 is buggier than software-accelerated Quartz Compositor, on my machine.

Reality might hit me in the face if I ever get a new machine, but my 13 year old laptop works flawlessly.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#125
post #75
post #70

Earlier quoted context omitted.

I used X when I started with Linux in my high school. When I finally stopped tolerating macOS almost a decade ago, I started with Wayland only, and never looked back. I even ditched Krita in favour of Gimp, solely because Gimp supports Wayland (from version 3, and on 2.99 before that). To this day, I don’t understand X, like at all. It’s all some super complicated pile to me. While I don’t understand Wayland either,…

Remember x11 was initially a client server model, where multiple clients could access a single x11 server. This brought a lot of complexity we don’t use these days

Speak for yourself. I use it every day.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#126

I haven’t booted into an X11 environment in maybe 4 years. Wayland has been fine (Fedora + Gnome, Fedora / Arch + Niri). I think this is one of those issues where hardcore users overestimate how much anyone else cares or will notice.

Wayland is buggy as hell for me. Im not particularly invested in X11 but at least it works.

Nvidia GPU? Their drivers have been broken on Linux for a long time now. I've had no bugs on my steam deck or on asahi linux with wayland.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#127
post #101

Earlier quoted context omitted.

Have you actually tried setting it up on Wayland yourself? Please do. I've seen too many threads like this based on a hunch and docs, while it just doesn't work. I'll be more than happy to be proven wrong.

I've used it. It works fine. You connect with RDP, get a gdm login screen, and can log in.

Thank you, I will definitely test it soon.

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#128

I was working on a carousel library a few months ago. I had made a few stress-test demos so that I could catch obvious issues while I was adding things and tweaking things. One carousel there had 16K slides. On Windows both Chrome and Firefox managed that fine. They scrolled from start to end and back without issue and you could see, I think, all the frames in my 60Hz screen. On GNOME and X11 (dual boot, so same hard…

Firefox remains very conservative on enabling modern features on X11. Some distributions force them on, but otherwise it's up to the user to figure out how to do that.

It's likely that some hwaccel flag in about:config wasn't turned on by default. Similarly, if you want smooth touchpad scrolling, you need to set MOZ_USE_XINPUT2

Re: GNOME 50 completes the migration to Wayland, dropping X11 backend code

#130
post #2

I was mostly surprised by the "Gnome 50" part. Last I remembered Gnome was still version 3. Turns out they jumped from 3.38 to version 40

> I was mostly surprised by the "Gnome 50" part. Last I remembered Gnome was still version 3. Turns out they jumped from 3.38 to version 40

I think GTK is version 5, so they have to converge somewhere.

This is an old trick from SW developers to show a suppose maturity: bump the version number.

Post reply on HN