• insomniac_lemon@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    4 days ago

    Just grep the source for “wayland” and you’ll see what I mean.

    and

    # Refuse to build in Arch package environments

    MATCHES ".*archlinux.*")

    Not sure if there is more to this, but it seems like it screws over X11 users for no reason (I’m still using a 1050Ti).

      • insomniac_lemon@lemmy.cafe
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        4 days ago

        I waited a long while to try it

        look inside

        crash to login manager.


        Not sure if you’re using some non-proprietary driver or what, but I’m not worried about switching over. Maybe nice with AMD GPU, unlikely for me though.

        I don’t want GNOME or Plasma (I’ve had issues with Plasma on X11 when I tried it) so that could be it, too.

        • Junkers_Klunker@feddit.dk
          link
          fedilink
          English
          arrow-up
          4
          ·
          4 days ago

          I’m on bazzite KDE and haven’t reconfigured anything because everything just ran smooth, but I realise I might be the minority here.

    • sem@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      4 days ago

      Can someone grep Wayland and tell us what you find?

      IDK how I would do that on my phone.

      • Max-P@lemmy.max-p.me
        link
        fedilink
        English
        arrow-up
        13
        arrow-down
        1
        ·
        4 days ago

        I find mostly complaints around Wayland not working like Xorg, like complaining they can’t just get the absolute cursor position and things like that.

        Sounds very much like parroted points from probonopb’s rants, like claims of “broken by design”.