this post was submitted on 18 Sep 2023
213 points (94.2% liked)
Linux
48078 readers
1034 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Can someone debunk this please? It feels like something is overlooked here
They got all of the basic facts right and their general experience mostly mirrors my own, though in my case the majority of problems encountered apply to Wayland in general and are rarely compositor-specific. That is to say that I can usually Google "[APP]" [FEATURE] not working "Wayland" and find people from a variety of different Wayland compositors all experiencing the same thing[^1]. Maybe I just got lucky when I chose my specific compositor?
In fact, despite being on Wayland for about a year now, the only compositor-specific issue I've ever encountered is a broken controller configuration overlay when using Steam's Big Picture Mode. It's actually super frustrating because I have absolutely no idea if it's an issue specific to my compositor, wl-roots, or something unique about my configuration. All I really know is that it works correctly if I launch Steam in a nested gamescope compositor, so it's not a bug in the protocol nor xwayland.
[^1]: Some recent examples: broken Steam Controller cursor, busted SDL in TF2, Invisible Emacs cursor
Thanks for sharing your experience. If the majority of issues are Wayland-wide right now instead of compositor-specific, then that is good in my opinion. These issues get fixed once at the protocol level and are then solved for everyone. Compositors should principally just work, given that they implemented the protocol correctly.
Not all protocol-level fixes are implemented. Example: protocol-level screen sharing. There is extension for this, but kde and gnome use pipewire instead. Basically it is X11 all over again, but worse.
Why are they not using the protocol-level solution, is the pipewire way just simpler to implement? Also, why is the screen sharing fix just an extension and not part of the core protocol?
Dunno. wlr-export-dmabuf-unstable-v1 exists for a while. And wlr-screencopy-unstable-v1. Last one implemented in Sway and Mir.
Kde uses kde-zkde-screencast-unstable-v1 which requires pipewire for some reason and Gnome seems to use unregistered extension.
GNOME and KDE both support the desktop-agnostic xdg-desktop-portals which provide general desktop APIs and that's what most DEs are now converging. The portals including screensharing, input emulation and much more. The problem is that sway/wlroots doesn't want to support it as they're somehow vehemently against a D-bus dependency