this post was submitted on 21 Feb 2024
437 points (95.8% liked)
linuxmemes
21608 readers
1300 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I keep trying Wayland and an in the middle of an attempt. I use fedora maniacally updated, Nvidia, and plasma shell. I'm about to abort again:
-even configured to directly use Wayland, I see chrome based browsers glitch out on occasion, and when it starts glitching it just keeps on glitching
-plasma panel stops updating multiple times a day, staying frozen including the clock
-sometimes kwin starts, but plasmashell has to run manually, and per above has to be restarted on occasion
-occasionally it just forgets what the monitor resolution is supposed to be and reverts to 1024x768
-the blur translucency effect glitches around mouse cursor
-immersedvr doesn't support Wayland
On the flip side, xorg problems are: -occasionally kwin can't grab keyboard for some effects until restarted. This is a well documented bug butt other than it being xorg specific, doesn't seem to be figured out.
-some things tear in ugly ways, but not nearly as bad as the chrome glitch under Wayland.
Maybe kwin isn't a great Wayland compositor, maybe Nvidia drivers are still not up to snuff. Ultimately, it's not viable for me. Further kwin is a huge factor for "why Linux desktop" for me, gnome shell is more limited even than Windows for my workflows.
I had those same issues on my 3080. I switched to AMD and Kwin works great on Wayland.
I wonder. Does KWin still use the old workaround for Nvidia?
I remember gnome refusing to bend to Nvidia over eglstreams.
If Kwin is still using that workaround, even now after Nvidia conceded, maybe that is the problem.
Definitely think NVidia has got some ways to go on improving Wayland drivers. AMD has its share of issues but they're a lot less obtrusive than what you're describing