I’ve been on Cinnamon for quite a few years now, and I’ve loved just about everything about it, but when I got my Framework, things got a little rough. The odd screen size 2256x1504 looks spectacular on its own, but with 125% or 150% scaling, the fonts are magnificently crisp and things are, generally, the right size for me.
But X didn’t seem to like this much. CPU was a bit higher most of the time, and while this wasn’t much of an issue while plugged in, it added sluggishness and battery drain when I wasn’t.
Wayland was the answer, but it just wasn’t ready (for me). And so, for now, I’m trying out Ubuntu 23.10 with Gnome 45 on Wayland. Not a huge fan of snaps, but they’re working fine.
Up until now, things using Xwayland would be blurry when scaled, but after looking back in, most of the apps I stare at have made the switch to Wayland proper! Discord, Element, Firefox, Thunderbird. The list goes on. I can deal with things like Bitwarden and Cider being a little fuzzy since I just poke at them from time to time. I’m just so impressed.
The future is now!
I agree. I’ve been using Wayland for a couple of years now and it’s been pretty smooth. Had the odd bug here and there in the beginning, but the last year or so has been good.
I only have 1 thing that I really need to switch to an X11 session for and that’s 1 particular game running through Steam Proton. Sure it runs, but the performance is just abysmal for some odd reason. Started happening about a month ago after the update to kernel 6.5. But that is literally the only thing I still use X11 for at this point and it’s a new issue.
Bummer. I’ve been able to sidestep a lot of the gaming issues because my wife ended up with a PS5, and two of the main games I play are available there. Good to hear you’re having a good wayland experience, too, though! There are dozens of us! Dozens!
Found my issues seems to be related to amdgpu’s drm driver switched to FIFO (first in, first out) scheduler. If I switch back to RR (round robin) it goes back to normal. So there’s currently a discussion on the amd-drm gitlab about how to fix this issue.
