>boot plasma session with Wayland one (1) time. >entire system shits itself

>boot plasma session with Wayland one (1) time
>entire system shits itself
I'll continue using X11 thank you very much.

Tip Your Landlord Shirt $21.68

Yakub: World's Greatest Dad Shirt $21.68

Tip Your Landlord Shirt $21.68

  1. 2 weeks ago
    Anonymous

    *krashes*

    • 2 weeks ago
      Anonymous

      I'm thankful for KDE because, by switching to Wayland as the default, they further proved how Wayland itself is a mess and it's not merely a GNOME-specific issue.

  2. 2 weeks ago
    Anonymous

    just wait until June for Nvidia/wayland to finally work

    • 2 weeks ago
      Anonymous

      two more weeks

    • 2 weeks ago
      Anonymous

      You'll never position a new window where you want

      • 2 weeks ago
        Anonymous

        what do you mean this is not wayland issue

        • 2 weeks ago
          Anonymous

          I mean I am tired of the philosophical homosexualry of wayland trannies about what is a wayland issue and what isn't. Meanwhile when I init a window using any graphics library (glfw, sdl2, raylib whatever) with a specific position, it just works in x11 but not in wayland. Wayland is not what I think it is and it's a mutter issue? Fine. Then wayland should never ever be in the same dropdown box with x11. Frick wayland.

  3. 2 weeks ago
    Anonymous

    >run Wayland
    >literally cannot launch many things in wine for no reason I can think of
    >go back to x11
    guess I'll just deal with tearing
    amd gpu btw

    • 2 weeks ago
      Anonymous

      I mean these crash criticisms on Wayland or performance are fairly weird since for some people Xorg crashes and Wayland works fine.

      The real issue is the actual technical limitations of the protocol and all the non-standardized extensions that work only in some places.

      The reason is obvious. Wine can't port the WinApi to Wayland.
      Initially they shelved a Wayland port entirely, then 7 years later or something they decided to come with a very limited subset of WinApi features which essentially works for fullscreen games but any application like photoshop that needs to give users dialog windows isn't going to work.

      They can map it to X11.

      • 2 weeks ago
        Anonymous

        >The reason is obvious. Wine can't port the WinApi to Wayland.
        >Initially they shelved a Wayland port entirely, then 7 years later or something they decided to come with a very limited subset of WinApi features which essentially works for fullscreen games but any application like photoshop that needs to give users dialog windows isn't going to work.
        What I don't understand is why all these big projects go along with the insanity. I mean one thing is all the Redhatware, but does no one else stop to evaluate whether all the hours wasted so far trying to support it have been worth it?

    • 2 weeks ago
      Anonymous

      I have TearFree enabled and I don't have tearing

  4. 2 weeks ago
    Anonymous

    I'll never use gayland or gnome3+. Not using your shitware.

  5. 2 weeks ago
    Anonymous

    Same thing for me
    This is just unusable, I've encountered so many bugs making using wayland a really bad experience
    It's funny they are completely ignoring the fact that nvidia has like 70% market share

    • 2 weeks ago
      Anonymous

      >It's funny they are completely ignoring the fact that nvidia has like 70% market share
      As of now, Wayland is a net negative regardless of GPU.

      While Wayland has admittedly fewer issues on AMD and Intel GPUs, X11 still works better on them.

  6. 2 weeks ago
    Anonymous

    didn't it get an update recently? why is everyone saying it's abandoned?

  7. 2 weeks ago
    Anonymous

    > boot plasma on Wayland for the first time
    > it works perfectly

  8. 2 weeks ago
    Anonymous

    >install arch with kde on amd
    just worKs

  9. 2 weeks ago
    Anonymous

    >launch game on wayland
    >it uses "xwayland"
    lmfao

    • 2 weeks ago
      Anonymous

      >dude its better because it's both, the input delay is just the code of conduct daemon!

  10. 2 weeks ago
    Anonymous

    >run hyprland, the most unstable Wlroots compositor
    >Everything just works
    Seems like you have a skill issue.

  11. 2 weeks ago
    Anonymous

    works on my kde 6.0.4 nvidia dgpu+amd igpu machine machine
    >gnome
    not my problem

  12. 2 weeks ago
    Anonymous

    >No Wfce
    Simple as

  13. 2 weeks ago
    Anonymous

    I tried gayland once with KDE, it was so fricking broken I realized this could only happen if you fall for IQfy memes

    • 2 weeks ago
      Anonymous

      you mean KDE? because IQfy hates Basedland

      • 2 weeks ago
        Anonymous

        >IQfy hates Basedland
        Yeah, right, that's why it's being shilled here all the time. Next you're gonna tell me IQfy hates Apple shit too, huh

  14. 2 weeks ago
    Anonymous

    >Be on my laptop
    >Go from X11 to Wayland
    >Games run 5% faster

    >Be on my desktop
    >Go from X11 to Wayland
    >Games run 2% slower
    ???

    • 2 weeks ago
      Anonymous

      > Be on any device
      > Disable compositor on X11
      > Go from X11 to Wayland
      > Games run 10% slower

  15. 2 weeks ago
    Anonymous

    As long as you're not running it as root, you'll be fine.

  16. 2 weeks ago
    Anonymous

    Yo, wayland shills. How do you restart Xwayland without restarting the Wayland session? Because occasionally, Xwayland crashes if I happen to move the mouse too far while tabbing between windows, leaving me unable to use applications that don't support wayland yet.
    KDE if it matters.

    • 2 weeks ago
      Anonymous

      >KDE
      Just wait for 5 minutes and let it krash

    • 2 weeks ago
      Anonymous

      >Xwayland crashes if I happen to move the mouse too far
      The absolute state

      • 2 weeks ago
        Anonymous

        Um, you see, ackshyually it's Xorg's fault (even though it's due to the wayland protocol being fragile by design.) You should use only Wayland-native apps (even though wayland apps also crash like this, even more so than X apps which only do so occasionally.) It's your bad software's fault for doing the needful on the main thread (even though the absurdity of killing apps for blocking the main thread seconds is self-evident.)

        • 2 weeks ago
          Anonymous

          >the absurdity of killing apps for blocking the main thread *for 0.2 seconds is self-evident

        • 2 weeks ago
          Anonymous

          >5 years ago
          >still a problem
          https://gitlab.freedesktop.org/wayland/wayland/-/issues/159
          https://gitlab.freedesktop.org/wayland/wayland/-/issues/443

          G*d, Wayland is never gonna be usable is it?

          • 2 weeks ago
            Anonymous

            At least they acknowledged there's an issue.
            Meanwhile, in wlroots...

          • 2 weeks ago
            Anonymous

            > *reports bug*
            > "yes it is a bug"
            > 5 years later
            > *nothing changed*
            One would think that not working around design problems would be incentive for the protocols to stop being shit...

          • 2 weeks ago
            Anonymous

            >GNOME mutter fixed
            GNOME chads, we won.

          • 2 weeks ago
            Anonymous

            >Breaks shitty software written in python that also blocks the main loop
            Honestly starting to think KDE is based.

    • 2 weeks ago
      Anonymous

      just move the mouse less, chuddie. run better software

      • 2 weeks ago
        Anonymous

        Let's be honest. Do you even need a mouse? What's the use case for such a device?

        • 2 weeks ago
          Anonymous

          how am i supposed to kjerkoff to gskinny ktrannies in kpronhub without a KGmous?

  17. 2 weeks ago
    Anonymous

    Works fine on my Hyprland , also I have nvidia

  18. 2 weeks ago
    Anonymous

    when nvidia releases 555 beta next month it's over for us xorg sisters...

    • 2 weeks ago
      Anonymous

      I'll stay with 525.105.17 + plasma5 + x11 session on Debian 12 lil bro

  19. 2 weeks ago
    Anonymous

    It drives me absolutely insane that Plasma went from a having a rock solid X11 session, to now a completely broken X11 session AND Wayland session. As soon as they unfrick their X11 session I'm going right back--I have to run nearly all of my applications under XWayland anyway to get them to not glitch out and frick up.

Your email address will not be published. Required fields are marked *