First of all: I don’t have anything against Wayland. I just wanna play Minecraft occasionally.

I am running Fedora with KDE on some HP workstation with an Nvidia 2060 FE. I am using the proprietary drivers. With the next release of Fedora (and KDE), Wayland will be the only supported Display Manager (as of my understanding). I tried switching to Wayland, but I get some weird black stuttering in Minecraft making it completely unplayable. The bad thing is that with my friends GPU, a GTX 1050, it worked just fine. On my Laptop with just the integrated Graphics too.

Have you got any tips for me? I neither want to switch the distro nor the desktop enviroment, as I’m happy with how it is. I could imagine buying a used amd gpu, but I dont really want to spend a lot of money.

For now, I am just waiting and hoping they’re having it fixed in the release. ** Edit:** thanks for all the help. @Pantherina@feddit.des solution, forcing it to use xwayland made it better, but then i discovered that if I’m in fullscreen, it works perfectly fine, also without xwayland. It seems like a really dumb solution, and i’m not quite happy with it, but hey, if it works, don’t touch it.

tl;dr: In fullscreen it works just fine

  • Sentau@discuss.tchncs.de
    12·
    9 months ago

    You don’t have to worry. The folks at fedora have decided that the X11 session will remain in fedora 40 so you will be able to use X11 if you still face issues in wayland.

    Edit : I was not clear enough. Want I mean to say is that the kwin-x11 and other required packages will be part of the fedora repo and people can just download them to enable the plasma-X11 session

      • Sentau@discuss.tchncs.de
        3·
        9 months ago

        At today’s FESCo meeting, we agreed on the following proposal:

        AGREED: KDE packages which reintroduce support for X11 are allowed in the main Fedora repositories, however they may not be included by default on any release-blocking deliverable (ISO, image, etc.). The KDE SIG should provide a notice before major changes, but is not responsible for ensuring that these packages adapt. Upgrades from F38 and F39 will be automatically migrated to Wayland. (+5, 0, -1)

        For additional clarification: this means that all users performing upgrades MUST be migrated to the Wayland session. They then MAY opt-in to the X11 session by installing a package for that purpose. We are explicitly not providing detailed technical implementation requirements here, but we expect all parties to follow the spirit of this decision when making technical decisions.

      • Pantherina@feddit.de
        1·
        9 months ago

        They are likely just removing the entry in sddm.

        On Kinoite you will need a custom RPM to change that setting

  • JustTesting@lemmy.hogru.ch
    9·
    9 months ago

    there’s a lot of stuff you can do, and you can end up with something usable, though not great, at least not in my experience. NVidia’s drivers are to blame, they don’t really work well with opengl and have lots of issues (and also regressions).

    The 550 beta driver is ok-ish, steam flickers but I can play games. Drivers before 535 also somewhat worked, though it really depends on your GPU.

    But I don’t think you will have it working acceptably without some work.

    Here’s some pointers on stuff to try:

    • check protondb for how other people got games to work, you can filter by your GPU.
    • try running through gamescope or gamemoderun
    • try the modeset=1 (and maybe fbdev) kernel parameters for nvidia drm
    • and there’s tons of env vars and other things that can help, I couldn’t summarize them all here, but as a pointer: XWAYLAND_NO_GLAMOR=1, WLR_RENDERER=vulkan, LIBVA_DRIVER_NAME=nvidia, GBM_BACKEND=nvidia-drm (for the drm above), __GLX_VENDOR_LIBRARY_NAME=nvidia
    • try the beta drivers, if those are available somehow (I’m on arch so they were easy to install), or just different driver versions in general.

    The above is meant more as hints than something to copy paste, so use at your own risk. You can of course always just install a second DE with X11 and log into that for gaming and use your regular DE for everything else

    • dinckel@lemmy.world
      3·
      9 months ago

      None of these will help it, sadly. The flickering is an XWayland issue that’s still not fixed. Switching to native Wayland when possible would eliminate the flickering completely, however with games it’s not as easy.

      In the case of minecraft specifically, you’ll require the newest version of lwjgl, which just got experimental Wayland support. Same for Windows games under Wine. 9.x had a native Wayland mode hidden in the settings

      • Lojcs@lemm.ee
        1·
        9 months ago

        The usual xwayland flicker alternates last two frames (unlike op’s black flicker) and never occurred to me while playing a game, so op’s problem is probably something else

        • dinckel@lemmy.world
          1·
          9 months ago

          I’m experiencing the exact same issue as the op, hence the comment. This is what helped me

      • ohje@feddit.deOP
        1·
        9 months ago

        Can you tell me how you did it? I just found an old guide for lwjgl 2.x.

        • dinckel@lemmy.world
          1·
          9 months ago

          Realistically you should just need lwjgl-glfw version 3.3.3 or newer, and that should be it

  • Lojcs@lemm.ee
    6·
    9 months ago

    Roll back your drivers to 535 if you’re on 545. 545 is broken

    • limitedduck@awful.systems
      3·
      9 months ago

      Is 545 still the latest? That release was so awful it made me completely drop Nvidia and pick up an AMD card. Fixed so many issues

      • Hirad@lemmy.ml
        2·
        9 months ago

        I’m curious how awful exactly. Been using 545 since it was released (on Arch) and except for frame drop on X11, on Wayland it’s working flawlessly and I’m even playing games on it!

        • Lojcs@lemm.ee
          3·
          9 months ago

          When I tried it games would flicker like crazy with black frames

        • limitedduck@awful.systems
          2·
          9 months ago

          Like the other commenter I also had wildly flickering frames. Overwatch in particular was stuttering back to some previously buffered frame when the framerate was either below or above a sweet spot. I was also having issues with KDE Plasma bars that I assumed was a KDE issue, but they went away with the new GPU with no other software changes than swapping drivers. I was on a GTX 1080 which was still going strong with the games I played

  • Pantherina@feddit.de
    2·
    9 months ago

    Try forcing Minecraft to use XWayland. Thats easy to do when using the Flatpak (you can open it, close it again and then copy the ~/.minecraft stuff to ~/.var/app/com.mojang.Minecraft/.minecraft or how its called to save time.

    Then in the KDE Flatpak settings you can disable Wayland (under “more settings”) and it will run as XWayland, that may fix something.

    And if you want to keep using Xorg on Fedora KDE and even Kinoite that should be possible by editing either /etc/sddm.conf or some configfile in /etc/sddm.conf.d/. This does not require the “install a RPM” hack that adding SDDM themes does.

    Btw if you want a LAN world you need to allow some random 25565 or something Port as UDP and another random port tcp and udp afaik. You enter that one port then and discovery doesnt work but other people can directly connect to you

  • excitingburp@lemmy.world
    2·
    9 months ago

    Switching over to the discrete GPU work in the efi/bios might help. Optimus (the driver that chooses between discrete and integrated) is known to be a steaming pile.

  • Errorgance@sh.itjust.works
    2·
    9 months ago

    Have you tried temporarily disabling the Compositor with Shift+Alt+F12? This fixed a lot of my graphical issues in games under Wayland with an Nvidia card.

    • Zamundaaa@discuss.tchncs.deEnglish
      4·
      9 months ago

      That shortcut does nothing on Wayland. What you’re experiencing is either placebo, or you’re not using Wayland

      • Errorgance@sh.itjust.works
        1·
        9 months ago

        You’re correct, it’s actually a KDE shortcut. My misunderstanding.

        In my case it did help, so not a placebo. Given that OP is also using KDE, it may still help.

        • Zamundaaa@discuss.tchncs.deEnglish
          3·
          9 months ago

          Yes, it is a KDE shortcut, a kwin_x11 shortcut to be more specific. It’s not a thing with kwin_wayland, and so it most certainly did not help or do anything for you - unless you’re not actually using the Wayland session of course.

          • Errorgance@sh.itjust.works
            1·
            9 months ago

            Ah, gotcha. I’m not new to Linux in general, but I’m very new to running it as a desktop (as in, the last few weeks). The last time I really tried was well before Wayland was even a thing. I’ve been distro hopping a lot to find what I like, and didn’t even realize I wasn’t using Wayland this time, oops. That certainly explains why it worked for me.

            Learn something new every day. Thanks!

  • porl@lemmy.worldEnglish
    2·
    9 months ago

    It is probably your NVIDIA driver. Version 545 has this kind of problem. Rolling back to 535 solved it for me.

  • flashgnash@lemm.ee
    2·
    9 months ago

    I’m having the exact same situation with a 2060 super particularly badly when CPU spikes but not exclusively

    Full screen hasn’t worked for me, but that’s probably because I’m using hyprland. Forcing it to run in xwayland solved the issue for you?

    • ohje@feddit.deOP
      2·
      9 months ago

      It didn’t really solved it,it just felt like it was a lot better.

      • flashgnash@lemm.ee
        1·
        9 months ago

        Ah. So no solution in sight til Nvidia fixes their buggy driver then?

        At least I know I’m not the only one getting this

  • kib48@lemm.eeEnglish
    1·
    9 months ago

    is there a way you could make it use the integrated GPU on your workstation?

    • ohje@feddit.deOP
      3·
      9 months ago

      This fixes the problem but it drops my framerate to about 10 per second.

      • anamethatisnt@lemmy.world
        1·
        9 months ago

        Then it sounds like you can either wait for nvidia to fix their buggy drivers (have you tried the beta drivers too?) or sell your 2060 fe and buy an amd gpu that will play much nicer with kde wayland.

    • TheGrandNagus@lemmy.worldEnglish
      17·
      9 months ago

      1. They aren’t criticising Wayland, they’re criticising how the Nvidia drivers handle Wayland.

      2. Criticising Wayland is fine. It’s the blind hatred and misinformation that people generally frown upon.

      E: oh, your post history shows a very unhealthy obsession with Wayland. Like, it’s the only thing this account has spoken about.

      I don’t think I’m going to comment any further than this, it’ll only waste both our time.

    • TimeSquirrel@kbin.social
      8·
      9 months ago

      Yeah, notice how it’s still up, people are having a rational discussion, and nobody is getting annoyed with anybody. Unlike whatever it is you’re doing.