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
    link
    fedilink
    arrow-up
    11
    ·
    edit-2
    8 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
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        8 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.

  • Lojcs@lemm.ee
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    8 months ago

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

    • limitedduck@awful.systems
      link
      fedilink
      arrow-up
      3
      ·
      8 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
        link
        fedilink
        arrow-up
        2
        ·
        8 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
          link
          fedilink
          arrow-up
          3
          ·
          8 months ago

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

        • limitedduck@awful.systems
          link
          fedilink
          arrow-up
          2
          ·
          8 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

  • porl@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

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

  • excitingburp@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    8 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.

  • flashgnash@lemm.ee
    link
    fedilink
    arrow-up
    2
    ·
    edit-2
    8 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
      link
      fedilink
      arrow-up
      2
      ·
      8 months ago

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

      • flashgnash@lemm.ee
        link
        fedilink
        arrow-up
        1
        ·
        8 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

  • Errorgance@sh.itjust.works
    link
    fedilink
    arrow-up
    2
    ·
    8 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.de
      link
      fedilink
      English
      arrow-up
      4
      ·
      8 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
        link
        fedilink
        arrow-up
        1
        ·
        8 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.de
          link
          fedilink
          English
          arrow-up
          3
          ·
          8 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
            link
            fedilink
            arrow-up
            1
            ·
            8 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!

  • kib48@lemm.ee
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

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

    • ohje@feddit.deOP
      link
      fedilink
      arrow-up
      3
      ·
      8 months ago

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

      • anamethatisnt@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 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.

    • TimeSquirrel@kbin.social
      link
      fedilink
      arrow-up
      8
      ·
      8 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.