Curious from people who follow its development closely.

  • What protocol are about to be finally implemented?
  • Which ones are still a struggle?
  • How many serious protocols are there missing?

https://arewewaylandyet.com/

  • exanime@lemmy.today
    0·
    1 year ago

    I’ve been using it for my daily driver for work and casual gaming with no issues for 4 months now (Garuda Linux)

  • IcePee@lemmy.beru.co
    0·
    1 year ago

    Slightly OT but hasn’t Fedora gone all in on Wayland? Maybe it’s an attempt drive critical mass of adoption and concentrate developers’ minds to closing the gap between now and fully production ready. As such, maybe moving to Fedora will net you the best support and smoothest Wayland implantation.

      • kevincox@lemmy.ml
        0·
        1 year ago

        Or just use it in a web browser. I don’t really want to run their proprietary spyware outside of a sandbox anyways.

      • devfuuu@lemmy.world
        0·
        1 year ago

        It enters a loop in discord and doesn’t work. There was a bug recently I was reading about it. Makes you go insane. All the other alternatives basically make you lose the krysp and auto microphone sound detection.

        • Cornelius@lemmy.ml
          0·
          1 year ago

          The problem is it’s completely unwatchable. Streams are 2 fps no matter how low or high quality you set the stream :c

  • SuperSpecialNickname@lemmy.ml
    0·
    1 year ago

    I’m using it on Plasma 6 with AMD graphics and so far it’s going good. When I had Nvidia I had issues with electron based applications. Games have been running pretty good regardless of the GPU, though Forza horizon 5 wouldn’t launch under Nvidia for some reason.

  • e8d79@discuss.tchncs.de
    0·
    1 year ago

    I am using Wayland and the only issue that is a bit annoying is that I can’t use fractional scaling because it breaks FreeRDP clients. Both Remmina and FreeRDP have issues when scaling is active. For now I just increased the font size in KDE its not perfect but good enough until this is hopefully fixed.

  • D_Air1@lemmy.ml
    0·
    1 year ago

    I’m still struggling with remote desktop software and other alternatives such as sunshine. KDE connect input sharing is inconsistent on wayland, but they will probably fix that eventually. xwaylandvideobridge is great when it works, but currently has an issue with eating input invisibly. Also, some things just seem to be kinda wonky. For example screen sharing portal when sharing my screen in a browser seems to open twice. Same with obs. Still no good virtual keyboard. If onboard worked on wayland that would be perfect.

    • boredsquirrel@slrpnk.net
      0·
      1 year ago

      Yes the duplicate portals are a mess. On Signal desktop there are 4 portal requests and they all say something different.

    • Björn Tantau@swg-empire.de
      0·
      1 year ago

      Still no good virtual keyboard. If onboard worked on wayland that would be perfect.

      Not perfect integration but with a workaround Onboard is somewhat usable.

      On my Steam Deck I’m mostly using Steam’s keyboard with Maliit for logins and the lock screen and Onboard in case I need special keys.

  • merthyr1831@lemmy.world
    0·
    1 year ago

    I’ve been using wayland on my laptop somce the new year and beyond some driver issues that were purely on AMD’s side (and not entirely Wayland exclusive either) I’ve had no problems.

    Stuff like application scaling works so much nicer on Wayland, and X11 just wasn’t very stable when handling fullscreen games to the point where I’d set games to borderless or even windowed mode to stop it crapping out on alt-tab

    • nexussapphire@lemm.eeEnglish
      0·
      1 year ago

      Didn’t you love it when your screen locked and the full screen app had control over your keyboard and mouse!

  • DannyBoy@sh.itjust.worksEnglish
    0·
    1 year ago

    I want to switch to get high refresh rates on my multi monitor setup. I tried recently again but I can’t for the life of me get screen sharing working, which I need for work.

    • shaytan@lemmy.dbzer0.com
      0·
      1 year ago

      Your work app may be electron based (which is a bit too common nowadays), and until they update to electron 29, wayland won’t probably work.

      (or until they add xwayland video bridge, but the former option is better than the latter.

      • DannyBoy@sh.itjust.worksEnglish
        0·
        1 year ago

        I didn’t know I needed the desktop portal for my DE as well, I’ve installed that now. Between that and updating Zoom it works on Zoom now, thanks.

    • frazorth@feddit.uk
      0·
      1 year ago

      What were you trying to screen share with?

      Most of the apps people are using are Electron, which has supported Wayland and the pipewire screensharing for nearly 4 years. However since Chrome/Chromium doesn’t enable Wayland by default, Electron won’t. Which also means that no one tests it in their apps.

      I’ve had such success just ignoring the apps and using the web client since that’s up to date and doesn’t require the app builders to enable features.

      At least under Fedora.

  • Fushuan [he/him]@lemm.eeEnglish
    0·
    1 year ago

    Most comments have been positive, so I’m gonna list all my issues. Using endeavours with KDE 6.2 and the AUR explicit sync patch, 5800 ryzen CPU and 3080 NVIDIA GPU.

    The discord xwayland app can’t share screen, and the waycord app that fake chromiums the web interface that let’s you share screen has the sound bug out sometimes with large sound spikes. So if I want to share the screen I have to open the second app and then close it fast to minimize the chances I annoy my friends.

    Window positioning. It almost seems a flagship Wayland issue. I would love if apps remembered on which screen and position I left them the next time I open them, telegram opens in the middle of the primary monitor, and I have to drag it to the right of the secondary one every time I switch on the PC.

    Shutting down in any way that is not opening the console and typing reboot or “shutdown now” takes way way longer and sometimes bugs out. This might not be a Wayland issue, but a KDE one.

    The tdrop program that let’s you interact with any terminal as if it were a dropdown terminal doesn’t work in Wayland, and it just isn’t the same to open a terminal in the normal way, is lame. Foot is a good terminal for sure but I want the dropdown effect.

    I can’t think of anything else right now, most explicit sync issues I had were fixed with the AUR patch, so of anyone has those issues wait until the real patch comes around and they will get fixed. It was quite annoying without the patch though, some programs glitched visually hard and several games were unplayable due to the heavy ghosting (dark souls 2 and dragon’s dogma 2, for example). I’ll add to this comment if I remember anything else. Even if the issue was recently fixed it’s good to have a list of stuff so that people can check it out and confirm that it’s fixed, for posteriority.

    • cobra89@beehaw.org
      0·
      1 year ago

      The tdrop program that let’s you interact with any terminal as if it were a dropdown terminal doesn’t work in Wayland, and it just isn’t the same to open a terminal in the normal way, is lame. Foot is a good terminal for sure but I want the dropdown effect.

      https://wiki.archlinux.org/title/Yakuake

      It’s its own terminal but I find it to be pretty good and it works with Wayland.

    • azvasKvklenko@sh.itjust.worksEnglish
      0·
      1 year ago

      You mean Plasma 6.0.2, not 6.2 - that will be released in a year.

      Use X11 to Wayland Video bridge to get screen sharing working with any X11 app that can’t talk to desktop-portal/PipeWire (such as Discord)

      What’s worth noting is that applications, as of now can’t affect window positioning in any way. It’s all about how compositor (kwin_wayland in this case) is placing them. Personally I don’t care that much because I’ve got shortcuts to quickly move windows between screens or desktops. You might consider looking at window rules - they’re pretty neat on KDE.

      Shutting down? What???

      On the tdrop thing, I wouldn’t expect it to be possible in near future, but how about Yakuake?

      • Fushuan [he/him]@lemm.eeEnglish
        0·
        1 year ago

        Yeah, 6.0.2, the version available in the arch repos.

        I’ll check the video bridge, thanks! – Update on this, apparently I was already using it since it ships by default with KDE, it seems to be a discord bug. Weirdly enough, going back to an older flatpak version (0.0.42) fixed the issue. I’ll have to check the updates to see if they fix it.

        Thanks on the window rules mention too. – Update on this, you are a saint. I added a rule for the telegram window in KDE so that it remembers its position, and it simply works. https://imgur.com/a/zrvbRPI

        Yeah, idk, when I try to use the GUI it takes way longer than the CLI command somehow, and sometimes it blocks itself. It must be something related to some programming hanging itself and the system trying to wait until it stops, but I can’t be bothered, it’s way faster to open a terminal and just typing the command or opening KDE connect and pressing the “shutdown now” shortcut. Not a Wayland issue though.

        I did use yakuake in the past but call it stupid brain, but once I read that alacritty was faster and I customized it to my liking, and then checking that foot was a little bit faster, I can’t go back. It’s stupid, I know that most of the use I give the terminal is actually spent on the commands themselves and that I can give transparency and remove window borders in yakuake, I’m just pissy that my fancy combo stopped working.

  • makingStuffForFun@lemmy.ml
    0·
    1 year ago

    I use an accessibility tool called Talon Voice. It is x.org only. Will the shift to Wayland kill these tools, or is it a case of the developer needing to rewrite for wayland?

    • boredsquirrel@slrpnk.net
      0·
      1 year ago

      On X11 apps can scan and read what they want. This is not even very good, but developers dont need to implement accessibility really, just make all text scannable.

      If this is a screenreader you are talking about.

      Apps need to send the reader specific texts that shouls be read, like push notifications. And this needs to be implemented, because on Wayland no app can just scan everything.

      • wewbull@feddit.ukEnglish
        0·
        1 year ago

        So rather than having one single app that deals with screen reading, it’s now down to every individual application to make accessibility a priority.

        Huge retrograde step.

        We can all agree that authors should all value accessibility, but we also all know that they won’t.

        • lemmyvore@feddit.nlEnglish
          0·
          1 year ago

          That’s one of the huge problems with Wayland. The core protocol is super minimalistic so it falls to each and every individual app to (re)implement everything: accessibility, clipboard, keyboard, mouse, compositing etc. etc.

          The fact this was done in the name of security is a solution looking for a problem. Inter-window communication was never a stringent security issue on Linux.

          It’s like advising people to wear helmets in their everyday life. Sure, in theory it’s a great idea and would greatly benefit those who slip and fall, or a flower pot falls on their heads, or are in a car accident and so on. But in practice it would be a huge inconvenience 99.99% of the time.

          The largest part of all Linux apps out there will never get around to (re)implementing all this basic functionality just to deal with a 0.01% chance of security issues. Wherever convenience fights security, convenience wins. Wayland will either come around or become a bubble where 99% of Linux userland doesn’t work.

          • Zamundaaa@discuss.tchncs.deEnglish
            0·
            1 year ago

            it falls to each and every individual app to (re)implement everything: accessibility, clipboard, keyboard, mouse, compositing etc. etc.

            I haven’t read so much nonsense packed in a single sentence in a while. No, apps don’t implement any of these things themselves. How the fuck would apps simultaneously “implement compositing themselves” and also neither have access to the “framebuffer” (which isn’t even the case on Xorg!) nor information about other windows on the screen?

            Please, don’t rant about things you clearly don’t know anything about.

        • boredsquirrel@slrpnk.net
          0·
          1 year ago

          GUI frameworks should implement this, just like any app built on GTK, Qt, Iced or possibly others have native wayland support.

          But yes I agree this is not a good situation. There should be something like “accessibility permission” on Android, where apps can basically read anything.

  • bionicjoey@lemmy.ca
    0·
    1 year ago

    I don’t follow this stuff at all, so I have no idea what the advantages are of Wayland that I’d actually see and benefit from in my daily use. That being said, I saw everyone saying it’s better, so I tried switching to it. After rebooting, my PC just showed a black screen. I needed to use a TTY to revert back to xorg. So no, as of right now I’m not using Wayland.

  • mlg@lemmy.worldEnglish
    0·
    1 year ago

    HDR is only experimental on gnome and kde with weston not having an implementation.

    I think 10 bit color depth hasn’t even been worked on much.

    VRR I think is about finished although X11 has it too.

    And the Nvidia wayland support is slowly improving although still full of bugs and stability issues.