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<
Yes
Even on Nvidia. I’m on NixOS w/ Hyprland on a RTX 3080 in reverse sync on a multimonitor setup, and have no issues.
Everything just works most of the time. When it doesn’t, updating the driver usually fixes the issue.
deleted by creator
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
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
10 bit color is supported in wlroots(sway) and hyprland, can’t speak for other desktops.
With explicit the protocol and the Nvidia patch for it next July, most Nvidia problems will be solved
I’m going to buy an AMD video card this weekend solely so I don’t have to deal with the NVidia bullshit anymore. I’m eager to give hyperland a try.
How’s the AMD drivers situation on Linux? I always used Nvidia since they have official drivers, but might change for the next card if AMD works better. I don’t use Wayland so never ran into the issues.
If your AMD card is older than your latest linux distro release it’s plug and play, no driver installation required
Wayland works pretty well on most desktop environments toobeware fresh released AMD cards in combination with long term release distros like Debian stable, you most likely will need the driver from the AMD website (not recommended)
Mesa is usually pretty quick to update, it’s just that stable distros won’t update mesa all that quickly. I assume most of them have some way to install a newer mesa from a community repo or something.
I love hyprland, but plugging my laptop into a projector for a presentation and forgetting to mirror displays was a fun time. Hard to explain the default anime girl away without people knowing what you’re talking about that. Since then I’ve learned you can disable that background lmao
Oof that sounds hella unprofessional though
That’s the hyprland community, for good and mostly bad
https://github.com/hyprwm/Hyprland/issues/2930
I have a feeling most of these people are either NEETs or never used a work computer.
I’m on the gay side of the community (and have only seen Ghibli and Cowboy Beebop which takes away a ton of credentials). Still rough, but a tad better. Downloaded a premade setup from github because it’s cute and left it with that. Outside of adding some keyboard shortcuts
Judging people’s backgrounds is 100x more unprofessional imo unless they’re like seriously questionable
Idk what specific image was shown. But anything described as “anime girl” could have strong csam vibes assuming this grad school student is older than 11 themselves.
For some reason its normalized in some parts of the Linux community to have sexualized images of children.
The stock wallpaper is not NSFW in any way as I remember
It was just a presentation for peers in grad school. For a fun project unrelated to my thesis. Would never have used my personal for a work related presentation. Just a funny story nonetheless. Getting mad shit from buddies beats being fired or passed for promotion anyday lmao
Sounds like a hell of your own making. Always change the background to something generic. Like a nice tree. Always. Nobody gives a shit about trees.
This has long been the best advice. However, just in case you are not aware, some pretty important NVIDIA changes are expected to drop in the next 2 months. It will take a while to work into every distribution but NVIDIA should finally work as well as AMD.
Yes I know. I have read all about explicit sync. It’s going to take at least a few months to trickle into the various packages and distributions and we’re still trusting NVidia to give us a proper driver with it as well. And we’re assuming there’s nothing else that will cause yet more problems with Wayland/etc.
I’m at my wits end trying to be patient with them (on the order of years). I now understand why Linus flipped them off with a loud “F you”.
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
Didn’t you love it when your screen locked and the full screen app had control over your keyboard and mouse!
Here is an alternative Piped link(s):
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
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. :)
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. :(
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!
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.
is Debian shipping with it default yet?
while Debian is still deciding if they ship with Wayland by default or not, Fedora and KDE are planning to already completely drop x11 for their next release (they ship Wayland by default)
For Fedora I’m not surprised, but KDE is considering dropping X11 support already?
Yes, because Plasma 6 is so flawless on Wayland. /s
Fedora should drop every other DE except KDE. That would really free up some resources.
It would also uncheck a lot of accessibility requirements that RHEL in particular needs.
I was kidding about Fedora but Red Hat can actually afford to do that. They’re not a generalist distro, they can and should offer their customers a very specific desktop stack.
Part of the reason red hat uses gnome is because it is the only desktop that meets many accessibility requirements. It would be a huge engineering effort to bring any other desktop up to par in that regard. Most graphical Linux software is really far behind in accessibility.
Fedora 40 with kde plasma 6 dropped a day or two ago, and they did remove x11, you have to get it from the repo in case you want it, otherwise, it only comes and is planned for wayland, which I believe is great, for once it does seem like the year of wayland
Debian Gnome has had it as default since 2019.
Just waiting on kde 6.1 for remote input so input leap can work
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.
You need xdg-desktop-portal, the desktop portal of your DE and a modern Browser.
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.
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.
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.
You can also force apps to use Wayland via environment variables.
ELECTRON_ENABLE_WAYLAND=1 appHowever since no one tests it I’ve found them to be really buggy. Hence why I suggested just using the web app.
Can you give some details about this? I can’t find anything online about it.
Thanks, I got it running under Wayland with that (xeyes doesn’t show it) but screenshare still isn’t working. That’s okay, I’ll try again next year
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.
Looks like it’s a known bug on Slack’s end that’s known for 1.5 years but now is “actively investigated” as of 8 days ago.
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.
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.
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.
Yes the duplicate portals are a mess. On Signal desktop there are 4 portal requests and they all say something different.
missing a mountain of accessibility tools
Like?
If there is something missing, add it either as an issue or a PR in the project.
https://github.com/mpsq/arewewaylandyet
It would help your case when saying that it’s not ready. It might also inspire people to fix it if they see something that is missing.
I still use X11 in my work computer because I need keepassxc to auto-type password to non-web programs.
