• pathief@lemmy.world
    link
    fedilink
    arrow-up
    55
    arrow-down
    3
    ·
    edit-2
    1 year ago

    I can only hope plasma6 has serious improvements on Wayland compatibility with nvidia drivers because plasma5 is unusable.

    Yes, I know it works on your machine. It doesn’t work on mine :P

      • Secret300@sh.itjust.works
        link
        fedilink
        arrow-up
        30
        arrow-down
        2
        ·
        1 year ago

        Ye but people don’t want to accept that the company charging $5000 for a GPU is also too stubborn and lazy to pay any devs to write decent drivers

        • Sentau@lemmy.one
          link
          fedilink
          arrow-up
          23
          ·
          1 year ago

          This is what I don’t get. AMD has driver issues on windows because of a combination of their own incompetence and windows updates doing stupid windows things - people squarely lay the the blame on AMD. NVIDIA releases bad closed source drivers causing issues on linux - somehow the fault of linux and the open source communities.

          These people should be hounding NVIDIA to fix their issues instead crying to DE developers to fix issues caused by NVIDIA.

          • chayleaf@lemmy.ml
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            because in Windows, blame doesn’t solve problems. You can blame Microsoft, or you can blame AMD, but either way nothing will change. In Linux, there’s some level of accountability because almost all software has maintainers (if not, you can step up personally). Similarly, you can’t hold Nvidia accountable on Linux - best you can do is not buy their GPUs.

    • kadu@lemmy.world
      link
      fedilink
      arrow-up
      23
      ·
      1 year ago

      Nvidia’s latest driver patched several issues with Wayland sessions - perhaps the experience will be a tiny bit better now

      • FalseDiamond@sh.itjust.works
        link
        fedilink
        arrow-up
        8
        ·
        edit-2
        1 year ago

        I had a quick go at it yesterday (the latest 535 broke DDC CI for one of my monitors, making plasma-powerdevil unable to start) and for whatever reason KWin ran at something like 3 seconds per frame. No that’s not a typo, I mean it. I hope it’s fixed before it gets to Arch’s repo.

        EDIT: It works! I had to switch to the DKMS driver (the main one isn’t in the repos yet) but other than that my Wayland session didn’t die a horrible death. Well smooth. I still didn’t test much, but at least night light works.

      • pathief@lemmy.world
        link
        fedilink
        arrow-up
        4
        ·
        1 year ago

        Waiting for the driver to reach the repos to try it out. I am hopefull in an Hyprland future! You know, some day!

    • merthyr1831@lemmy.world
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      2
      ·
      1 year ago

      Hopefully Fedora and others forcing users onto Wayland is going to help push Wayland devs to fixing the stuff that’s breaking compatibility for everyone still stuck on X11.

      • SquigglyEmpire@lemmy.world
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        1 year ago

        Wayland is just a protocol, issues need to be fixed by devs of the apps/toolkits that have still haven’t migrated over unfortunately.

      • pathief@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        Yeah, I share the feeling. Not sure if the problem lies on Wayland or Nvidia but hopefully if Wayland becomes the standard they’ll address the elephant in the room!

        • loutr@sh.itjust.works
          link
          fedilink
          arrow-up
          4
          arrow-down
          1
          ·
          1 year ago

          Wayland is just a set of protocols, which work fine (albeit with limitations) when implemented properly. So if KDE’s implementation of its share of the APIs works correctly with Intel and AMD GPUs, but not with Nvidia ones, the culprit is extremely likely to be the latter.

    • devfuuu@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      edit-2
      1 year ago

      Completely agree. I keep trying to open a new session on a clean new user regularly to check if it works and it is absolutely horrible. 3 days ago after updating the system and seeing some new latest kde versions coming in, tried again and noped the out of it in a few minutes. The fonts and scalling in so many places are very bad.

      I keep reading about great improvements in the 6 version and am really hopeful for it to be usable.

      Or the problem is just that no developers have normal regular laptops that are 14’’ at 1080p and can’t imagine that proper scaling at 125% and 150% needs to work out of the box.

      Edit: I don’t even have nvidia hardware, it’s just regular intel stuff. Can’t imagine the struggle of nvidia folks.

      • Chewy@discuss.tchncs.de
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        The other half of the developers have 13" 2160p displays that are sharp either way – but don’t notice the battery life hit.

        Iirc there’s ongoing work for proper fractional scaling protocol, so it might get fixed for KDE/QT applications at some point.

        • KISSmyOS@lemmy.world
          link
          fedilink
          arrow-up
          2
          ·
          1 year ago

          Iirc there’s ongoing work for proper fractional scaling protocol

          I don’t know why “making stuff show up bigger on a screen” isn’t a solved problem in 2023, and at this point I’m afraid to ask.

          • Chewy@discuss.tchncs.de
            link
            fedilink
            arrow-up
            2
            ·
            1 year ago

            Many apps are designed with bitmap icons (png, jpg) instead if svg, so fractional scaling requires manual changes.

            Also, frameworks like GTK don’t have enough development resources to quickly make changes to support anything besides integer scaling. It’s difficult to change to fractions if everything assumes integers.

            PS: “making stuff show up bigger on a screen” works already, it’s just not perfect. Windows is as far as I know the only OS coming close to doing scaling perfectly. Except Android and similar OS that were designed with fractional scaling in mind.

    • Xirup@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Completely agree, as an NVIDIA user (for now) I am screwed if I am required to use Wayland. I mean, I use Wayland for a long time and it works well with NVIDIA but there are many things that don’t quite work, like many emulators (Yuzu/RPCS3) that for some reason have a strange tearing, or some programs that simply won’t open in xWayland.