• wh0_cares@lemmy.blahaj.zone
      6·
      8 months ago

      I was having a similar issue with screen tearing on i3, although I’m on AMD, so your solution may be different.

      The two solutions I found were either swapping to a wayland based wm, like sway, which I’ve heard nvidia doesn’t like, or running a specific command either in the terminal or your i3 config file, which is not in my config file for some reason, and I’ve … kinda forgotten what the command was.

      … damn, I thought this would be more helpful. Good luck finding a solution that works, I’m sure googling can help.

      • KillingTimeItself@lemmy.dbzer0.comEnglish
        2·
        8 months ago

        mmm, i dont want to use wayland tbh, i’ll pick it up eventually, when its mature enough for consideration, but until then im learning about x shenanigans, and it’s quite fun. And likewise, nvidia, so.

        I’ll see what i can find on the internet ig.

          • KillingTimeItself@lemmy.dbzer0.comEnglish
            2·
            8 months ago

            that would be the secondary reason i’ve been using linux for 4 going on 5 years now lol. Love it, wouldn’t it trade it for anything. Even with the hell that it can be from time to time.

    • halva@discuss.tchncs.de
      6·
      8 months ago

      use picom or FullCompositionPipeline in Xconf

      or wait for a few months until explicit sync patches arrive and nvidia finally becomes truly stable on wayland

    • Cassa@lemmy.blahaj.zone
      4·
      8 months ago

      KDE has a display option that might help! it works a bit 😅 - “screen tearing: [_] allow in fullscreen windows” - it’s at the bottom.

      but if not then x11 for you :/ I switch back and forth - for some applications. But finally getting an AMD card, in the mail now 😍

      • KillingTimeItself@lemmy.dbzer0.comEnglish
        2·
        8 months ago

        i’ve been through the wiki shenanigans more than a few times, havent fully read up on them yet though, i’ve tried the obvious ones, so far they haven’t done much. Seems like it’s only video playback, havent tried a game for long enough to see yet though.

    • gentooer@programming.dev
      4·
      8 months ago

      Same on i3 on a dual graphic Nvidia/Intel laptop. For me switching to sway (the Wayland alternative for i3) fixed it. This is on a laptop from 2013 tho, so it could be different on your hardware.

        • Something Burger 🍔@jlai.lu
          1·
          8 months ago

          I switched to Wayland recently (when updating to KDE6) and am experiencing heavy tearing which wasn’t there on Xorg, as well as other issues (cannot copy images to the clipboard, global hotkeys no longer work).

          Somehow this is nVidia’s fault (this happens on my two laptops, one with Intel+nVidia, the other with Intel only).

          • halva@discuss.tchncs.de
            2·
            8 months ago

            am experiencing heavy tearing which wasn’t there on Xorg

            in which apps? anything that runs under xwayland is broken under nvidia at the moment because nvidia don’t and can’t implement implicit sync which is required for that, resulting in terrible graphical corruption. wait for a few months until explicit sync patches arrive

            cannot copy images to the clipboard

            Works on My Machine™. sounds like a bug on plasma 6 to me, check their bugzilla and whatnot. or switch back to 5.27, it’s not like you’re morally obliged to do plasma 6 “stable release” beta testing lmao

            the other with Intel only

            does graphical corruption happen there too?