CachyOS is basically ‘Arch for people who can’t be arsed fettling about with Arch’ in my view, I really like it coming from mostly various ubuntu-likes. I chose it for the AM5 build I did last summer on basically those grounds, plus the fact it’s more tilted towards modern hardware in terms of the default packages.
It’s less ‘one of the only ways to get HDR to work’ and more ‘less arsing about because Cachy has sensible defaults for most of its use-cases’ I think, CachyOS really is good out of the box and requires minimal fettling. A lot of distros ship packages from basically the dark ages too, for example if you’re on say an Ubuntu LTS you’ll be stuck on Plasma 5. There is a tradeoff with the rolling release model in that things can break, but in my experience the occasional minor burn from this outweighs the risk of having old versions of packages.
Just a heads up if you’re a new-ish CachyOS user I’m sure you’ve been told already but treat anything coming from the AUR as untrustworthy unless you know what you’re doing with respect to that particular package. It’s not vetted like the system repos are, so caveat emptor.
Why is GNOME and KDE against X11 in this meme? Did they announce they are going to drop support for X11?
I’m surprised there are so many comments about the user experience for Wayland and X11. Unless you are programming for Wayland and X11, or are doing a lot of remote connection, you will not be able to tell much of a difference between the compositors other than package support differences. Im glad that there is an effort to move away from the X11, working with xlib is pretty archaic.
Im glad that there is an effort to move away from the X11, working with xlib is pretty archaic.
I find working with xlib to be simpler and easier for creating window managers than libwayland-client imo.
Tbh, I haven’t used libwayland-client enough to confidently put it ahead of xlib, but xlib holds a lot of quirks and window requests are not straightforward, especially if you need to keep track of windows and verify changes made to them. There isn’t a full proof way of verifying windows requests as ConfigureNotify events are detached from window change requests. Also XGetImage internally allocating memory was a pretty annoying quirk, I know XGetSubimage fixes this problem, but XGetImage allocating its own memory is unnecessary in the first place. I think this is all very much intertwined with the design philosophy back when they first designed X11, from what I’ve seen Wayland and it’s libraries don’t have them same problems. Maybe if you or someone else has found similar bugs when attempting more complex projects with Wayland lib and can comment on this?
Is there a single, unified product that I can use for remote desktop access to Linux running either X11 or Wayland, Windows, and MacOS? I provide support for family that are both Windows and Mac users (and one Linux user, yay!). I’d like a single remote desktop solution for everything that is easy to get Windows users and MacOS users to install. I’ve been using AnyDesk, because ninite.com has an installer for it, so it’s a low bar for low-skilled windows users, and it’s easy enought to get installed on MacOS. But incoming Anydesk connections don’t work on Wayland. Does Rustdesk handle incoming Wayland connections these days?
Just try it. Rustdesk works really well, but I haven’t tried it on Wayland. If you already have a wayland machine, it won’t do harm to try.
I have tried it in the past. It was great but I could only connect to running wayland sessions. It wouldn’t handle the login screen. Also the public server performance was pretty spotty, but I could always self-host the server.
I just use it in an already logged in desktop session on x11, so I have never felt a difference in terms of servers or used login functionality
I’m on Wayland (KDE), Rustdesk works beautifully. No complaints.
The problem I remember having was getting login screen access on a wayland remote machine. I could attach to a running session, but couldn’t log in to a new one. If they’ve fixed that, awesome!
Are you self-hosting a Rustdesk server, I remember the performance of the public server to be pretty spotty.
X11 really needs to be put down. Its had its time
Unless there’s a replacement without losing functionality, it’s going to be hard. I waited years for the switch to let wayland be ready. I thought it was when kde defaulted to Wayland, but nope. Once every month I run into issues related to Wayland. Or I run into not being able to implement certain things in Wayland that were super easy in x11.
I mean yes we could force the transition, but for many people maintaining their workflow and features are important. That said, I would want new applicationd snd libraries to support Wayland.
Just give it another 10 years and a few hundred thousand dollars of budget and it’ll be finally good (it won’t)
I can’t get by without xdotool. Wayland intentionally breaks this and calls it security.
What deficiencies does ydotool have for your workflow?
It’s abandoned it’s GitHub page talks about rewriting in JavaScript in 2024. X actually gets security updates.
Sending keys to non-active windows without activating them.
It looks like ydotool also needs root, and has weird interactions with non-qwerty keyboard layouts.
I’ve also been using Autokey lately which has similar blockers with Wayland.
I switched from autokey to espanso when kde/Wayland forced me to abandon X, I gotta say I really like espanso now.
Make amazing things that can’t be replicated on X. Notably the list of things people think only works on Wayland is long and wrong. Right now there is a vibrant window manager ecosystem and HDR.
Alternatively wait until new versions of basic apps no longer work on X. Although it would be hilarious if we got a comparability layer to run wayland apps on x
except at the faa
I love and use Wayland and KDE but MAN my best remote tool still hates wayland.
Wayland still lacking adoption and functionality for basic and essential needs after more 15 years and with such budgets, really speaks volumes about it’s architecture and decisions.
VMware Player still can’t copy and paste properly between the two machines on Wayland. How on earth is that affected by the desktop compositor?
One problem here lies within the architecture of wayland that it forces every DE/WM to implement their own compositing and many other things. So more and more fragmentation and harder for both WM developers and app developers.
Wayland still lacking adoption and functionality for basic and essential needs after more 15 years and with such budgets, really speaks volumes about it’s architecture and decisions.
In 2012 I had a job that centralized all of its email communications to a server in the closet. Instead of installing apps, the IT department used X11 forwarding, on Windows desktops, to open remote Thunderbird on everyone’s machine. The linux box ran postfix, dovecot, maildir and thunderbird all in one. It did not work well lol
How can you miss Cosmic, written in Rust by system76 guys? It’s the most modern desktop there is for Linux.
Not as full featured as plasma but it’s matching Gnome for sure.
i thought compiz fusion is the most modern
Cosmic is going to be the OS to have… In a few more years. It’s just quite under baked at the moment.
Too bad Wayland is glacially slow when taking screenshots next to X11 (Had a python script taking screenshots of a Minecraft window and doing some image recognition at 60 fps on X11 and …3 on Wayland. I now need to rewrite it to stream the whole desktop as a webcam for the same thing.)
My uneducated guess is maybe it should be written in C instead of python. On top of that, screen recording via OBS works great on Wayland, so Wayland can’t be fully to blame.
At least part of that is complete nonsense. Python often already does low level things in c and it was doing 60 fps under X so python is unlikely to be the bottleneck. You would need to profile it to determine the actual bottleneck.
Maybe this isn’t the right place to ask, but does anyone know why Wayland just started shitting the bed whenever I have multiple monitors connected aftera kennel update a couple weeks ago? I’m running Debian trixie with KDE Plasma and using the latest NVIDIA proprietary driver with a RTX 3050.
One of the few problems with Wayland is that multiple monitors never really work, Atleast for me.
I switched to Linux roughly two years ago from Windows and I have absolutely no idea what all these comments are talking about. CachyOS and everything that I need just works. In fact, one of reasons I ended up on Cachy was because at the time, with my very limited understanding, it was one of the only ways I could get HDR to work.