This merge resquest has finally been merged into XWayland, which means NVIDIA users are just one beta driver release away (May 15th) from probably having a good experience on Wayland now!

  • Rustmilian@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    You miss the entire point of WMs then.
    You’re complaining about 7 lines of configs when the entire point of WMs is for you to literally customize everything through configs.
    Shit, you probably don’t even need half of that crap. QT_QPA_PLATFORM=wayland is already handled by qt, you only need that when running apps across Waypipe from a headless server environment. By default QT infers your environment from $DISPLY which is always :0 in Wayland.

    • 𝘋𝘪𝘳𝘬@lemmy.ml
      link
      fedilink
      arrow-up
      0
      arrow-down
      1
      ·
      edit-2
      7 months ago

      Thank you for educating me on basic knowledge about WMs, which I use since ove a decade.

      I just expect applications behave the same. I have literally not one single line of configuration for X11 in any of my configuration files.

      I need this QT variable, otherwise Cura does not work properly.

          • Rustmilian@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            7 months ago

            I don’t see any graphical glitches on my hardware.
            Perhaps you’re still on the qt5 version?
            Maybe a bug with your Nvidia driver?
            Perhaps your WM doesn’t have explicit sync yet and your card & driver needs it in this particular case? Perhaps it’s running under XWayland?

            Wayland#Qt :
            While it shouldn’t be necessary, to explicitly run a Qt application with the Wayland plugin, use -platform wayland or QT_QPA_PLATFORM=wayland environment variable.

            As it says above, it should really be inferred by default. Something weird is going on here.