Let me guess… You have an Nvidia card.
Guilty as charged
Didn’t they straighten out Wayland support? I thought this was a thing of the past as of 555, but I also haven’t run Nvidia myself in years and years.
My work PC has a 3080 and the latest
nvidia-dkmsin the Arch repo. I haven’t had a single display-related issue for probably a year.With the same setup I had constant issues with Variable Refresh Rate, monitor sleep and actual sleep…
Nvidia on Linux did not want to work well for me
I had an NVIDIA card when I switched to Linux about two and a half years ago and I’ve never had an issue AFAIK.
So you are living in an illusion of choice, while your options are obviously determined by the big corpo that you relied on for getting that card
(Saying that, I got an NVIDIA card like a dumbass too)
…more like a gifted old laptop, but yeah.
Protip: People who have iGPU + nvidia can just set the iGPU as main GPU on the BIOS and offload 3D programs to the nvidia via prime-run like they would on a laptop.
That’s my setup.
I’m represented, but run AMD on desktop and Intel on laptop.
Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that’s had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.
It’s fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.
Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.
No KMag + KDE Connect remote input, no Wayland.
I use KDE Connect remote input on Wayland all the time…
KMag is broken (simply has not been updated, not like it couldn’t work) but you can zoom the entire screen in KDE with super +/- is that not good enough?
I honestly don’t know where people are getting these Wayland issues. I’m on EndeavorOS with an RTX 3080ti and multiple monitors and it has worked flawlessly for ~2 years now.
There’s probably a lot of people on ‘stable’ distros who are still running Wayland code from a couple of years ago and hitting bugs that have been fixed already.
same
i ran arch with 2 monitors with different refresh rates on a rtx2060, idk why everyone’s complaining. my screenshare issues were my fault or i didn’t update vesktop which i can’t fault due to it being like a “pirate” client for discord.
so what’s everyone’s issue with wayland?
KDE on Wayland has only very recently started to become workable for me, before that it was utter crap as I switch between home and office with my laptop, with varying display setups. In that case you got stuff like screen positions not being remembered and applications consistently starting off screen, requiring gymnastics to coax them onto a display.
And regularly it would crap out and not show output to one of the displays, if you opened up display manager you’d see the displays not touching and a big red error telling you that gaps betweens displays aren’t supported. Well here’s a brilliant idea, how about not automatically putting a gap between them in that case?
As I said, last few months it works better (although I still encounter some issues from time to time that I never had on X11). But the whole Wayland protocol had such a rough start, with issues encountered often being downplayed by parts of the community because “it’s better and we don’t want to hear otherwise”, that I simply cannot feel any love for it anymore. There was too much basic stuff that took too long to support, while people were shouting “but HDR!”, “better code!”. I don’t fucking care, I just want to be able to work and for too long that required X11.
Edit: some typo’s and improved readability.
On my old nvidia laptop with Endeavouros i have some minor lag from time to time, nothing too crazy. But there are a couple of things i can’t make work. For start i can’t lower the gamma with xrandr, wlr-randr should work but my nvidia give me the middle finger. Secondly i can’t, for the love of me, find a decent onscreen keyboard app to use. I can technically enable the touchscreen keyboard in my desktop adding
KWIN_IM_SHOW_ALWAYS=1but is just too bothersome to have it pop-out everywhere. Also, while most of the app-images works, last time i’ve tried running this one https://github.com/ryzendew/Linux-Affinity-Installer it crashed 9 times out of 10. All of this works just fine on x11.
I wish Wayland would do basic shit like save my window positions for multi-screens. I hate having to set that up every time I reboot.
So what’s not working in wayland? Screenshots? Remote desktop? Screen recording? Display in general?
I feel like a lot of people tried Wayland in 2020, a bunch of things didn’t work and they’ve been permanently traumatised.
I switched my laptop years ago, but my desktop only fairly recently - multi screen, mixed DPI with variable refresh rates for gaming took longer to be ready than my laptop’s single screen, normal DPI, fixed refresh rate config.
It works sometimes, but when it doesn’t, it wastes way too much time. I just switch back to windows for 50% of the time for anything productive. I love configuring hyprland, but actually using it for anything that needs to do something sucks. Thank god for arch linux wiki. I can run some apps instead of going to windows. Can’t run vm either🫠
deleted by creator
I can confirm that the default remote desktop on Ubuntu 25.1 doesn’t work at least.
deleted by creator
What’s it with the Wayland hate?
X did a great job for decades but it’s old, it never was designed for modern day requirements, let it retire gracefully instead of dumping on it’s replacement, maybe?
I understand there are some apps that still require X, those at some point will be / should be / have to be updated, but I don’t see that as a reason not to want to move forward to something better
Some people just can’t find a better hill to die on it seems.
The issue with wayland is that both the process and the base mechanisms had significqnt flaws, that made it take a long time to get things working. In all fairness, the core team uad a valiant effort for a dwcade, hampered by unresponsive complainers, and late-to-the-party suggestions.
Fyi: I am an early WL adopter, but not on any of the major DEs.
tbf to this thread, wayland wasn’t really viable until 2023.
I made an existing comment on this that people didn’t like because I pointed out that most of Wayland’s “modern upgrades” like VRR, HDR, etc were unimplemented or unfinished for years. Even HDR is still “beta” on KDE iirc.
People also like to pretend the triple buffer wasn’t a can of worms for many users for a very long time (and still is on low power devices).
Even HDR is still “beta” on KDE iirc.
That’s a weird comparison because HDR is never going to happen on X.org (nor probably in the X11 protocol or clients). Wayland is being actively developed and the developers took it from something that can be made to work with some effort and some concessions to something that will reliably work in most cases. The year isn’t 1987 – software isn’t being written by nerds for nerds who can tinker and fix issues or add new features as a patchwork of unmaintainable code.
So I recently updated pop from 22.04 to 24.04. The only real headache I’ve had is running games through proton. Games now start in windows, which might not even show up at all until I super + F11 to full screen it. The mouse gets stuck in either a corner or the middle, sometimes the cursor works in the menus but stops working on the game itself. Gamescope can fix some of these issues, but alt-tabbing is always an adventure if it breaks the game or not.
An annoying thing is it is very hard to figure out where an issue lies. Is it wayland, is it Cosmic, is it gamescope, or proton? Any tips or tricks people might have would be appreciated.
It’s a shame, because I want to like Wayland. i don’t know what magic system 76 worked in x11 but the only issue I had before was some tearing when moving windows around. 2 monitors of different resolution and framerate with nvidia.
Man I thought it was about the new European twitter concurrent. The replies did make no sense for a while 😅
kde, hyprland and mangowc are working without issues for me on cachyos with gtx1660
Cinnamon user here. I wish I could use Wayland. ;_;
I can’t believe that these arguments never mention one of the central tenets of engineering: don’t fix what ain’t broke. And Wayland breaks a bunch of what ain’t broke.
Yeah it’s newer etc. people don’t care.
X was broken as fuck and held together by duct tape and zip ties, as long as no one looked at it wrong.
That’s great, now run birdtray.
The shit that relied on it to run, do not work correctly on wayland. Breaking existing shit is what I’m talking about.
It’s a…mail notification??
You’re complaining that Wayland sucks cause it isn’t backwards compatible with your favorite desktop widget?
OK.I’m complaining it sucks because it breaks “things”.
Also, it’s a “desktop widget”, so this awesome thing that’s so much better should be able to handle compatibility for a simple desktop widget and not keel over and die, right?
Don’t fix what isn’t broken, don’t break what is working.
X is broken in many different ways. It has a huge codebase made to support a poor design that was optimized for machines 40 years ago. No one wants to touch the code base since it is so incredibly fragile plus the original developers are much older now.
In all fairness, it did work for way longer than anyone expected. I doubt the original designers of the X protocol anticipated it lasting this long.
@possiblylinux127 @Skullgrid protocol itself is mostly OK. Yes, it have many limitations, but it covers much more desktop needs than wayland/mir/surfaceflinger/etc.
But implementation is really broken.
For example, the way how some extensions override vtable is terrible: overriding functions usually should restore base function in vtable before calling it and and restore back after. Breaking this would break call chain and override function will never be called again.
I think, this is a reason why devs switched to wayland. Nobody want to reimplement x11 from scratch, but exisiting implementation is borkedHow much do you k ow about computer graphics and X? The protocol is indeed not ok. It has tons of hacks and is incredibly janky. Doing basic graphics with X is so incredibly awful as you need to jump though tons of hoops.
That that completely ignores the security issues.
