Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

linuxiac.com

Post reply on HN
Print view View original

181–190 of 190 posts

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

#181

Post by jjav »

woleium wrote: post #75
wltr wrote: 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

That's the whole point and I sure use it every day.

Starting a GUI app on any machine on the network and have its windows display on my local screen is vital functionality.

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

#184

Post by aki237 »

I have no idea what issues folks are talking about. I use vanilla gnome for my work and personal use case (given with well supported GPUs, read: no Nvidia). All the features work. Zoom/screen share/obs etc.,

Multi touch gestures work on laptops as smoothly as they were on a mac. HDR has started working recently even in my browser. VRR has been working for almost a couple of years.

It doesn't break, most mem leaks that gnome was known for all gone. Almost all the cli X specific tools I use (mostly clipboard stuff) are all available. Initially when I switched I did see like a 10~15% increase in battery usage albeit being smooth.

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

#185

Post by killerstorm »

ginalloa wrote: post #97
killerstorm wrote: post #25

I'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.

As discussed earlier on HN, KDE these days has been the most usable desktop for many users. It is mostly stable, feature rich and can be customized easily.

Alright, I tried KDE again - and it's really good. Seems like Chrome-in-Wayland problem I had before is resolved now. And otherwise KDE accumulated all the goodies one should expect from DE over years.

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

#186

Post by vrighter »

ahartmetz wrote: post #168
tcbawo wrote: post #92

Earlier quoted context omitted.

For certain jobs, I've done development for Linux while also having a Windows box for other things. Opening Linux GUI apps remotely on my Windows desktop is nice and allows me to consolidate my displays. This is an edge case, for sure. How well does Wayland support this?

AFAIK it's more or less still being worked on. Since Wayland has no support in the core protocol, it's an add-on which needs the compositor to forward input and output streams and then something to compress the video and forward it (+input events) further over the network. I can't say that I got it to work so far, though screen sharing in MS Teams(!) running in MS Edge for Linux does work and uses much of the same fu…

Anything not in the core protocol might as well not exist. It is literally, by design, impossible to write a fully featured desktop using the core protocols by themselves.

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

#187

Post by vrighter »

coldtea wrote: post #159
erelong wrote: post #116

I'm curious to what extent things in this article have been fixed: "Think twice before abandoning X11. Wayland breaks everything!" https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d... In my experience Wayland always had problems, so depending on how XWayland works, I'd probably have to drop Gnome if there's no X11 support that's functional and I imagine a lot of others would need to do so (until X11 suppor…

Most of the arguments sound irrelevant: > Wayland breaks everything! It is binary incompatible, provides no clear transition path with 1:1 replacements for everything in X11, and is even philosophically incompatible with X11 Being binary compatible is a moot point, 1:1 replacement for "everything in X11" are not an issue if the subset you need works or has good replacements, and being "philosophically incompatible" i…

yes but it's no good to me if wayland supports the subset of functionality that you use but not the subset that I need.

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

#188

Post by charlsysaysbase »

szszrk wrote: post #30

Transition 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. Th…

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

Gnome has had remote desktop sharing I think since 46.

Settings --> System --> Remote Desktop

The "desktop sharing" tab is for setting credentials to share your logged in screen.

The "Remote Login" tab is for setting credentials to access GDM and login as any user (i.e. headless).

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

#189

Post by charlsysaysbase »

szszrk wrote: post #101
yjftsjthsd-h wrote: post #98

Earlier quoted context omitted.

I don't use GNOME, or GDM, or RDP, but isn't https://gitlab.gnome.org/GNOME/gnome-remote-desktop#headless... describing that? > GNOME Remote Desktop supports integrating with the GNOME Display Manager (GDM) to achieve remote login functionality. This feature is only available via the RDP protocol. It works by the remote user first authenticating via a system wide password, which gives access to the graphical login sc…

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.

> Have you actually tried setting it up on Wayland yourself?

I use it very regularly. Particularly the headless part (where nobody is logged in physically, just a remote session).

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

#190

Post by irthomasthomas »

ColonelPhantom wrote: post #31
irthomasthomas wrote: post #27

Earlier quoted context omitted.

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.

What is broken for you? At this point, starting from roughly KDE 6, Wayland has been pretty much flawless for me. KDE 5.27 was pretty much fine already as well.

Just installed fresh and logged in to Wayland. Sudo password stopped working. After fixing that it kept opening some window and refused to close. Even without those bugs none of the accessibility tools work.
Post reply on HN