I ended up enabling wayland on Pop!_OS when I was fussing around trying to enable adaptive sync for gaming’s sake (Variable refresh rate - ArchWiki). But it was more a proactive effort on my part to avoid the issues the wiki mentioned, and try and skate in the compatibility area (i.e. far as I know, steam deck uses KDE and wayland, and steam + proton is how most of my games run; stick with what they’re working on and testing against). Which eventually pushed me into trying Nobara (fedora-based KDE gaming distro) and later TuxedoOS (back to apt for familiarity’s sake, still KDE + wayland). Screenwise, a 240hz and a pair of 165hz screens, previously the 240 and a 60hz ultrawide. I ruined a perfectly good monitor by seeing a higher refresh rate one…
Haven’t noticed discord issues, but I don’t voice chat on there much (PTT when I do), and don’t screenshare at all. Only reason I use the flatpak app is for voice, otherwise it’s in a browser - but that was true on Windows for me as well, so… the ‘normal’ experience remained?
Depends on if you are using a Nvidia graphics card or not. I have two rigs at home, one has a Intel Arc A770 graphics card and wayland works like a dream.
On my Nvidia 3090 Rig things sort of works but requires alot of patience pluss a lot of artifacting
All in all, positive experience on the intel side, not sure about AMD
Wayland itself is generally fine, but I’m pretty sure Fedora/Gnome/Wayland is probably the most “complete” implementation in the first place. Running an X session occasionally does things I would generally rather it didn’t, leaving blackout outlines of recently closed or moved applications and general animation oddities that usually don’t happen under Wayland.
-however-, some older games that prefer to launch massively below my display resolution (NFSU comes to mind) did have some visual artifacting until I learned of the forced FSR tick box available in Bottles (and probably other wine-related setups, but that’s been generally the easiest to make work) which resolves it. This may be more of a problem with my display not necessarily playing nice with 800x600ish resolutions rather than a Wayland issue, but switching to an X session /also/ resolved it.
I also haven’t had much occasion to do terribly much screen recording outside of occasionally using the inbuilt recorder in PCSX2, which as you may expect is windowing system agnostic as it’s just recording the emulator output to file while displaying it.
sure and when i can do things like present what i need to without it flickering and garbling after it asks me three times which screen to share, and after it stops making my monitor have this stupid pwm flicker i might have the same opinion
wanting things to actually function is not a symptom of being old
I’m not in on it too much other than occasional news about distros dropping X support. I don’t have a horse in the race but I want actually live projects to be worked on instead of relics running the game. This is what Windows is, mostly things that haven’t been worked on for years.
Yea sure, it might work now, but you are missing out on the future progress. Progress breeds innovation. No matter how bad the progress/setback is, there is someone figuring out to fix it and communities uniting to get something done.
And alot of this XvWland feels like an old guard struggle using some arbitrary software that is probably going to get that patch later anyways, but still entranch themselves, because never change a running system. Well, change it for the better.
In the end, I just want audio screensharing for Wayland in Discord.
For me both Xorg and Wayland are running well on (K)Ubuntu 22.04 LTS. On (K)Ubuntu 24.04 LTS it is even better. UE4 game(s) seem run better under Wayland.
Intel CPU + Intel integrated graphics work fine.
Intel CPU + AMD Radeon RX 6800XT / AMD Radeon RX 7900 GRE work fine as well.
Sorry that came to mind. Be that as it may. Im pretty tired of nvidia. Like yea my wayland experience works with them but discord is the one that pisses me off most. What gives?
I also see Wayland running better on new and old hardware. As there is a very significant leap in new technologies that X probably does not utilise, which Wayland should.
Pleased I don’t have to make this post. I really wish not to be negative - from zero, wayland can be ok and I enormously appreciate OSS, and if X11 devs say they want to handle things differently, i’m at least prepared to listen.
But I still can’t use wayland on every device, and perhaps that’s fine. But being told e.g. ‘we’re not supporting x11 clients, we support wayland clients’ doesn’t work if what I want to run are X11 clients. (and I actually like ssh -Y thanks, so might you if you’ve ever seen cygwin present a GUI of an application running on solaris, naturally, in wrong endian colors). I wish they’d be more concerned about that.
So what do you all got (I only use amd/intel gpu’s) - each of the below mean, on one device at least, I can’t use wayland - but - on one device I keep wayland only (or at least, until I need to login X11 session to work).
Applications
Alternatives
X11
Wayland
redshift
gammastep (wlroots)
xvncserver
wayvnc (wlroots)
krfb (kde no output on monitor off, crashes excessive)
mpv
mpv
mpv.conf: gpu-context-waylandvk - for most accel; too slow on platform
desktop sharing on teams from plasma 6.1 (not electron, just pwa from chromium) results in flickering around the damage regions which appears to probably be where a kwin animation has just happened, though not always
also happens on zoom actually this part might be a lie I actually can’t remember
that incident was on a 7940u p14s gen 4 with 780m on amdgpu, although happens on my 7950x with a 6900xt
found that out after presenting to a client. at least I got to feel the embarrassment after it was over
I screen share all the time and chromium asking me over and over again what screen to share annoys me too
Something tells me the pipewire screen capture protocol implementation has some… maturing to do…
That seems to be present on Windows for me, on Firefox. I’m not entirely sure why that is. I think the browser screen capture protocols are just junk in general.
