Wile I agree that it's not Wayland's fault, I also think that people acting like X11 was obsolete yesterday and everyone should immediately stop using it simply because Wayland exists, while that is still true, are not helping the situation any

What's your hardware and distro ? I have an Nvidia card and am considering a switch next year

Cries in hardware raytracing

eurobeats intensify

In my case, windows start to flickr intensively after a while. I tried a bunch of flags and workarounds but nothing worked for me.

I use the proprietary driver, though.

Well of course you haven't had any issues you could pin specifically to NVIDIA + Wayland. Because according to your post you're specifically using Nouveau + Wayland. Be kind of strange for a driver you don't have installed to be causing you issues.

And you didn't need to point out you're an Arch user, we could tell just from the sense of superiority dripping off your comment.

RTX 2080 here, and this is the major blocker for me with Nvidia + Wayland: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1317

This issue causes XWayland apps to effectively render previous frames very sporadically, and it's especially very noticeable in Electron apps. Discord for example, sometimes someone will send a message and the message will appear, then disappear, then reappear, then disappear over and over again until it finally syncs back up. The user isn't actually deleting and resending their message of course, but the render state of the app is basically "jumping backwards through time".

Tried out the 544 beta driver, and while we did get Night Light/Color support (and that incessant top-screen flicker bug was fixed, occurred in both Wayland and X11), I started to notice the aforementioned issue heavily occurring in IntelliJ which is a Java based development tool which unfortunately is the final deal breaker for me since I can't really work when I write a line of code, and it disappears, reappears, disappears, then reappears again.

This only occurs via XWayland, and surprisingly games don't seem to get hit with it (in my case) so I suppose if you only use Wayland native apps like a web browser then it's fine - otherwise, it makes things very difficult. It also occurs on both Mutter (GNOME) and KWin (KDE) but I imagine there isn't a compositor where this doesn't happen due to what causes the actual problem in the first place.

After trying the 545 beta and the problem getting worse, it's put the nail in the coffin for me on Nvidia and I'll be picking up a 6700XT after my next paycheck comes in. It is a beta driver yes, but the root of the issue is due to the architecture of their driver which isn't going to be magically redone in between the beta and "stable" release.

So, no - I wish it was just a circlejerk, and realistically I can't see how it'd end up being this popular if it was just user error.

I'm using it presently, and aside from a few quirks in electron app rendering (slack input box flickers sometimes; things like that), it's been solid:

• Ryzen 9 3900X (24)
• GeForce RTX 4070 Ti
• Fedora 38
• Nvidia proprietary driver
• Hyprland (used Gnome before and it was fine)

I use it daily for work and some gaming (CP2077, BG3 of late) and it works well.

Before I'd updated the video card, I had a AMD 5700 xt and it mostly worked, but I was getting sporadic driver crashes (card would reset), which was annoying.

Laptop support is not where it needs to be especially when it comes to dual GPU.

Yes, 3060 and Wayland/gnome act funny after resuming the machine from sleep while connected to a second display.

• Some applications, e.g. Firefox will not update properly after a resume when screen config has been changed while asleep. That is, if I undock my laptop and then resume, Firefox won't visibly scroll or change, but buttons invisibly move which I know because where the mouse cursor changes when hovering changes after playing with the scroll wheel. Only fix is killing Firefox and restarting. Maybe it's a snap thing.

• On resume, wallpaper for gdm is painted on secondary monitor while laptop display stays dark, even though that's where the login prompt etc is. A quick close/open of the laptop lid forces the main display to come back online.