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.
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. :(
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.
Wondering if anyone has an alternative to cursr. That’s really the only thing stopping me from making the switch to Wayland full time. I use to make my 2 displays that are different resolutions play nicer
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!
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.
What app? … that is kinda relevant and you should open a Bug that they need to support pipewire portals for screenshare.
Or, as said, use the browser version.
Zoom runs fine in the browser, and it way less invasive. Keep in mind, that “screenshare works” that this app can record everything you do as long as it is running. And if it is a native app (no flatpak) then it can also start how it likes.
It’s Slack, so Electron, and the browser version unfortunately doesn’t support Huddle calls, which is what we use for all our calls and where I’d be screen sharing from.
Annyoing. If you are/were on KDE Plasma there is XWaylandVideobridge, which allows to share the screen by apps requesting access to the webcam, but getting a virtual input instead, which comes out of KDEs portal.
Yeah complex, but said to work. Apps need to run as X11 though.
I’m on GNOME, but thanks for the help. Getting me to dig deeper and figure out it’s a known issue with Slack and not Wayland will help me going forward.
No, screensharing works really well. Only problem is if apps expect to show a preview themselves, like Firefox. Then you get annoying duplicate portal requests, still works.
Edit: I just updated Zoom and it’s working now! Zoom doesn’t work at all Slack gives me one window at a time and black screens for Firefox windows. I will try both of these in the browser and see if I get anywhere.
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!
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.
Valve is great in terms of Linux support and it’s development, but to be honest I hate Steam launcher too. I do not use the store frontend, friendlist, notifications and other things on top, all I want is to download game binaries and updates.
You can still make shortcuts to your steam games to launch them outside of steam. However I have noticed that the Blizzard launcher doesn’t seem to fully quit after quitting the system tray icon, I have to click stop game in steam. I guess I still prefer this to having unused wine/proton process running in the background.
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.
On kde there’s a feature where you can pass all keys to x11 apps and on hyprland you can specify which keys get globally passed to which apps and maybe all keys.
If all else fails you can create a script that uses obs sockets and runs as root to capture keys globally. They seem to be looking into a global keys portal though.
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.
I have a steam deck and getting assassin’s creed… dunno, brotherhood? to run was so annoying, I thought about just letting it be. I’ll stay away from their games now.
I haven’t played anything blizzard in a minute but I absolutely LOVE the ubi launcher that asks for admin permissions two to eight times then makes me look up my password each time I launch one of their games (not that often) despite checking Remember Me EVERY TIME
XFCE is my preferred DE when I’m using one. It’s got a long lineage going back to FVWM and the setup remains consistent between new updates. I appreciate how it stays out of the way.
For anybody else following along, XFCE is working on Wayland support. In fact, the only component not already supporting Wayland in Git is XFWM4 itself. Wayland will ship officially as part of the 4.20 release.
They are creating an abstraction library that will allow XFCE to support both X and Wayland. Other desktop environments are going to use it as well.
I recently tried to get Wayland working. Followed a simple guide to enable some NVIDIA boot parameter. Somehow it fucked my complete grub and I couldn’t boot until I messed around a fair bit with live usbs. Cost me a whole evening.
So I guess what Wayland is missing is normal support from the GPU manufacturers.
I don’t know how you messed that up, usually the switch is as easy as it can be, and the issue comes when using it, for its lack of explicit sync, causing apps to flicker, and frame pacing in games to be plain bad
This is being fixed in the next two months thankfully
Edit: Taking about Nvidia wayland support here, AMD and Intel are great
Nvidia didn’t want to play nicely and give standard APIs.
Their work around was other extensions that don’t actually do what’s needed, but sort of works in some scenarios.
All the GPUs I’ve used work fine, it’s a Nvidia throwing it’s toys out the pram situation which should hopefully get resolved as they open source the high level drivers and so the correct APIs can be implemented.
Nvidia don’t give a shit about Wayland. The reason they’re adding explicit sync is because it was implemented in the kernel. They don’t care how it will be used or by what.
lemmy.ml
Oldest