this post was submitted on 21 Feb 2024
436 points (95.6% liked)

linuxmemes

21263 readers
959 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

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!

    founded 1 year ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    436
    I'm joining the Wayland club on Nvidia (sh.itjust.works)
    submitted 8 months ago by KuroeNekoDemon@sh.itjust.works to c/linuxmemes@lemmy.world
    113 comments fedilink hide all child comments
     

    I run proprietary Nvidia drivers as well and Wayland runs so much better than Xorg now that I'm permanently coming over to Wayland. I'm extremely happy rn with Wayland

    you are viewing a single comment's thread
    view the rest of the comments
    [–] jj4211@lemmy.world 13 points 8 months ago (2 children)

    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.

    [–] bitwolf@lemmy.one 3 points 8 months ago

    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.

    [–] merthyr1831@lemmy.world 1 points 8 months ago

    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