wayland

is this usable yet? I have a nonstandard monitor setup so x11 is out of the question

  1. 2 weeks ago
    Anonymous

    No and never will since it was never meant to support a desktop workflow.

  2. 2 weeks ago
    Anonymous

    Depends what you want. If your monitors are fucked anything is better than that. Wlroots only works reliably on amd, gnome dosent support fractional scaling, no idea how good kde wayland is. I use hyprland (wlroots) and its good enough for me.

  3. 2 weeks ago
    Anonymous

    > is this usable yet?

    impossible to answer, becase "this" does not exist
    it's a "protocol" which means "this" is a bunch of separate shitty implementations, each with its own set of cute little bugs

  4. 2 weeks ago
    Anonymous

    GNOME devs hijacked it
    It's over

  5. 2 weeks ago
    Anonymous

    been using it the past 2-3 years without issue
    setup might be a pain if you have some weird distro but it just werks LULZ is full of idiots parroting outdated information

  6. 2 weeks ago
    Anonymous

    >have a nonstandard monitor setup so x11 is out of the question
    ???

    • 2 weeks ago
      Anonymous

      X11 runs extra poorly with multiple monitors, especially with rotation, VRR, etc enabled.

  7. 2 weeks ago
    Anonymous

    Been using it without flaw since Ubuntu LTS last came out, so I'd say it's definitely useable

  8. 2 weeks ago
    Anonymous

    It totally is, especially with multiple monitors, I have 2 myself and never experienced any issues on Pop. Ignore all the NEET Xsissies ITT since they have no idea what they are talking about

  9. 2 weeks ago
    Anonymous

    It is not and never will be. Stop asking.

    • 2 weeks ago
      Anonymous

      it works perfectly fine on AMD, the only issue is screen sharing the whole screen on discord (which you can get around with OBS)

  10. 2 weeks ago
    Anonymous

    does it work with proprietary Nvidia blobs yet? Haven't checked for five years.

    • 2 weeks ago
      Anonymous

      Yes

  11. 2 weeks ago
    Anonymous

    Biggest issue is zero hardware accelerated browsing on chrome based browsers.

    • 2 weeks ago
      Anonymous

      This is false

      • 2 weeks ago
        Anonymous

        Are you using the AUR only fork of chromium that allows it? Because I cannot for the life of me find a way to enable it through any other means.

        • 2 weeks ago
          Anonymous

          This is openSUSE Tumbleweed with the official google-chrome binaries. The only tweak I did is enabling the Wayland ozone platform in chrome://flags, which you have to do to make it not use xwayland anyway.

          • 2 weeks ago
            Anonymous

            Did exactly the same as yours. Hardware acceleration says it is active yet uses zero GPU and gets raped by a 4k60fps video.

            • 2 weeks ago
              Anonymous

              This is openSUSE Tumbleweed with the official google-chrome binaries. The only tweak I did is enabling the Wayland ozone platform in chrome://flags, which you have to do to make it not use xwayland anyway.

              And evidence of the zero GPU usage. under hardware accelerated video it will use the video area.

            • 2 weeks ago
              Anonymous

              Yeah, same here. I can play that video smoothly, but going by CPU usage in htop it's definitely not using hardware decoding in Chrome, and it is in Firefox.
              That's not what "zero hardware accelerated browsing" is though. Browsers use hardware accelerated rendering and compositing too. You'd notice the difference in performance (esp. scrolling) if your browser was truly 100% software rendered. No platform works like that any more.

              • 2 weeks ago
                Anonymous

                Fair. I should have said Wayland lacks "hardware accelerated video decoding" on chrome based browsers, though the issue still stands. My poor little mini PC can't brute force 4k 60fps through CPU power alone. I guess MPV always works but it still feels like this should have been solved years ago.

              • 2 weeks ago
                Anonymous

                Yeah, it sucks. Maybe it'll change when Google finally launch Lacros so they're dogfooding Chrome/Wayland on their own hardware.

  12. 2 weeks ago
    Anonymous

    The forced compositing is a deal breaker for me.

    • 2 weeks ago
      Anonymous

      Welcome to 2005+18.

      • 2 weeks ago
        Anonymous

        Yeah, no kidding. A lot of modern software sucks.

  13. 2 weeks ago
    Anonymous

    Wayland is complete. If it does not cover your specific use cases then that is a you problem.

  14. 2 weeks ago
    Anonymous

    It's usable for me (i915/amdgpu, Sway, mostly KDE/Qt5/Qt6 apps, Firefox/WebRender, Steam.) There used to be minor issues, like the menus in Dolphin wouldn't avoid screen edges, but those issues are gone now and I can't think of anything else. Everything just werks now.

  15. 2 weeks ago
    Anonymous

    name on one wayland de/wm that is not flatshit

  16. 2 weeks ago
    Anonymous

    How about you stop listening to this shit board for every little thing and take the initiative to figure things out for yourself? You know well that you're going to get the same parroted replies which won't get you anywhere.

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