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?
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.
Edit: With some help here and a Slack update released yesterday to fix the problem, it’s working in both Zoom and Slack!
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.
missing a mountain of accessibility tools
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.
VRR on X11 doesn’t work with multi screen setup, so it might be broken for a lot of people
With explicit the protocol and the Nvidia patch for it next July, most Nvidia problems will be solved
10 bit color is supported in wlroots(sway) and hyprland, can’t speak for other desktops.
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.
please don’t post that site. I just need a few more things to work well with Wayland like Nvidia Drivers.
Last updated: 31 October 2022<
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.
I’d switched from i3 to sway, but the click offset in Krita made me switch back.
XFCE doesn’t support it yet so I’m not on it.
Also last I tried, autoclickers weren’t working
I haven’t tried it but the website lists ydotool as an alternative.
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?
On KDE Plasma, my only outstanding bug is that the “window shade” button on my window controls is broken. Too bad since I use that feature a lot.
On GNOME everything seems to work as far as I can tell. It’s pretty smooth!
That site’s great.
The main thing I wish for is for ffmpeg to start supporting the wlroots screengrabbing api.
Wake me up when there’s a working, native non-wsl waypipe client with sound for windows and android, that can hand off applications seamlessly to other hosts. (Think two computers, two monitors that feel like one).
Also working screensaver and monitor power options
I truly believe the answer to this question is going to be yes around the May - June timeframe when Nvidia releases their explicit sync enabled drivers. All aboard the Wayland hype train babyyyy!
Some way of globally capturing hotkeys, for things like starting stream, media hotkeys, etc. Only passing key events to the foreground window is shortsighted, but we need a secure way of doing this.
Pretty sure there is a protocol for this in development or maybe even merged already.
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.
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?
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.
