• Price: 370$
  • Model: Asus ROG Strix G15 (G531GV)
  • CPU: Intel I7 9th Gen
  • GPU: Nvidia RTX 2060 6GB
  • Ram: 16GB
  • Storage: Samsung SSD 980 Pro 1TB (NVME)
  • SaveMotherEarthEDF@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 month ago

    Ah the problem you are describing in wayland actually usually happens only with electron apps. Most of the electron apps require forcing them to run on wayland. They are usually running on X (x-wayland) which cause all sorts of glitches. You can use xeyes to check if the app is using xwayland or not. If eyes move when you move the cursor inside the app then it’s on xwayland.

    To resolve the issues for the electron apps I pass these parameters: --enable-features=UseOzonePlatform --ozone-platform=wayland

    Getting these args to flatpacks could be a bit tricky. You can usually find Appimages that can allow you to run these apps easily on wayland.

    I am also on ver 550.120 so doubt that driver is the issue here.

    • Petter1@lemm.ee
      link
      fedilink
      arrow-up
      2
      ·
      1 month ago

      😂i need to fix element (matrix client) with that 🥳 finally got the cause of the issue

      Thank you very much!

      How could that be fixed by the devs? Is it something electron has to update or all electron apps individually, in order for it to work out of box?

      • SaveMotherEarthEDF@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 month ago

        So last when I was following the issue on github, it would need to be supported by electron first. It’s in the works but for now, and take it with a grain of salt, I think the recommendation in the issue was to add the options in the desktop file or executable of the app yourself.

        If you are distributing the app with the flags then just a remainder to set the compatibility of the flags such that it also works with X.