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?
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<
Five years on wayland here, it’s been great as long you don’t have single Nvidia gpu or need https://xkcd.com/1172/ kinds of x11 features
Been working great for me for ~1 year on my desktop and closer to 2-3 on my laptop.
The only thing missing for me was Barrier for input sharing, which libei is supposed to fix. I ended up going for a hardware solution as Barrier is jank af anyway.
Only thing not working for me is HDR (should be fixed in Plasma 6.1), not like you could do HDR on Xorg anyway. Also no HDMI 2.1 but that’s because fuck the HDMI Forum.
Performance-wise, just blows away Xorg in every metric, and explicit sync should make that even better.
Oh so a Plasma update broke HDR. I was wondering what happened when HDR went from looking primo to looking washed out and ugly. I’ll just wait patiently on SDR. :)
Were you using patched KWin or something? Because experimental HDR support is supposed to be one of the big features for 6.0, so unless it broke in 6.0.3 or something, you shouldn’t have had an update to break HDR in the first place because it wasn’t supported.
No just whatever came from the Arch repo. I’m not entirely sure what version I’m on right now, but it’s been broken for me for maybe 2-3 weeks. It’s not the biggest deal and I’m used to unimportant features like that occasionally breaking.
Well that’s a weird one then. It got released February 38th and took a couple days for Arch to get it. I had the washed out colors too but I didn’t have any HDR before that. That’s ~6 weeks ago so yeah it’s probably 6.0.3, the last that came out about that 2-3 weeks ago. I guess you were one of the lucky ones it worked and then broke! With a bit of luck it’ll be fixed for good on 6.1.
Any chance it’s hardware dependent? First I’m hearing of this and I just toggled it off and on to be sure I wasn’t seeing things - mine is definitely working. I’m all-Intel FWIW.
It works for most people but there’s some issues with some monitors where the color saturation doesn’t work well and result in washed out colors compared to SDR.
It will also output RGB into YUV buffers if you have a display that only supports YUV colorspaces, so you end up with a very green and reddish purpleish screen.
Initial HDR support was introduced in 6.0, and 6.1 is supposed to bring some fixes for the washed up colors. I haven’t found a bug for the YUV stuff and didn’t have time to do a proper bug report.
Ah makes sense, thanks for the additional info!
Could be that the graphics card is outputting an HDR signal (Rec. 2020 color space), but the monitor is in SDR mode. That would result in desaturated colors.
I wish it were that simple, but no. The monitor enables HDR automatically when being fed an HDR signal. I can confirm that HDR is enabled on both ends and it still ends up washed out, whereas before it was perfectly fine. :(
What hardware solution did you go with?
A bigger desk so I can just roll the chair a few inches to switch to the work laptop.
My original plan was a keyboard/mouse only KVM, probably a Teensy or a RPi or something of the sorts. But I got lazy as the extra desk space has just made it a non-issue for me. I also have a Logitech mouse that can switch between devices, so if I was going to really need that setup I’d probably just get the matching keyboard.
I can’t run xscreensaver in wayland :(
The real problem right here
That site’s great.
The main thing I wish for is for ffmpeg to start supporting the wlroots screengrabbing api.
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!
Nah. Wayland is buggy as hell on AMD too. That’s not the only issue.
Hadn’t had a single issue on my AMD igpu. If you experience issues it’s most likely coming from a different source than Wayland itself, it might be worth tracking it down and reporting the issue, so it can be fixed in the future.
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.
No, Workstation is still supporting XOrg and there just is a change proposal for to drop Xorg on Workstation 41.
The KDE Spin and the Atomic KDE Variant have no wayland anymore, but there is a COPR repo and you can enable that and reinstall the packages.
You mean the KDE spin and Atomic KDE variant have no X11 anymore?
Yes
I’d love to find an alternative to xdotool’s auto type feature (or ClickPaste from Windows).
There is
wtypebut unfortunately it doesn’t work in KDE nor GNOME because neither of them support the right protocol. I’ve run into the “<DE> hasn’t implemented $PROTOCOL” a few times in the past and it’s certainly a bit annoying.Aside from when that comes up, I don’t really have any complaints. A tool we used for work was never going to be fully functional on Wayland because of its dependence on Xinerama (I think) but thankfully we’ve moved away from it.
I like ydotool, uses a systemd user service, but fulfills my needs of KB shortcuts to paste text into vnc sessions
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.
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.
VRR on X11 doesn’t work with multi screen setup, so it might be broken for a lot of people
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
Also working screensaver and monitor power options
?
My first experience in wayland, us discovering I couldn’t control monitor sleep/standby function. I found how to reinstall X and managed to escape it since.
I dont know what that means. Normally the monitor turns off when the PC stops sending a signal. In KDE i can easily configure when to dim, turn off, lock etc. the screen.
I needed to do that from the console, xset didn’t work. As far as I could tell there was no other command.
What did you want to do?
A command to place the monitor in standby mode
What does this mean? Like unplugging without unplugging? Keeping one screen active and only turning off the other one?
I mean in the KDE monitor options I can choose [mirror,extend to left,extend to right,only external,only internal] so this is 100% possible.
That sounds like problem with specific software configuration, like missing packages in some distro or something being badly built. There’s nothing about Wayland that would prevent it from working.
Tried xset, not compatible. Tried searching equivalent command, there was none. That was in 2022.
Wayland is not a standalone server like Xorg and it doesn’t have standard utilities to control stuff like DPMS. That functionality goes to compositors that are effectively individual Wayland server implementations. Compositors can provide utilities to control display, and they usually do. For example, on KDE Wayland you can call
kscreen-doctor --dpms off, wlroots compositors (Sway, Wayfire, Hyprland,…) have inter-compatible tools, likeswaymsg output DP-1 dpms off. If that’s what you meant anyway.
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 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.
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.
So because they won’t, those who need accessibility, will require x.org… forever?
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.
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.
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.
I still can’t stream screens via discord and my autoclicker relies on a lib that only works with X
Discord would work if they ever updated their electron version.
Or just use it in a web browser. I don’t really want to run their proprietary spyware outside of a sandbox anyways.
It works fine with Firefox funnily enough
For streaming there is Wayland to X11 bridge. I have been using it regularly with MS Teams and it works great.
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.
Or Vesktop, which is a client mod that allows streaming (even with audio)
The problem is it’s completely unwatchable. Streams are 2 fps no matter how low or high quality you set the stream :c
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.
This is already possible
Mind elaborating a bit more?
I use Hyprland daily and it works great The only issue I have is that PhpStorm has some minor issues. Being a Java app, it runs via XWayland. It mostly works, but sometimes menus and popups get confused and won’t stay open.
wayland doesn’t support diagonal monitors
yeah it does it has from the start.
is there compositor support? is there a way to get kde to rotate my monitor to a specific degree via cli?
keep in mind I have no idea if there are real use cases for diagonal monitors, I just duct taped an accelerometer to the back of my monitor and can only get it to rotate in 90 degree increments with kscreendoctor and thought it would be funny if the picture was just always upright
If I remember correctly, the rotation in smaller degree increments could be used to correct some distortions on some really old CRTs that have scan lines that are skewed diagonally.
