←back to thread

Wayland Nvidia

(kextcache.com)
64 points breve | 5 comments | 04 Dec 25 10:00 UTC | HN request time: 0s | source
Show context
superkuh ◴[08 Dec 25 15:33 UTC] No.46193426[source]▶
To be clearer, as each wayland desktop pretty much creates their own incompatible wayland compositor (because wayland protocol is minimal and not feature complete) this is just a guide to fixing the hyperland broken wayland desktop. Not all waylands' broken desktops.
replies(1): >>46193496 #
1. ChocolateGod ◴[08 Dec 25 15:38 UTC] No.46193496[source]▶
What protocol is missing from Wayland?

Yes Wayland doesn't have a printer protocol like Xorg, I know.

replies(3): >>46194197 #>>46195051 #>>46217996 #
2. singron ◴[08 Dec 25 16:24 UTC] No.46194197[source]▶
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/t...

This is an incomplete list of protocols that aren't part of core Wayland. Compositors implement additional protocols that aren't even part of this process (e.g. wlr-screencopy-unstable). See the wlroota protocols here: https://gitlab.freedesktop.org/wlroots/wlroots/-/tree/master...

replies(1): >>46194380 #
3. ChocolateGod ◴[08 Dec 25 16:37 UTC] No.46194380[source]▶
Right but there's the xdg-portal for screen capture which runs through Pipewire and supports sand-boxing (because its negotiated over dbus), which all the main compositors support.

Just because a protocol isn't part of Wayland, doesn't mean a standard protocol does not exists.

4. ◴[08 Dec 25 17:28 UTC] No.46195051[source]▶
5. superkuh ◴[10 Dec 25 14:20 UTC] No.46217996[source]▶
The big ones missing for me are accessibility support (ie, screen readers) and mouse/keyboard input support for basic things like keyboard sharing.