Think twice about Wayland. It breaks everything!

Wayland.md

Think twice before abandoning Xorg. Wayland breaks everything!

Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.

Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.

The Wayland project seems to operate like they were starting a greenfield project, whereas at the same time they try to position Wayland as "the X11 successor", which would clearly require a lot of thought about not breaking, or at least providing a smooth upgrade path for, existing software.

In fact, it is merely an incompatible alternative, and not even one that has (nor wants to have) feature parity (missing features). And unlike X11 (the X Window System), Wayland protocol designers actively avoid the concept of "windows" (making up incomprehensible words like "xdg_toplevel" instead).

DO NOT USE A WAYLAND SESSION! Let Wayland not destroy everything and then have other people fix the damage it caused. Or force more Red Hat/Gnome components (glib, Portals, Pipewire) on everyone!

Please add more examples to the list.

Wayland seems to be made by people who do not care for existing software. They assume everyone is happy to either rewrite everything or to just use Gnome on Linux (rather than, say, twm with ROX Filer on NetBSD).

Edit: When I wrote the above, I didn't really realize what Wayland even was, I just noticed that some distributions (like Fedora) started pushing it onto me and things didn't work properly there. Today I realize that you can't "install Wayland", because unlike Xorg, there is not one "Wayland display server" but actually every desktop envrironment has its own. And maybe "the Wayland folks" don't "only care about Gnome", but then, any fix that is done in Gnome's Wayland implementation isn't automatically going to benefit all users of Wayland-based software, and possibly isn't even the implementation "the Wayland folks" would necessarily recommend.

Edit 12/2023: If something wants to replace X11 for desktop computers (such as professional Unix workstations), then it better support all needed features (and key concepts, like windows) for that use case. That people also have displays on their fridge doesn't matter the least bit in that context of discussion. Let's propose the missing Wayland protocols for full X11 feature parity.

Wayland is broken by design

• A crash in the window manager takes down all running applications
• You cannot run applications as root
• You cannot do a lot of things that you can do in Xorg by design
• There is not one /usr/bin/wayland display server application that is desktop environment agnostic and is used by everyone (unlike with Xorg)
• It offloads a lot of work to each and every window manager. As a result, the same basic features get implemented differently in different window managers, with different behaviors and bugs - so what works on desktop environment A does not necessarily work in desktop environment B (e.g., often you hear that something "works in Wayland", even though it only really works on Gnome and KDE, not in all Wayland implementations). This summarizes it very well: https://gitlab.freedesktop.org/wayland/wayland/-/issues/233

Apparently the Wayland project doesn't even want to be "X.org 2.0", and doesn't want to provide a commonly used implementation of a compositor that could be used by everyone: https://gitlab.freedesktop.org/wayland/wayland/-/issues/233. Yet this would imho be required if they want to make it into a worthwile "successor" that would have any chance of ever fixing the many Wayland issues at the core.

Wayland breaks screen recording applications

• MaartenBaert/ssr#431 ❌ broken since 24 Jan 2016, no resolution ("I guess they use a non-standard GNOME interface for this")
• https://github.com/mhsabbagh/green-recorder ❌ ("I am no longer interested in working with things like ffmpeg/wayland/GNOME's screencaster or solving the issues related to them or why they don't work")
• vkohaupt/vokoscreenNG#51 ❌ broken since at least 7 Mar 2020. ("I have now decided that there will be no Wayland support for the time being. Reason, there is no budget for it. Let's see how it looks in a year or two.") - This is the key problem. Wayland breaks everything and then expects others to fix the wreckage it caused on their own expense.
• obsproject/obs-studio#2471 ❌ broken since at least 7 Mar 2020. ("Wayland is unsupported at this time", "There isn't really something that can just be easily changed. Wayland provides no capture APIs")
• There is a workaround for OBS Studio that requires a obs-xdg-portal plugin (which is known to be Red Hat/Flatpak-centric, GNOME-centric, "perhaps" works with other desktops)
• phw/peek#1191 ❌ broken since 14 Jan 2023. Peek, a screen recording tool, has been abandoned by its developerdue to a number of technical challenges, mostly with Gtk and Wayland ("Many of these have to do with how Wayland changed the way applications are being handled")

As of February 2024, screen recording is still broken utterly on Wayland with the vast majority of tools. Proof

Workaround: Find a Wayland compositor that supports the wlr-screencopy-unstable-v1 protocol and use wf-recorder -a. The default compositor in Raspberry Pi OS (Wayfire) does, but the default compositor in Ubuntu doesn't. (That's the worst part of Wayland: Unlike with Xorg, it always depends on the particular Wayand compositor what works and what is broken. Is there even one that supports everything?)

Wayland breaks screen sharing applications

• jitsi/jitsi-meet#2350 ❌ broken since 3 Jan 2018
• jitsi/jitsi-meet#6389 ❌ broken since 24 Jan 2016 ("Closing since there is nothing we can do from the Jitsi Meet side.") See? Wayland breaks stuff and leaves application developers helpless and unable to fix the breakage, even if they wanted.

NOTE: As of November 2023, screen sharing in Chromium using Jitsi Meet is still utterly broken, both in Raspberry Pi OS Desktop, and in a KDE Plasma installation, albeit with different behavior. Note that Pipewire, Portals and whatnot are installed, and even with them it does not work.

• raspberrypi/bookworm-feedback#149 (comment) ❌ broken since at least Nov 17, 2023 ("window sharing not being available in wlroots derived compositors (such as wayfire)")
• flathub/us.zoom.Zoom#22 Zoom ❌ broken since at least 4 Jan 2019. ("Can not start share, we only support wayland on GNOME with Ubuntu (17, 18), Fedora (25 to 29), Debian 9, openSUSE Leap 15, Arch Linux"). No word about non-GNOME!
• https://community.zoom.com/t5/Meetings/Screensharing-only-works-on-GNOME-wayland-when-it-should-work-on/m-p/64823 Zoom ❌ Still broken as of 24 Jun 2022. ("... we only support Wayland on Gnome with Ubuntu 17 and above, Fedora 25 and above, Debian 9 and above ...")
• probonopd/Zoom.AppImage#8 ❌ broken since 1 Oct 2022 Zoom: "You need PulseAudio 1.0 and above to support audio share" on a system that uses pipewire-pulseaudio

Wayland breaks automation software

sudo pkg install py37-autokey

This is an X11 application, and as such will not function 100% on 
distributions that default to using Wayland instead of Xorg.

Wayland breaks Gnome-Global-AppMenu (global menus for Gnome)

• https://gitlab.com/lestcape/Gnome-Global-AppMenu/-/issues/116 ❌ broken since 24 Aug 2018 ("because the lack of the Gtk+ Wayland support for the Global Menu")

• https://bugs.kde.org/show_bug.cgi?id=424485 ❌ Still broken as of late 2023 ("I am also still not seeing GTK global menus on wayland. They appear on the applications themselves, wasting a lot of space.")

Wayland broke global menus with KDE platformplugin

• https://blog.broulik.de/2016/10/global-menus-returning/ ("it uses global window IDs, which don’t exist in a Wayland world... no global menu on Wayland, I thought, not without significant re-engineering effort"). KDE had to do additional work to work around it. And it still did not work:

• https://bugs.kde.org/show_bug.cgi?id=385880 ("When using the Plasma-Wayland session, the global menu does not work.")

Good news: According to this report global menus now work with KDE platformplugin as of 4/2022

Wayland breaks global menus with non-KDE Qt platformplugins

• https://blog.broulik.de/2016/10/global-menus-returning/ ❌ broke non-KDE platformplugins. As a result, global menus now need _KDE_NET_WM_APPMENU_OBJECT_PATH which only the KDE platformplugin sets, leaving everyone else in the dark

Wayland breaks AppImages that don't ship a special Wayland Qt plugin

• https://blog.martin-graesslin.com/blog/2018/03/unsetting-qt_qpa_platform-environment-variable-by-default/ ❌ broke AppImages that don't ship a special Wayland Qt plugin. "This affects proprietary applications, FLOSS applications bundled as appimages, FLOSS applications bundled as flatpaks and not distributed by KDE and even the Qt installer itself. In my opinion this is a showstopper for running a Wayland session." However, there is a workaround: "AppImages which ship just the XCB plugin will automatically fallback to running in xwayland mode" (see below).

Wayland breaks Redshift

• https://wiki.archlinux.org/index.php/redshift ❌ broken ("Redshift does not support Wayland since it offers no way to adjust the color temperature")

Update 2023: Some Wayland compositors (such as Wayfire) now support wlr_gamma_control_unstable_v1, see https://github.com/WayfireWM/wayfire/wiki/Tutorial#configuring-wayfire and jonls/redshift#663. Does it work in all Wayland compositors though?

Wayland breaks global hotkeys

• albertlauncher/albert#309 ❌ broken since 7 Jan 2017 ("This is a security measure, but has the side effect of preventing applications from registering their own global hotkeys") YouTube video by René Rebe

Wayland does not work for Xfce?

See below.

Wayland does not work properly on NVidia hardware?

Apparently Wayland relies on nouveau drivers for NVidia hardware. The nouveau driver has been giving unsatisfactory performance since its inception. Even clicking on the application starter icon in Gnome results in a stuttery animation. Only the proprietary NVidia driver results in full performance.

See below.

Update 2024: The situation might slowly be improving. It remains to be seen whether this will work well also for all existing old Nvidia hardware (that works well in Xorg).

Wayland does not work properly on Intel hardware

• https://cfenollosa.com/blog/fed-up-with-the-mac-i-spent-six-months-with-a-linux-laptop-the-grass-is-not-greener-on-the-other-side.html ❌ broken since at least 02 Apr 2021 ("Screen tearing with the intel driver. Come on. This was solved on xorg and now with Wayland it's back.")

Wayland prevents GUI applications from running as root

• https://bugzilla.redhat.com/show_bug.cgi?id=1274451 ❌ broken since 22 Oct 2015 ("No this will only fix sudo for X11 applications. Running GUI code as root is still a bad idea." I absolutely detest it when software tries to prevent me from doing what some developer thinks is "a bad idea" but did not consider my use case, e.g., running truss for debugging on FreeBSD needs to run the application as root. https://bugzilla.mozilla.org/show_bug.cgi?id=1323302 suggests it is not possible: "These sorts of security considerations are very much the way that "the Linux desktop" is going these days".)

Suggested solution

Wayland is biased toward Linux and breaks BSD

• https://blog.netbsd.org/tnf/entry/wayland_on_netbsd_trials_and ❌ broken since 28 Sep 2020 ("Wayland is written with the assumption of Linux to the extent that every client application tends to #include <linux/input.h> because Wayland's designers didn't see the need to define a OS-neutral way to get mouse button IDs. (...) In general, Wayland is moving away from the modularity, portability, and standardization of the X server. (...) I've decided to take a break from this, since it's a fairly huge undertaking and uphill battle. Right now, X11 combined with a compositor like picom or xcompmgr is the more mature option."

Wayland complicates server-side window decorations

• https://blog.martin-graesslin.com/blog/2018/01/server-side-decorations-and-wayland/ ❌ FUD since at least 27 January 2018 ("I heard that GNOME is currently trying to lobby for all applications implementing client-side decorations. One of the arguments seems to be that CSD is a must on Wayland. " ... "I’m burnt from it and are not interested in it any more.") Server-side window decorations are what make the title bar and buttons of all windows on a system consistent. They are a must have_ for a consistent system, so that applications written e.g., Gtk will not look entirely alien on e.g., a Qt based desktop, and to enforce that developers cannot place random controls into window titles where they do not belong. Client-side decorations, on the other hand, are destroying uniformity and consistency, put additional burden on application and toolkit developers, and allow e.g., GNOME developers to put random controls (that do not belong there) into window titles (like buttons), hence making it more difficult to achieve a uniform look and feel for all applications regardless of the toolkit being used.

Red Hat employee Matthias Clasen ("I work at the Red Hat Desktop team... I am actually a manager there... the people who do the actual work work for me") expicitly stated "Client-side everything" as a principle, even though the protocol doesn't enforce it: "Fonts, Rendering, Nested Windows, Decorations. "It also gives the design more freedom to use the titlebar space, which is something our designers appreciate" (sic). Source

Wayland breaks windows rasing/activating themselves

• https://phabricator.kde.org/D16648#470609 ("Wayland clients can't raise or activate themselves"), ❌ broken since May 27 2019

Wayland breaks RescueTime

• https://help.rescuetime.com/article/117-common-linux-issues ("One of the features of Wayland is that it prevents apps from doing precisely what RescueTime is trying to do—track activity in other windows.") ❌ broken since June 3, 2021

Wayland breaks window managers

Apparently Wayland (at least as implemented in KWin) does not respect EWMH protocols, and breaks other command line tools like wmctrl, xrandr, xprop, etc. Please see the discussion below for details.

Wayland requires JWM, TWM, XDM, IceWM,... to reimplement Xorg-like functionality

• https://gitlab.freedesktop.org/wayland/wayland/-/issues/233

• Screen recording and casting
• Querying of the mouse position, keyboard LED state, active window position or name, moving windows (xdotool, wmctrl)
• Global shortcuts
• System tray
• Input Method support/editor (IME)
• Graphical settings management (i.e. tools like xranrd)
• Fast user switching/multiple graphical sessions
• Session configuration including but not limited to 1) input devices 2) monitors configuration including refresh rate / resolution / scaling / rotation and power saving 3) global shortcuts
• HDR/deep color support
• VRR (variable refresh rate)
• Disabling input devices (xinput alternative)

As it currently stands minor WMs and DEs do not even intend to support Wayland given the sheer complexity of writing all the code required to support the above features. You do not expect JWM, TWM, XDM or even IceWM developers to implement all the featured outlined in ^1.

Wayland breaks _NET_WM_STATE_SKIP_TASKBAR protocol

• https://github.comelectron/electron#33226 ("skipTaskbar has no effect on Wayland. Currently Electron uses _NET_WM_STATE_SKIP_TASKBAR to tell the WM to hide an app from the taskbar, and this works fine on X11 but there's no equivalent mechanism in Wayland." Workarounds are only available for some desktops including GNOME and KDE Plasma.) ❌ broken since March 10, 2022

Wayland breaks NoMachine NX

• https://kb.nomachine.com/TR03S10126?s=wayland ❌ broken since 2021-03-09 ("The session becomes unresponsive once logged-in to the Wayland desktop")

Wayland breaks xclip

xclip is a command line utility that is designed to run on any system with an X11 implementation. It provides an interface to X selections ("the clipboard"). Apparently Wayland isn't compatible to the X11 clipboard either.

• AppImage/AppImageKit#1221 (comment) ❌ broken since 2022-20-15 ("Espanso built for X11 will not work on Wayland due to xclip. Wayland asks for wl-copy")

This is another example that the Wayland requires everyone to change components and take on additional work just because Wayland is incompatible to what we had working for all those years.

Wayland breaks SUDO_ASKPASS

• https://github.com/linuxhw/hw-probe-pyqt5-gui/commit/eb2d6e5145fb8571414bda57676084b7f13b94e5#diff-23cb15995f1502beebb38433bfa83204a5f45b376eaf88e2e41a0d8a1cd44722R290 ❌ broken since 2022-04-09 ("SUDO_ASKPASS doesn't work on Wayland currently, so piping the password")

Wayland breaks X11 atoms

X11 atoms can be used to store information on windows. For example, a file manager might store the path that the window represents in an X11 atom, so that it (and other applications) can know for which paths there are open file manager windows. Wayland is not compatible to X11 atoms, resulting in all software that relies on them to be broken until specifically ported to Wayland (which, in the case of legacy software, may well be never).

Possible workaround (to be verified): Use the (Qt proprietary?) Extended Surface Wayland protocol casually mentioned in https://blog.broulik.de/2016/10/global-menus-returning/ "which allows you to set (and read?) arbitrary properties on a window". Is it the set_generic_property from https://github.com/qt/qtwayland/blob/dev/src/extensions/surface-extension.xml?

Wayland breaks games

Games are developed for X11. And if you run a game on Wayland, performance is subpar due to things like forced vsync. Only recently, some Wayland implementations (like KDE KWin) let you disable that.

Wayland breaks xdotool

(Details to be added; apparently no 1:1 drop-in replacement available?)

Wayland breaks xkill

xkill (which I use on a regular basis) does not work with Wayland applications.

What is the equivalent for Wayland applications?

Wayland breaks screensavers

Is it true that Wayland also breaks screensavers? https://www.jwz.org/blog/2023/09/wayland-and-screen-savers/

Wayland breaks setting the window position

Other platforms (Windows, Mac, other destop environments) can set the window position on the screen, so all cross-platform toolkits and applications expect to do the same on Wayland, but Wayland can't (doesn't want to) do it.

• PCSX2/pcsx2#10179 PCX2 (Playstation 2 Emulator) ❌ broken since 2023-10-25 ("Disables Wayland, it's super broken/buggy in basically every scenario. KDE isn't too buggy, GNOME is a complete disaster.")

Wayland breaks color mangement

Apparently color management as of 2023 (well over a decade of Wayland development) is still in the early "thinking" stage, all the while Wayland is already being pushed on people as if it was a "X11 successor".

https://gitlab.freedesktop.org/pq/color-and-hdr/-/blob/main/doc/color-management-model.md

Wayland breaks DRM leasing

According to Valve, "DRM leasing is the process which allows SteamVR to take control of your VR headset's display in order to present low-latency VR content".

• "Unfortunately not all Wayland compositors support DRM leasing" https://help.steampowered.com/en/faqs/view/18A4-1E10-8A94-3DDA - "not all" highlights one of the fundamental problems with Wayland - there is fragmentation

Wayland breaks In-home Streaming

• ValveSoftware/steam-for-linux#6148 ❌ broken since 2019-03-17

Wayland breaks NetWM

Extended Window Manager Hints, a.k.a. NetWM, is an X Window System standard for the communication between window managers and applications

Wayland breaks window icons

• Wayland breaks window icons when no .desktop files are used: Seemingly Wayland requires developers to use the xdg-shell protocol, which in turn requires developers to use reverse-DNS application IDs and set_app_id, which causes the icon to be loaded from the .desktop file. This is serious breakage, as not all desktop environments (for good reasons) use .desktop files. A display server should have no business in this, as this belongs into the domain of the desktop environment. https://community.kde.org/Guidelines_and_HOWTOs/Wayland_Porting_Notes#Application_Icon, https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/52 ❌ broken since 2021-06-21

• Qt setWindowIcon has no effect on KDE/Wayland https://bugreports.qt.io/browse/QTBUG-101427 ("Resolution: Out of scope", meaning it cannot be fixed in Qt, "Using QT_QPA_PLATFORM=xcb works, though", meaning that if you disable Wayland then it works) ❌ broken since 2022-03-03

• LibrePCB developer: "Btw it's just one of several problems we have with Wayland, therefore we still enforce LibrePCB to run with XWayland. It's a shame, but I feel totally helpless against such decisions made by Wayland and using XWayland is the only reasonable option (which even works perfectly fine)..." https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/52#note_2155885

Update 6/2024: Looks like this will get unbroken thanks to xdg_toplevel_icon_manager_v1, so that QWindow::setIcon will work again. If, and that's a big if, all compositors will support it. At least KDE is on it.

Wayland breaks drag and drop

• On Raspberry Pi OS (which is running a Wayland session by default), dragging a file out of a zip file onto the desktop fails with "XDirectSave failed."
• The same seems to be true in Gnome: https://discourse.gnome.org/t/xdnddirectsave-and-wayland/2954

Wayland breaks ./windowmanager --replace

• Many window managers have a --replace argument, but Wayland compositors break this convention.

Workarounds

• Users: Refuse to use Wayland sessions. Uninstall desktop environments/Linux distributions that only ship Wayland sessions. Avoid Wayland-only applications (such as PreSonus Studio One) (potential workaround: run in https://github.com/cage-kiosk/cage)
• Application developers: Enforce running applications on X11/XWayland (like LibrePCB does as of 11/2023)

Examples of Wayland being forced on users

This is exactly the kind of behavior this gist seeks to prevent.

• Asahi Linux enforces Wayland for ARM-based Macs: https://social.treehouse.systems/@marcan/110354541574112092
• Fedora enforces Wayland for KDE Plasma: https://fedoraproject.org/wiki/Changes/KDE_Plasma_6#Why_drop_the_X11_session_with_the_Plasma_6_upgrade?
• Red Hat enforces Wayland for RHEL:https://www.redhat.com/de/blog/rhel-10-plans-wayland-and-xorg-server

History

• 2008: Wayland was started by krh (while at Red Hat)
• End of 2012: Wayland 1.0
• Early 2013: GNOME begins Wayland porting

Source: "Where's Wayland?" by Matthias Clasen - Flock 2014

A decade later... Red Hat wants to force Wayland upon everyone, removing support for Xorg

References

• Dudemanguy's Musings, Wayland Isn't Going to Save The Linux Desktop
• Chris Titus Tech: Wayland vs Xorg https://www.youtube.com/watch?v=U_MBJcD3SFI
• tildearrow: did somebody say "anti-Wayland horseshit"?
• pcsx2: CI/Linux: Disable Wayland and spring cleaning
• Testing SCREEN RECORDERS on Linux Mint Wayland
• ProtonPenguin: Wayland Breaks Everything

At what point is modifying someone elses linux distro more work than just building it yourself how you want?

I mean if you are using arch, then of course you need to configure everything, but if it is a fedora, for example, then I guess, everything (including vcam) should work out of the box.

At what point do you just decide you have to make so many changes so many compromises to get a working system that by the time you do it all it is a very different beast from stock whatever do you just have to throw your hands up and say it would be so much easier if it was just built or configured this way from the start?

I mean if you are using arch, then of course you need to configure everything, but if it is a fedora, for example, then I guess, everything (including vcam) should work out of the box.

Fedora got that super annoying apparmor thingy that you need to do a Dr. Dr. Professor for.

I wish you had quoted my final edit cause that is the core of the two mashed up but related thoughts.

Fedora works out the box if you use a livecd and that livecd works out the box and you never update it unless it is broken out the box then an update might fix it but bust 10 other things. There is a fuckin reason I want off the Fedora Train.. It's gonna crash and when it does no one will care because it didn't crash for them, yet.

Fedora doesn't test everything they produce. They test only critical-paths. Yes, I am aware of what the comment says. It was written years ago.

  <!--
    Note: The critical-path-* groups are used to identify the packages
    that are critical to the health of the distro. For details see:
    https://fedoraproject.org/wiki/Critical_path_package
    @core is also considered part of the Critical Path.
  -->
  <group>
    <id>critical-path-anaconda</id>
    <_name>Critical Path (anaconda)</_name>
    <_description>A set of packages that provide the Critical Path functionality for installing Fedora with anaconda</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">anaconda</packagereq>
      <packagereq type="mandatory">anaconda-install-env-deps</packagereq>
      <packagereq type="mandatory">anaconda-webui</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-apps</id>
    <_name>Critical Path (Applications)</_name>
    <_description>A set of applications that are considered critical path</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="default">firefox</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-base</id>
    <_name>Critical Path (Base)</_name>
    <_description>A set of packages that provide the shared platform for Critical Path functionality on all Fedora spins</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <!--
        @core is already in the critical path, there is no need to duplicate things from @core here
      -->
      <packagereq type="mandatory">dbus-broker</packagereq>
      <packagereq type="mandatory">dracut</packagereq>
      <packagereq type="mandatory">initial-setup</packagereq>
      <packagereq type="mandatory">kernel</packagereq>
      <packagereq type="mandatory">NetworkManager</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-build</id>
    <_name>Critical Path (Build)</_name>
    <_description>A set of packages that provide the Critical Path functionality for building Fedora packages</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">gcc-c++</packagereq>
      <packagereq type="mandatory">mock</packagereq>
      <packagereq type="mandatory">mock-core-configs</packagereq>
      <packagereq type="mandatory">redhat-rpm-config</packagereq>
      <packagereq type="mandatory">rpm-build</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-compose</id>
    <_name>Critical Path (Compose)</_name>
    <_description>A set of packages that provide the Critical Path functionality for building Fedora deliverables</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">gnome-kiosk</packagereq>
      <packagereq type="mandatory">kiwi-cli</packagereq>
      <packagereq type="mandatory">kiwi-systemdeps</packagereq>
      <packagereq type="mandatory">livesys-scripts</packagereq>
      <packagereq type="mandatory">lorax</packagereq>
      <packagereq type="mandatory">mock</packagereq>
      <packagereq type="mandatory">mock-core-configs</packagereq>
      <packagereq type="mandatory">pungi</packagereq>
      <packagereq type="mandatory">selinux-policy</packagereq>
      <packagereq type="mandatory">setup</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-deepin-desktop</id>
    <_name>Critical Path (Deepin desktop)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the Deepin desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">deepin-desktop</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-gnome</id>
    <_name>Critical Path (GNOME)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the GNOME desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">bash-color-prompt</packagereq>
      <packagereq type="mandatory">dconf</packagereq>
      <packagereq type="mandatory">gdm</packagereq>
      <packagereq type="mandatory">gnome-classic-session</packagereq>
      <packagereq type="mandatory">gnome-control-center</packagereq>
      <packagereq type="mandatory">gnome-initial-setup</packagereq>
      <packagereq type="mandatory">gnome-shell</packagereq>
      <packagereq type="mandatory">gnome-terminal</packagereq>
      <packagereq type="mandatory">gvfs-fuse</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">xorg-x11-drv-amdgpu</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">xorg-x11-drv-ati</packagereq>
      <packagereq type="mandatory">xorg-x11-drv-evdev</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">xorg-x11-drv-fbdev</packagereq>
      <packagereq arch="x86_64" type="mandatory">xorg-x11-drv-intel</packagereq>
      <packagereq type="mandatory">xorg-x11-drv-libinput</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">xorg-x11-drv-nouveau</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">xorg-x11-drv-qxl</packagereq>
      <packagereq arch="x86_64" type="mandatory">xorg-x11-drv-vesa</packagereq>
      <packagereq type="mandatory">xorg-x11-server-Xorg</packagereq>
      <packagereq type="mandatory">xorg-x11-xauth</packagereq>
      <packagereq type="mandatory">xorg-x11-xinit</packagereq>
      <packagereq type="default">avahi</packagereq>
      <packagereq type="default">gnome-bluetooth</packagereq>
      <packagereq type="default">gnome-session-xsession</packagereq>
      <packagereq type="default">gnome-software</packagereq>
      <packagereq type="default">nautilus</packagereq>
      <packagereq type="default">toolbox</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-kde</id>
    <_name>Critical Path (KDE)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the KDE desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">bluedevil</packagereq>
      <packagereq type="mandatory">kactivitymanagerd</packagereq>
      <packagereq type="mandatory">kdecoration</packagereq>
      <packagereq type="mandatory">kinfocenter</packagereq>
      <packagereq type="mandatory">kscreen</packagereq>
      <packagereq type="mandatory">kscreenlocker</packagereq>
      <packagereq type="mandatory">kwayland-integration</packagereq>
      <packagereq type="mandatory">kwin</packagereq>
      <packagereq type="mandatory">layer-shell-qt</packagereq>
      <packagereq type="mandatory">plasma-breeze</packagereq>
      <packagereq type="mandatory">plasma-desktop</packagereq>
      <packagereq type="mandatory">plasma-discover</packagereq>
      <packagereq type="mandatory">plasma-integration</packagereq>
      <packagereq type="mandatory">plasma-nm</packagereq>
      <packagereq type="mandatory">plasma-systemsettings</packagereq>
      <packagereq type="mandatory">plasma-thunderbolt</packagereq>
      <packagereq type="mandatory">plasma-workspace</packagereq>
      <packagereq type="mandatory">polkit-kde</packagereq>
      <packagereq type="mandatory">qt6-qtwayland</packagereq>
      <packagereq type="mandatory">sddm</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-lxde</id>
    <_name>Critical Path (LXDE)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the LXDE desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">lxde-common</packagereq>
      <!-- specify this because otherwise xfce4-notifyd wins -->
      <packagereq type="default">notification-daemon</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-lxqt</id>
    <_name>Critical Path (LXQt)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the LXQt desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">lxqt-session</packagereq>
      <!-- specify this because otherwise xfce4-notifyd wins -->
      <packagereq type="default">notification-daemon</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-server</id>
    <_name>Critical Path (Server)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the Server edition</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq>bind-dyndb-ldap</packagereq>
      <packagereq>cockpit</packagereq>
      <packagereq>freeipa-server</packagereq>
      <packagereq>freeipa-server-dns</packagereq>
      <packagereq>freeipa-server-trust-ad</packagereq>
      <packagereq>opendnssec</packagereq>
      <packagereq>postgresql</packagereq>
      <packagereq>realmd</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-standard</id>
    <_name>Critical Path (standard)</_name>
    <!-- not all deliverables include @standard, critical-path-base only includes stuff from @base -->
    <_description>A set of packages that relate to Critical Path functionality and are in standard but not base</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">bash-color-prompt</packagereq>
      <packagereq arch="aarch64,ppc64le,x86_64" type="mandatory">fprintd-pam</packagereq>
    </packagelist>
  </group>
  <group>
    <id>critical-path-xfce</id>
    <_name>Critical Path (Xfce)</_name>
    <_description>A set of packages that provide the Critical Path functionality for the Xfce desktop</_description>
    <default>false</default>
    <uservisible>false</uservisible>
    <packagelist>
      <packagereq type="mandatory">xfce4-session</packagereq>
      <packagereq type="mandatory">xfce4-settings</packagereq>
    </packagelist>
  </group>

@shvedes

Yes, Wayland has problems, but. As I said above, this is a very rapidly developing project, and I hope all your problems will be fixed soon.

Very rapidly developing project?
How many years has it been? 16? Wayland is almost legal in that sense of age.
(if we compare since public release, x only has only 8 years ~> sure it has more non-public releases, but all the work public actually uses has been made in some 10-12 years)

I wish you had quoted my final edit cause that is the core of the two mashed up but related thoughts.

Fedora works out the box if you use a livecd and that livecd works out the box and you never update it unless it is broken out the box then an update might fix it but bust 10 other things. There is a fuckin reason I want off the Fedora Train.. It's gonna crash and when it does no one will care because it didn't crash for them, yet.

To be honest, I don't know what are you talking about. In my case fedora working flawlessly, no matter what machine I run it on.

@shvedes

Yes, Wayland has problems, but. As I said above, this is a very rapidly developing project, and I hope all your problems will be fixed soon.

Very rapidly developing project? How many years has it been? 16? Wayland is almost legal in that sense of age. (if we compare since public release, x only has only 8 years ~> sure it has more non-public releases, but all the work public actually uses has been made in some 10-12 years)

I said that this project has been developing very fast lately. When I say lately, I mean the last few years. For example, two years ago I definitely wouldn't have been able to use it. I tried, but there were too many issues that weren't compatible with my use case, but now it's a daily driver for me. I draw conclusions from my experience

I build mid-tier AMD machines with AMD Graphics. This is pre-pandemic mid-tier with a post-pandemic video card the previous one was RX560. Tell me why Wayland doesn't work properly. WHy am I getting 3d graphical glitches that look like a flat surface with a "camera" pointing at its surface. Why do I get blocky glitchy artifacts on Gnome and KDE on secondary monitors. Why does it run like shit, freeze, stutter, wholey and globally hard lock up to the point where I can't switch VTs. X11 used to do this 20 years ago and typically doesn't anymore without a direct reason behind it.. With wayland it could be anything everything and nothing because the other person doesn't have those issues or is simply lying their ass off because if they don't they will be shat on and blackballed if not outright cancelled.

So let me say what other people refuse to outright and matter of fact.

Wayland.. is not good enough.

I build mid-tier AMD machines with AMD Graphics. This is pre-pandemic mid-tier with a post-pandemic video card the previous one was RX560. Tell me why Wayland doesn't work properly. WHy am I getting 3d graphical glitches that look like a flat surface with a "camera" pointing at its surface. Why do I get blocky glitchy artifacts on Gnome and KDE on secondary monitors. Why does it run like shit, freeze, stutter, wholey and globally hard lock up to the point where I can't switch VTs. X11 used to do this 20 years ago and typically doesn't anymore without a direct reason behind it.. With wayland it could be anything everything and nothing because the other person doesn't have those issues or is simply lying their ass off because if they don't they will be shat on and blackballed if not outright cancelled.

So let me say what other people refuse to outright and matter of fact.

Wayland.. is not good enough.

Honestly, I don't know why you have so many problems. The only thing I would probably like to see soon is a fully functioning driver for Wine, global shortcuts and native apps (krita, gimp, etc). Also, the problem of scaling XWayland applications lies with XWayland, not with Wayland itself. Everything else has been working fine for me since switching to Wayland, no matter what systems and DE I test.

And it seems to me that our dialogue is developing into a quarrel, which I do not want. Don't get me wrong, I'm not a fanatic, I use XOrg on my laptop because it uses less RAM, which is important to me.

And I am using 6700XT, which can make sense for some reason, idk, since for different generations of GPU the driver can be used differently.

I have an 6650XT.

I have an 6650XT.

Well, then as I said I don't know why you facing so many graphical problems, and, unfortunately, I can't help you.

I have an 6650XT.

Well, then as I said I don't know why you facing so many graphical problems, and, unfortunately, I can't help you.

And this is why I have to take matters into my own hands and be a real linux user and do shit my self. That includes my decisions as well and one is to favor if not exclusively use x11 and specific reliable-enough tech.

not sure what's funnier, watching wayland-protocols fighting because of GNOME being petards, boomers fighting over why we should keep 40 yo software around or watching both display servers have their own specific issues, death by a thousand paper-cuts am I right?

not sure what's funnier, watching wayland-protocols fighting because of GNOME being petards, boomers fighting over why we should keep 40 yo software around or watching both display servers have their own specific issues, death by a thousand paper-cuts am I right?

Definitely

@severtheskyline

boomers fighting over why we should keep 40 yo software around

Click 'Unsubscribe' at the top of this gist, young grasshopper.

not sure what's funnier, watching wayland-protocols fighting because of GNOME being petards, boomers fighting over why we should keep 40 yo software around or watching both display servers have their own specific issues, death by a thousand paper-cuts am I right?

Yo! I am too young to be a boomer.

The only conflict for me is when people think they can convince me to give up a goal I have set forth. In this I must proceed regardless else I will just sit around and do nothing for another 2 years. No opposition shall stand against me or be the sole reason any of my endeavors would fail.

Why am I still getting messages for this? I thought I unsubscribed. Anyways, please stop. For your health.

I can't even unsubscribe. I guess I'll get annoyed forever.

@fgclue That is your destiny for being so toxic

? ? ?
How do I unsubscribe twice?? It says I'm not subscribed. Yet me still recieve this.
Stay suffer. too. Since you responded you have too suffer too

https://www.youtube.com/watch?v=qkTUxHUc7PE

? ? ? How do I unsubscribe twice?? It says I'm not subscribed. Yet me still recieve this. Stay suffer. too. Since you responded you have too suffer too

Likely because you got tagged.

I can't even unsubscribe. I guess I'll get annoyed forever.

@fgclue Mail filter = good boiiii 🐶📬✨🔥

@fgclue Did you try turning it off and turning it back on?

For those who think screen sharing works on Wayland - can you explain why it doesn't here?
raspberrypi/bookworm-feedback#149 (comment)

For those who think screen sharing works on Wayland - can you explain why it doesn't here? raspberrypi/bookworm-feedback#149 (comment)

can you explain why it works for me?

There is currently no official wayland protocol for screen sharing. Mostly because gnome insists of that not being a wayland protocol in the first place but a dbus interface using pipewire. wlroots based compositors do have an implementation for that via xdg-desktop-portal-wlr which uses a private wayland protocol to talk to the compositor but that one does only support capturing outputs.

There is a pending official protocol at https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124. It has to be merged + implemented in wlroots (including the toplevel image source) + implemented in the xdg-desktop-portal-wlr bridge + implemented in the compositor.

If you want to capture single windows you might be better off using X11.

The deeper one digs into this, the more question marks come up.

A Raspberry Pi developer responded:

We don't officially support gnome so I can't spend much time digging into this, but it looks like what's going wrong is the dmabuf buffers being shared by GNOME are in a GPU tiled format (which is more efficient for the GPU to read and write). But webrtc doesn't know how to read these formats, so it gets all garbled. [...] it might help to uninstall xdg-desktop-portal-wlr (which implements screen sharing on wlroots-based compositors like labwc and wayfire) and install xdg-desktop-portal-gnome (which implements screen sharing for gnome). Otherwise, if you can convince gnome to use software rendering instead of hw-accelerated (i have no idea how) then that might fix it since that will use vanilla linear buffer formats.

Apparently different desktop environments using Wayland now implement "how the rendering works internally" differently, using different pixel formats, some using GPU rendering and others software rendering. As a result, it seems that some desktop environments need to have their own incompatible versions of some "xdg" (didn't this stand for cross desktop?) portals, which apparently can't even be installed alongside each other.

In practice, does this mean that we are now at a point where due to every desktop environment doing their own thing you can't have multiple desktop environments installed alongside each other and everything just works?

Possibly ext-screencopy-v1 and ext-image-source-v1 could unbreak this as Consolatis suggests, but as so often there is an endless discussion going on since years in the merge request, someone even asked

So we have 2 ACKs and 2 implementations. Now what?

...and nothing happened.

can you explain why it works for me?

Probably because you either a) used some preconfigured default combination of Wayland compositor, desktop environment, portals, Pipewire etc. and/or b) because you were lucky. Usually as soon as you try to mix and match (as we like to do in Unix land), things are a broken mess, as evidenced above.

As a result, it seems that some desktop environments need to have their own incompatible versions of some "xdg" (didn't this stand for cross desktop?) portals, which apparently can't even be installed alongside each other.

The xdg-desktop-portal interfaces are designed such that the interface itself is the same for all clients but there are different implementations for the service providing part. The implementations can be installed alongside each other, AFAIR the XDG_CURRENT_DESKTOP env var is used to select the relevant implementation per interface which can be overwritten by the user.

can you explain why it works for me?

Probably because you either a) used some preconfigured default combination of Wayland compositor, desktop environment, portals, Pipewire etc. and/or b) because you were lucky. Usually as soon as you try to mix and match (as we like to do in Unix land), things are a broken mess, as evidenced above.

Its a.
Hyprland re-implemented various parts usually provided by wlroots and implements some own hyprland private wayland protocols + its own xdg-desktop-portal. That has benefits for users in case of screensharing and global shortcuts as its using the dbus interface abstraction. On the flip side hyprland is not working with other compositors on common wayland protocols to solve this mess.

get real

Yesterday I tried sway again. Sway keeps crashing when I play Dolphin-Emu. Of course, I did report it. But so far, not a solid experience.

I stuck a second GPU in my rig to offload GPU encoding to and free up my main GPU for display, now Wayland won't even start up. 🤷 I'm on mint anyway, so i can just keep using X11 which doesn't seem to care that I have a second GPU, and even lets me use it as a pass-through display device.
It's generally faster anyway, i saw 3D applications run 50% slower under wayland due to the overhead of xwayland because the vast majority of applications don't yet support it anyway.

I'm happy at least the mint developers are adding it as a optional login item instead of a 'you must use this now because reasons', I hope it stays that way until wayland actually reaches feature parity in another 15+ years

Apparently different desktop environments using Wayland now implement "how the rendering works internally" differently, using different pixel formats, some using GPU rendering and others software rendering. As a result, it seems that some desktop environments need to have their own incompatible versions of some "xdg" (didn't this stand for cross desktop?) portals, which apparently can't even be installed alongside each other.

I've been running into an issue with Davinci Resolve where the video previews get shown in the wrong buffer format. Resolve doesn't run as a native Wayland application and the issue occurs when using it through XWayland and X11. It's not related to the compositor or display server at all, it's actually has to do with Intel's Mesa driver and Intel's Compute Runtime not negotiating which buffer format they're sending to each other.

Different things support different texture formats and that can always become an issue when sharing buffers between things regardless of the method of sharing they're using. In this case, Debian Bookworm was providing a version of Mutter that was 3 (almost 4) version out of date and when the user upgraded to it, the issue was fixed.

I get that you want to mix and match things but that, as a rule, can't always work. That's not a Wayland problem, it's just a reality of how software development works.

Why is it working better in the X11 ecosystem then? Maybe it has to do with the fact that everyone basically uses the same implementation rather than reinventing the wheel (and bugs) time and again.

@probonopd

Why is it working better in the X11 ecosystem then? Maybe it has to do with the fact that everyone basically uses the same implementation rather than reinventing the wheel (and bugs) time and again.

Exactly! This is why we should all settle on a single Linux distro and implement world peace!

Why is it working better in the X11 ecosystem then? Maybe it has to do with the fact that everyone basically uses the same implementation rather than reinventing the wheel (and bugs) time and again.

I actually tested Davinci Resolve and its god awful because it does not communicate to the user !

By default, you require a license to have video previews of mp4 footage. But it doesnt tell you!
It doesnt tell you to convert it so that you can work with it. Then, when you want the previews, and the permission to edit it, you need the studio license for 329 EUR. Thats something you find out on the forums in the abyss...

Then, when you bought it, you edit your file, you see that AAC is not a supported codec.
You'd need to convert that... too. And thats something it doesnt tell you either.

Thats when I did the refund, and I didn't get it until I opened a PayPal case cause the support line didn't answer me.

Kdenlive works just fine in Wayland, at least on my system it does. No license or purchase required, no paid "optional" extras. No online currency in my case anyway so I would not have a choice anyway to use payware.

Kdenlive works just fine in Wayland, at least on my system it does. No license or purchase required, no paid "optional" extras. No online currency in my case anyway so I would not have a choice anyway to use payware.

Yep! And thats exactly what I changed to!

@AndreiSva

Exactly! This is why we should all settle on a single Linux distro and implement world peace!

No we should all be compiling our own systems, helping each other, not looking to a specific distro-leader to save us. They won't. Neither will I but I will try to cover as many as I can.

@mattatobin

@AndreiSva

Exactly! This is why we should all settle on a single Linux distro and implement world peace!

No we should all be compiling our own systems, helping each other, not looking to a specific distro-leader to save us. They won't. Neither will I but I will try to cover as many as I can.

You can't reasonably expect any non-developer to do that.

Linux wasn't designed for non-developers. That is why all these crap changes are happening. Also software development should be a pre-req for using a computer. So as a user you aren't trapped by whatever others give you.

root@localhost:~# apt-file search /usr/bin/Xorg
xserver-xorg-core: /usr/bin/Xorg          
root@localhost:~# apt-file search /usr/bin/Wayland
root@localhost:~# 

Wayland does not exist. What am I even supposed to boycott? Or install? Or migrate to?

@mattatobin

Also software development should be a pre-req for using a computer. So as a user you aren't trapped by whatever others give you.

Yeah, and you're not eligible to drive a car if you can't fix your Lada from 90s which breaks every 500 meters.

Or your Soviet DYRCHIK: https://www.youtube.com/watch?v=gpTzV_WkXhY

Look, I did not even come here from notifications, just recalled about the thread, like many times before as well, who suggested me to unsubscribe? :P Only a ban from GitHub might help perhaps.

@bodqhrohro While I don't expect everyone to be an expert in everything, I certainly am not. I would agree with a less extreme interpretation. Because you are correct. The extreme modernization of cars have made them extremely difficult if not impossible to service your self past the basics. It isn't like we needed to replace nearly every physical linkage with a 5volt signal and every button with a capacitive touch interface and every gauge with an lcd until those LITERAL android tablets glued to the dashboard take over for the older style engine computer.

I realize you were trying to get me on an extreme point but the issue with the really good extreme points is inside there is a kernel of a point that remains legit regardless of the absurdities piled on.

My last remark about this car analogy is .. Yeah, I know I can just put it in H but it doesn't make it any less bullshit.

made them extremely difficult if not impossible to service

The point is that it's not just difficult, but not needed as well.

A mature culture of modding and overcoming grows around deficient things. The rest just works™.

Now look how both X11 and Wayland attract tinkerers of different kind.

Modern cars (etc) CAN indeed be worked on.. I do all my own work, nothing of mine ever goes someplace requiring appointments and personal information to have it worked on. Rebuilding an engine or transmission hasn't changed that much. Been there, done that. Worst case is anything containing "VIN-locked" parts requiring the dealer to log into it and approve a new part. John Deere tractors are the worst offender here. Solution to this sort of thing (before they get cracked anyway) is to junk the OEM computer entirely and get an unlocked one sold for auto racing and whatever parts are needed to use it. Also some VIN-locked parts that fail other than in the chipset or board can be hacked by taking the offending chip or board from the old part and putting it in the new part that fixes a failure in some other part of itself. The computers do make a lot of things easier, like finding out which electrical sensor is bad is easy, a $35 scan tool does it. Finding which of a half dozen vacuum diaphragms was bad in the 1970's could require testing them all individually. Anyway, I don't think we will see Xorg on any small embedded computer systems using any sort of UNIX/linux based system in the future. Wayland might displace some proprietary systems though, and that will simplify running new interface pages on hacked/cracked systems if the authors don't have to figure out a one-off display server on whatever computer is used to control the setup. This sort of thing is already being done: hackers in Ukraine cracked John Deere's locked computers open like a melon, and their hacked firmware is now sold and used globally. I would recommend disconnecting any hacked device not intended as a communications system from the Internet not only for privacy but to prevent the vendor from "updating" it to lock out your cracks or install new antifeatures and DRM. It also should never, ever go back to the dealer for the same reason.

@lukefromdc I did say exactly:

The extreme modernization of cars have made them extremely difficult if not impossible to service your self past the basics.

The fact is, an android tablet replacing a stereo head unit is debatable as android auto stands. If it starts taking over for the dedicated firmware-based engine computer then I sure as hell will replace it with Linux and x11 if my car is so crippled. If it is JUST being a stereo.. Then I'd opt to just remove it completely from the car and wire in an actual car stereo or just replace it with a cellular dock. Android tablets especially the ones in cars now are utter junk. Hardware and software.

Of course my preference is for it to be operationally sound, has air conditioning, has an automatic transmission, and the driver seat is relatively comfortable. I require not much else.. It could be the junkest piece of junk that was ever called junk.. As long as it works and provides those basics. Tho a cup holder is always a plus.

If you are WAY past the basics, doing things like rebuilding engines and transmissions really hasn't changed much, so long as you don't encounter a VIN locked chip in a failed part. It's in the middle (e.g a computer replacement) that you get the most complexity it seems. Yes, I have rebuilt many engines and transmissions...

Why is it working better in the X11 ecosystem then?

Why does what work better in the X11 ecosystem? The example I just mentioned with Resolve happens in X11 and Wayland. It's a matter of texture compatibility and negotiation between a Mesa driver and compute runtime that are both developed by the same company.

Are you talking about what you mentioned with Portals? This has been mentioned to you before but Portals aren't part of Wayland. Like I said, Portals work with X11, too. DMAbuf isn't a Wayland thing either, it's a Linux kernel thing.

The quote you cited literally says that the issue has to do with the dmabufs being sent in a GPU tiled format that's more efficient for the GPU. That's exactly what I mentioned in my example with Resolve. The Intel Mesa driver uses an internal GPU texture formats called things like Tile4 and Tile64 and when it passes a buffer to their OpenCL driver, it interprets one as if it's the other. The issue happens in X11, too.

The only person who said Wayland was at fault in that issue was you...

I suspect these issues are caused by Wayland, which is the default session on Raspberry Pi OS, and is known for breaking screen sharing.

...and despite nobody else saying it was a Wayland issue, you still interpreted it that way. You really need to stop assuming that every bug is a Wayland limitation or issue, and accept that bugs and incompatibility between things has always happened, even under X11. X11 is a not a magic bullet that makes things work and neither is Wayland. They're each just parts of a working system.

Maybe it has to do with the fact that everyone basically uses the same implementation rather than reinventing the wheel (and bugs) time and again.

Without knowing what thing you're claiming works better in X11, I can't really answer this properly but... using this logic, wouldn't it be better if FreeBSD users just came to Linux? Wouldn't it be better if KDE, Gnome, Mate, etc all became one DE? Neither Wayland nor X11 would be needed because apps would just use whatever API is uniquely used in this super DE. Also nobody is re-inventing the wheel.

Do you want a bunch of options so people can pick and choose parts to work together or do you want no options? Or maybe you want a bunch of options that work together but none of them have the room to be all that different from each other so it's basically the same as having no options.

Why is it working better in the X11 ecosystem then? Maybe it has to do with the fact that everyone basically uses the same implementation rather than reinventing the wheel (and bugs) time and again.

I actually tested Davinci Resolve and its god awful because it does not communicate to the user !

By default, you require a license to have video previews of mp4 footage. But it doesnt tell you! It doesnt tell you to convert it so that you can work with it. Then, when you want the previews, and the permission to edit it, you need the studio license for 329 EUR. Thats something you find out on the forums in the abyss...

Then, when you bought it, you edit your file, you see that AAC is not a supported codec. You'd need to convert that... too. And thats something it doesnt tell you either.

Thats when I did the refund, and I didn't get it until I opened a PayPal case cause the support line didn't answer me.

I have my issue with Resolve, too, but it's not "god awful" just because it doesn't read mp4s without paying for the Studio version. I mainly edit Redcode RAW, Blackmagic RAW, or Prores and occasionally h.264 or h.265. I also do a lot of color grading and occasionally compositing. There really aren't open source tools that do any of that or work with those file formats.

Kdenlive works well for simpler videos and if I really needed to I could probably edit a film in it if it supports the formats the film is shot in, but I wouldn't choose it over Davinci Resolve. I'd love there to be an open source alternative to Resolve and I've thought of attempting to work on one myself but that would still take years to be usable and without a lot of help, it will still lag behind Resolve's feature set for a long time.

Kdenlive can use any video format your ffmpeg install supports. Distro versions that have patent-busting formats stripped out do need to be replaced with full-featured builds, which are available for most distros but kept an arm's length from the distro itself so any patent nastiness doesn't have the potential to take down the whole distro. This also separates the repo in question from the deeper pockets of someone like Ubuntu or Red Hat, discouraging patent lawsuits. For a proprietary video editor that makes money for its authors to use an unpaid version of a patented codec might cross a software paten red line that is currently being ignored when money is not part of the transaction. If the editor's team has to pay for the codec they cannot afford to then distribute it free having paid for it themselves. If for some reason you MUST use a paid editor and not pay for codecs, you could use ffmpeg to transcode everything to a supported codec first, thus taking the video editor and its authors out of the loop patent-wise. Render out to some low loss supported codec such as an uncompressed one, then compress in something like Avidemux or in ffmpeg directly

Please stay on the subject of Wayland deficiencies.

Guys I'm sorry but this "discussion" looks like:

Please stay on the subject of Wayland deficiencies.

You constantly bring up things that don't have to do with Wayland and then say it's Wayland. Just pretend we're complaining about Wayland and hush.

Kdenlive can use any video format your ffmpeg install supports...

Just looked it up and it looks like there's some work that was done to add braw support to ffmpeg so I'll have to check that out.

Render out to some low loss supported codec such as an uncompressed one, then compress in something like Avidemux or in ffmpeg directly

No way in hell. I'm not going to transcode everything. Blackmagic RAW and Redcode RAW are very high bitrate recording codecs which are only used by cameras and external recorders for cameras. Blackmagic RAW is 12-bit with PCM audio and metadata for ISO, white balance, lens, take, project, and per-frame gyrodata. The settings I typically record at are between 60-149MB/s (yes megaBYTES) on lower quality and 222-444MB/s at the highest quality. Transcoding everything before editing would strip out of all that metadata, disable highlight recovery options, and take up over twice the amount of space. I saw over twice as much because I'd need to use a 16-bit codec to make sure the baked in ISO curve doesn't crush away my data.

Even if I did go through all that effort (for no reason... I have two perpetual licenses for Resolve that I got with my cameras), Kdenlive's color grading is no where close to Resolve's.

@myownfriend This gist is about Wayland, not about the video editor you use.

@myownfriend This gist is about Wayland, not about the video editor you use.

That's nice. The guy who created the gist bitches about Pipewire and Portals and they're not Wayland either.

Hush.

Can't we all just dislike Wayland and everything else that came from the mentality if not the same people behind Wayland like systemd pipewire and Google (because Google is always responsible) together?

WON'T SOMEBODY PLEASE THINK OF THE CHILDREN?!

This gist isn't even "about Wayland". Probo literally said it's about complaining about Wayland and it's perceived faults. He's not interested in what it does better than X11, he's not interested in determining whether or not Wayland is even at fault, and he's not interested in whether or not the issues he perceives about Wayland have been addressed.

It's all about complaining with no realistic end goal in mind. If you haven't figured that out by now then you need to pay better attention.

To add to the point of @myownfriend, most of the issues on this Gist is already outdated and resolved because the programs has long switched to the relevant portal implementations. Wayland does not and should not handle stuff that is outside the scope of a compositor. A compositor renders things to the screen, full stop.

Compare that to the bloated X11, where you have to disable the security module otherwise more than half of the apps you use will break. And it also has a built-in printing API, a printing API has no place in a compositor.

@mattatobin you can't criticize systemd anymore because the systemd-democracyd installed in your computer will make it blow up 😨

@aki-k and yet here these people are complaining about xdg-portals which are completely seperate from Wayland itself.

Servicing this document and its comment thread has been more wasteful of compute time than all of AI and proof-of-work crypto combined. I feel the urge to personally rip out and scrap all the copper from the physical GitHub servers with this gist and its thread replicated on them, at the same time, just to make something valuable out of this thread and prevent further waste of human and compute time. Obviously, this is not possible, as the thread is probably geographically distributed and I cannot yet be in more than one location at once. Thank you, that is all.

Since there were questions what this gist is supposed to be about, and since some ground rules should be established:

Considered on-topic:

• Reasons why we still need (and will need for the foreseeable future) X11 and Xorg
• Deficiencies of the Wayland philosophy, policies, architecture, protocols, and current implementations; constructive ideas on how to fix those
• Deficiencies of technologies (like D-Bus, .desktop files, Pipewire, Portals) that Wayland factually forces upon us and which we would not have to use if it wasn't for Wayland (while I am writing this I notice that many of those have to do with IBM Red Hat - coincidence?)

Considered off-topic:

• Application alternatives (just use Y instead of X)
• Statements about other people

Off-topic comments may get deleted. Even though I don't like to do this, this gist becomes a random dumping ground otherwise.

Cool. I'll try and follow it as best as I can :)

• Deficiencies of technologies (like D-Bus, .desktop files, Pipewire, Portals) that Wayland factually forces upon us and which we would not have to use if it wasn't for Wayland (while I am writing this I notice that many of those have to do with IBM Red Hat - coincidence?)

What do .desktop files have to do with wayland? Did you ever use *any* kind of desktop panel / taskbar in the last 10 years that didn't use .desktop files to create its menu? Also dbus, pipewire and portals have nothing to do with wayland and are definitely not "forced upon us by wayland". If at all one could argue that Gnome tries to promote those (and flatpacks). But again, this has absolutely nothing to do with wayland.

yo, I know that this thread isn't exactly known for being productive but you guys might be interested in this: https://codeberg.org/river/river it's a wayland compositor, that has some custom protocol extension to allow for external window managers. If we're decrying the loss of standardization then it might be worth putting some weight behind something like river or wayfire that bring back your composable architecture.

Did you ever use any kind of desktop panel / taskbar in the last 10 years that didn't use .desktop files to create its menu?

I don't even have an idea what do you mean. I find those .desktop files useless garbage. And yet I have a taskbar (even though I was considering it a legacy kludge, just like GNOME Shell developers thought of tray that time and also showed it somewhere into a corner hidden by default lol).

Did you ever use any kind of desktop panel / taskbar in the last 10 years that didn't use .desktop files to create its menu?

I don't even have an idea what do you mean. I find those .desktop files useless garbage. And yet I have a taskbar

And that taskbar you use has an application menu? If yes, how are the applications added there?

If yes, how are the applications added there?

Eh? The point of a taskbar is switching open windows only. Not launching any applications. Do you confuse it with a superbar, just like zoomers grown up on Chrome confuse DNS with Google Search?

Eh? The point of a taskbar is switching open windows only. Not launching any applications. Do you confuse it with a superbar, just like zoomers grown up on Chrome confuse DNS with Google Search?

Yep sorry. I am new to computers.

But see what the most worrying part is? Previously, generations differed in favoured technologies drastically. Grandgrannies listened to AM radio and gramophones, grannies listened to tapes, boomers listened to CDs and WinAmp and youngsters listened to pirated MP3 in Telegram Spotify.

But we're already approaching a time when generations would differ in terms of what Windows version they consider "classic": NT3.11 for Workgroups, 98, XP, 7 or 10. Or, in terms of OP: Lisa, iMac G3 or Macbook Air.

It clearly smells of a severe stagnation. But OP would see nothing wrong. After all, we still have AM radio and landline phones, sometimes even with pulse dialing, so you can plug and use your rotten rotary phone.

You know what, this taskbar discussion made me think that the SKIP_TASKBAR hint was actually a kludge to avoid listing auxiliary windows, which Wayland now has a native concept of subsurfaces for, so the kludge is not needed anymore. Am I true? Or did it have other legitimate use cases?

Ah, I recalled, AIMP could be minimized to a floating mini player window, which is not needed to be listed on a taskbar.

How do I can unsubscribe from this thread?

I don't think you can.

https://www.theregister.com/2022/10/25/lashcat9_linux_ui/

Since there were questions what this gist is supposed to be about, and since some ground rules should be established:

Considered on-topic:

So you just want a thread for people to repeat back to you what you already think and you don't want anyone to correct you on the things you're misunderstanding? Nah, I'm not gonna do that.

The reason this gist is unproductive is because of you. You don't want it to be productive. You started it like a year before you knew what Wayland was, and you refuse to spend anytime learning about it and evaluate it fairly compared to X11.

You have demonstrated that much like everyone's parents, you've already reached the point where you won't learn about new things. Everything past a certain point sucks and is straying away from "how things should be". I think you've even said as much, just in different words.

What is the point of discussing anything in the gist of there's no actual reachable goal when you just want Wayland to be X11? I've asked you plenty of times if you have any issues with X11. I've asked you how you would improve X11 and you never seem to answer those questions. It's been around like 37 years. The compute we run now, how we use them, who uses them, and the standards we have for them have all changed dramatically in 40 decades but you can't think of a flaw or something to improve in it.

Progress isn't really a thing with you. It's all about preservation.

You started it like a year before you knew what Wayland was, and you refuse to spend anytime learning about it and evaluate it fairly compared to X11.

This Wayland thing started to appear out of nowhere (I think Fedora was first to force it on my be default), and the first thing I learned about Wayland is that it degraded my desktop experience. Since people seemed to push it as a "successor" to X11, I created this gist to document in which ways it degrades the desktop experience, so that people a) might have a chance to fix the issues and b) stop pushing Wayland until everything was fixed. The more I learned about what this Wayland thing is, the philosophies behind it, the never ending discussions, the more I realized that it wasn't just a matter of fixing some remaining issues, but that the issues go deeper, beginning with the mindset that everyone would appreciate to change existing software or even the way we work.

For example, it is still not possible for an application to set pixel precise locations for its windows on the screen. Something that has been working without a hitch all the time.

I've asked you plenty of times if you have any issues with X11. I've asked you how you would improve X11 and you never seem to answer those questions.

Sure, there's plenty of stuff that could be improved with X11, but it doesn't take away things that have been working fine so far. Like, having applications set pixel precise locations for its windows on the screen. What X11 is missing it never had. So you could argue it is not progressing fast. But then, it doesn't break (take away) things. It has been proven in psychology that taking away things from people is perceived much worse than not giving them something to begin with.

People talking about multiple screens with different pixel densities and HDR and whatnot is fine and all, but those are very rare edge cases for exotic hardware setups. Sure, it would be nice for those who have such hardware, but we could all live without those things for all those years. But take away the possibility for my application to set pixel precise locations for its windows on the screen and I get angry, really angry. And don't get me started about screen capturing and screen sharing, which despite all the claims is still an issue even today and doesn't work in a consistent and robust way across all Wayland "compatible" software. The more I learn about Wayland, the more I understand that those issues are deeply based in the Wayland core architecture (e.g., every desktop environment suddenly requiring its own window server, baked together with the window manager).

What do .desktop files have to do with wayland?

As of now, applications that don't use one show a yellow "W" icon rather than what the application has set as a window icon. (There is a very new protocol that will eventually change that.)

https://codeberg.org/river/river it's a wayland compositor, that has some custom protocol extension to allow for external window managers. If we're decrying the loss of standardization then it might be worth putting some weight behind something like river or wayfire that bring back your composable architecture.

Interesting. I'll link to it on wayland-x11-compat-protocols. Thanks!

As for the issue of setting precise pixel locations on screen in wayland, it is in fact possible to do exactly that in wlroots compositors for GTK applications by using gtk-layer-shell. That is exactly how I positioned mate-panel's calendar popup. the volume control slider, and similar widgets. You can get the screen dimensions but not where some OTHER app is drawing its windows. With gtk-layer-shell you can anchor a window to any of the four edges and set a margin. By using two edges and a computation from the monitor dimensions you can place a window anywhere on the screen. This is normally used for such cases as panels, such as what I used it for in MATE. Best of all it should work with any wlroots compositor. Thus, while I selected wayfire for the compositor used in mate-wayland-session, the session components can be used to build a session around any other wlroots compositor. The only thing you can't do is change compositors during the same session, at least not until work to allow keeping applications alive when a compositor is terminated and connect them to a new compositor instance lands. KDE is said to be working on this, and note that KDE is considering porting to wlroots. Their wayland session predates wlroots, which is the only reason it is different. About not being able to read one apps window positioning from another app: That is intended to make it more difficult for a malicious app to capture inputs and redirect them. Only thing is, unless wayland becomes a popular phone compositor, we have the desktop situation where a malicious app to say, steal a banking login this way won't work, but the same malicious app running in browser as a webapp will. Firefox etc may run different pages in different processes, but since these can be tabs in one window and are all coming from just one app, wayland's security model breaks down in this case. A malicious website can sense that you have a banking site open, get enough information to work out which bank is involved, then send you a page asking for input placing the entries in the same places as the banking site. That could be a malicious account formation page, say for a fake spyware remover. Then it can try the inputs as username and passphrase with your bank, hoping you use the same username and passphrase everywhere. That only has to work against a few people to steal a lot of money.

in wayland, it is in fact possible to do exactly that in wlroots compositors for GTK applications by using gtk-layer-shell.

Good to know.

And, say, for Qt applications running on kwin? Why should such an essential functionality that should work regardless of the toolkit being used even have "gtk" in its name?

For me, everything that works just with some toolkits or just in some desktop environment is actually counterproductive, because it further splinters the already small "Linux" user base, and creates "but it works for me" responses from Wayland proponents.

KDE is said to be working on this

Ah. See. With Wayland, everyone needs to be working on everything before it works for everyone. Unlike with X11, where it "just worked".

About not being able to read one apps window positioning from another app: That is intended to make it more difficult for a malicious app to capture inputs and redirect them.

Classic "Wayland solves no issues I have but breaks almost everything I need" situation.

Many of the Wayland design seem to come from the idea that you run untrusted applications on your computer, which imho is a flawed assumption to begin with. Not everyone wants a "hostile desktop environment" where nothing can be trusted and everything is assumed to be malicious and hence is sandboxed and encumbered, some prefer a "collaborative desktop environment" where the focus is to make things work no worse than on the Macintosh in 1984.

This Wayland thing started to appear out of nowhere

What the fuck are you talking about "out of nowhere"? Wayland was in development since 2008 and the major DEs had implemented a Wayland backend by 2016. Even before Wayland was in development, people knew that X11 needed to be replaced because it was pretty obvious it needed to be.

Just because you're asleep at the wheel doesn't mean that things are happening "out of nowhere".

(I think Fedora was first to force it on my be default), and the first thing I learned about Wayland is that it degraded my desktop experience.

You learned that something changed and you didn't know what. To this day you don't seem to realize what exactly Wayland is.

Since people seemed to push it as a "successor" to X11, I created this gist to document in which ways it degrades the desktop experience, so that people a) might have a chance to fix the issues and b) stop pushing Wayland until everything was fixed.

"Fixed" is a dubious way of putting it consider things that aren't broken are still list as broken according to you because they're only broken in the sense that they aren't X11-like which is what you're used to. Case in point, you have Zoom issue still up that has been closed since August 2022 and was never an issue with Wayland or even Pipewire, it was an issue with Zoom. I imagine it's still there because Zoom uses Pipewire.

The more I learned about what this Wayland thing is, the philosophies behind it, the never ending discussions, the more I realized that it wasn't just a matter of fixing some remaining issues, but that the issues go deeper, beginning with the mindset that everyone would appreciate to change existing software or even the way we work.

Bro, to this day you'll ask question about Wayland that someone who really cared about this shit should have found out three months in at most. Furthermore you pushed the idea that Wayland can't be a successor to a true successor to X11 unless software used it with zero changes: something that sound dumb to anyone who knows what they're talking about.

For example, it is still not possible for an application to set pixel precise locations for its windows on the screen. Something that has been working without a hitch all the time.

And? The only reason you think that's super essential is because your hyper-specific use of it for the Hello Systems interface. That's not a super common use case and is actually a pretty dumb way of implementing the interface.

Sure, there's plenty of stuff that could be improved with X11, but it doesn't take away things that have been working fine so far. Like, having applications set pixel precise locations for its windows on the screen. What X11 is missing it never had. So you could argue it is not progressing fast. But then, it doesn't break (take away) things. It has been proven in psychology that taking away things from people is perceived much worse than not giving them something to begin with.

Damn you STILL can't say what you don't like about X11 or what can be improved about it. Saying "Sure it can be improved" and then talking about something else is cop out. You knew it would sound dumb to claim it's perfect so you said it can be improved but you never really thought about how it can be improved so you just said it can be improved and then changed the topic.

So I'll ask again: What flaws does X11 have? How would you improve it?

People talking about multiple screens with different pixel densities and HDR and whatnot is fine and all, but those are very rare edge cases for exotic hardware setups.

Again showing you're asleep at the wheel. Mixed DPIs and multi-monitor setups aren't "exotic" anymore. People frequently have dual monitor setups with their laptops for work and anyone from streamers to graphic designers to video editors have dual or triple monitors setups. Windows literally has built-ins screen casting so people can wireless use their TVs as second monitors and people use it.

Sure, it would be nice for those who have such hardware, but we could all live without those things for all those years.

It depends on what you use your computer for. Claiming that it's not a problem that it's not a problem that X11 can't properly do multi monitor just because you feel people don't absolutely need it is crazy.

But take away the possibility for my application to set pixel precise locations for its windows on the screen and I get angry, really angry.

Okay, and I got really angry when I switched to Linux and had to lower my 4K screen's resolution down to 2560 x 1440 because after I managed to get something like mixed DPIs working on X11 it slowed down my mouse cursor, made my lower resolution monitor look worse, and some applications launched so that they were scaled down by 33% which made them unreadable on both screens.

Constant tearing and games changing the display resolution of both of my monitors also got me really angry.

And don't get me started about screen capturing and screen sharing, which despite all the claims is still an issue even today and doesn't work in a consistent and robust way across all Wayland "compatible" software.

Again, Wayland doesn't do screen sharing, Portals and Pipewire do. They're not part of the Wayland protocol or the Wayland project. This has been said a million times to you and you can't get it through your thick skull. Portals and Pipewire literally work in X11 as well because they're not part of Wayland. The issue you're dealing with is that you've demonstrated a complete inability to tell the difference between Wayland, Wlroots, Pipewire, and Portals.

Your dumb ass even said an audio problem was Wayland-related because you saw Pipewire mentioned in an issue. You still have it linked in the first post, too! Pipewire is an audio backend but you didn't know that because you're averse to learning.

For me, everything that works just with some toolkits or just in some desktop environment is actually counterproductive, because it further splinters the already small "Linux" user base, and creates "but it works for me" responses from Wayland proponents.

"But it works for me" is literally your reasoning for using X11. It doesn't work for a lot of other people but you don't care.

Ah. See. With Wayland, everyone needs to be working on everything before it works for everyone. Unlike with X11, where it "just worked".

Nothing "just worked" in X11. After I switched to Linux, installed the Nvidia Proprietary driver, and got switched to X11 without knowing, it was immediate and noticeable down grade in usability. I've said it a million times but it almost made me switch back to Windows because it felt like I was using a broken operating system that wasn't yet meant to be run on desktop computers. It wasn't until I realized what had happened after installed the Nvidia driver that I realized what happened and stuck around.

Pipewire, btw, was another reason why I stuck around Linux. Not only did it fix small audio issues I was having, it allowed me to use applications like Carla and Helvum to route audio between applications via a patchbay interface. It can also route video streams to other applications and even route webcams to multiple applications at the same time which is something that no other OS can do. Its such an obvious choice to use it for screen and window capturing as well.

Classic "Wayland solves no issues I have but breaks almost everything I need" situation.

It solve issues other people have and breaks the one thing that you specifically want but don't need.

Many of the Wayland design seem to come from the idea that you run untrusted applications on your computer, which imho is a flawed assumption to begin with. Not everyone wants a "hostile desktop environment" where nothing can be trusted and everything is assumed to be malicious and hence is sandboxed and encumbered, some prefer a "collaborative desktop environment" where the focus is to make things work no worse than on the Macintosh in 1984.

This is stupid bullshit worded to make it sound pleasant. "Collaborate desktops" is your dumb way of sugar coating "it's a free-for-all where all apps fight for control over each other". It's not collaborative if there's no agreements between applications, that's called being intrusive. There's nothing hostile about it.

If you use a computer online, surf to any websites at all you do not know and trust, and let them run JS, you are allowing unknown and untrusted code to run on your computer. A browser running untrusted JS itself becomes untrustable keep in mind. This is why some run the browser from a whole separate VM (Qubes style) or as another user for this reason.

Wayland makes it more difficult for a separate app to attack a window being used by a legitimate website in your browser but as I said in the last post cannot protect one browser window from another short of having the browser itself open every site in a separate instance. Unfortunately, that is the most likely scenario for clickjacking or keystroke-jacking on a desktop it seems to me,.

The browser itself could defeat this by using say, up to 100px of random top and left padding for each tab opened. Popup positions for login popups could further be randomized within the same basic part of the screen they now appear in. This would throw most transparent/invisible attack entries overlaying a legitimate website's browser window and tab out of position. This should work on wayland, x11, even Windows and MacOS.

in wayland, it is in fact possible to do exactly that in wlroots compositors for GTK applications by using gtk-layer-shell.

Good to know.

And, say, for Qt applications running on kwin? Why should such an essential functionality that should work regardless of the toolkit being used even have "gtk" in its name?

For me, everything that works just with some toolkits or just in some desktop environment is actually counterproductive, because it further splinters the already small "Linux" user base, and creates "but it works for me" responses from Wayland proponents.

KDE is said to be working on this

Ah. See. With Wayland, everyone needs to be working on everything before it works for everyone. Unlike with X11, where it "just worked".

About not being able to read one apps window positioning from another app: That is intended to make it more difficult for a malicious app to capture inputs and redirect them.

Classic "Wayland solves no issues I have but breaks almost everything I need" situation.

Many of the Wayland design seem to come from the idea that you run untrusted applications on your computer, which imho is a flawed assumption to begin with. Not everyone wants a "hostile desktop environment" where nothing can be trusted and everything is assumed to be malicious and hence is sandboxed and encumbered, some prefer a "collaborative desktop environment" where the focus is to make things work no worse than on the Macintosh in 1984.

@lukefromdc Best watch how you present internet security via web browsers. I actually know a thing or two about that and sorry dude but you're full of crap. You act like javascript hasn't had security features well before the browsers started dropping any semblance of a good user experience, customization, and extensibility.

What the fuck are you talking about "out of nowhere"?

I did not install it. Nor ask for it. As you say, I didn't even know what it was. It was pushed upon me (when it was undoubtedly premature) in one of the Fedora Live ISOs as the default. And the experience was noticeably worse. I noted down everything it broke. In the expectation that whoever was responsible for that Wayland thing would fix the breakage in time. Only then I learned that not even did they not intend to fix everything quickly, they partly refused to even take it as their job (example: "Wayland doesn't do screen sharing, Portals and Pipewire do. They're not part of the Wayland protocol or the Wayland project."). And this is the most annoying aspect of Wayland - it breaks stuff that had been working all the time and then expects other projects to provide workarounds. And expects everyone to like using those.

people knew that X11 needed to be replaced because it was pretty obvious it needed to be

Not obvious even to this day. Why not improve it in the few nice-to-have areas in which it needs to be improved.

Case in point, you have Zoom issue still up that has been closed since August 2022

As you wrote in the linked issue,

The issue you experienced isn't with Wayland, it's just with Pipewire's PulseAudio plugin. Wayland doesn't have anything to do with audio. Try it with Pipewire again

Before Wayland there was no need to have Pipewire. As you say, "Wayland doesn't do screen sharing, Portals and Pipewire do." So by having to deal with Pipewire we now have to deal with Pipewire's issues, too. (Fun fact, I don't actually have much to complain about Pipewire as an audio server on Linux, my main complaint is that Wayland doesn't do screensharing properly without having Pipewire and hence factually forces it upon us, assuming everyone is using Linux. On FreeBSD, for example, we use an entirely different audio system.)

So I'll ask again: What flaws does X11 have? How would you improve it?

None that really bother me. It can do the things I have been able to do with it for the past decades. Sure, the default built-in "GUI" could look nicer, it would be better if it would work without the need for configuration files (although this got a lot better), etc. But in the end, it all works like it "always" has. How I would improve it? Well, I'd mark certain unused features as deprecated for at least half decade or so (first with compile time warnings and then with run time warnings), and then eventually disable, later remove them. New features I would add without interfering with how the rest works. Never ever I would remove or change actively used features. Never ever would I impose any artificial barriers to what applications can or cannot do (for those who want that, they can come up with some sandboxing). Preserving the existing body of application and desktop environment software on a binary and API level would be key objective, similar to how Windows has evolved without major breakages over time. If a new version of Windows cannot run an old application anymore, then it is rightfully assumed that Windows broke it. After all, we don't even know whether the application is still being developed.

when I switched to Linux and had to lower my 4K screen's resolution down to 2560 x 1440

Qt can do fractional scaling on X11.

After I switched to Linux, installed the Nvidia Proprietary driver

Then be lucky that you never encountered the open source Nvidia driver, Nouveau. At least in my experience, it has been a disaster. Even just clicking on the application launcher in Gnome 3 made the icon animation stutter. Only with the proprietary Nvidia drivers, things were are halfway smooth.

Portals and Pipewire literally work in X11 as well because they're not part of Wayland.

Maybe, but that's besides the point. The reverse is much more interesting: How can Wayland work without life support from those Linux-centric technologies. Just because a circle of people involved with IBM Red Hat, Fedora, Gnome, and Flatpak think they want to sandbox everything it still doesn't mean that everybody wants everything sandboxed, and no, GNUstep won't start using D-Bus anytime soon.

"Collaborate desktops" is your dumb way of sugar coating "it's a free-for-all where all apps fight for control over each other".

I am coming from the assumption that I only run software on my personal computer that I want to run. If I don't like how an application behaves, then I either change it (if it is open source), or I don't run it at all. Simple as that. The desktop should not feel like a battleground where everything has to be restricted,, encumbered, and made unnecessarily hard.

If you use a computer online, surf to any websites at all you do not know and trust

That's the difference. The web is a battleground. My open source personal computer desktop is not.

@hyprwm in https://twitter.com/hyprwm/status/1814983041598591223:

We are now independent! No more wlroots, only Hyprland :)

How is this a good thing? Isnt't wlroots what was supposed to unify the splintered landscape that is Wayland implementations?

@probonopd when the majority has no choice you don't need to care about things like interop or basic functionality. You do understand this right?

A good enough attacker can jump out of a sandbox. There is no such thing as impenetrable security and that has been true since long before computers existed. I am not going to start letting untrusted sites run scripts no matter what the sandboxes offered by the browser. Even Torbrowser has had (rare) exploits, thus the use of Tails or Whonix with it when things really count.

I rely on defense in depth, relying on browser security measures alone means having only one "trench" facing a potential storm of attackers.
Having not analyzed Firefox security myself, I treat it as being potentially vulnerable to click and keystroke jacking given a malicious input until proven otherwise. If you can prove otherwise, great! I normally assume an attack to be possible until proven otherwise.

Wayland can help with attacks mounted from one app against another, but not against attacks mounted from one window of any application against another so far as I know. My point here was on the limitations of wayland's denial to apps of knowing where another app's windows are, not the current state of the arms race between browser devs and writers of attack websites.

@lukefromdc Best watch how you present internet security via web browsers. I actually know a thing or two about that and sorry dude but you're full of crap. You act like javascript hasn't had security features well before the browsers started dropping any semblance of a good user experience, customization, and extensibility.

"But it works for me" is literally your reasoning for using X11. It doesn't work for a lot of other people but you don't care.

The difference is: If something doesn't work in X11, then it likely never has. --> It may lack features, but does not take anything away

With Wayland, things are no longer working properly that have worked nicely until Wayland came into the picture. --> It takes away things that we took for granted over the decades

Big difference!

"But it works for me" is literally your reasoning for using X11. It doesn't work for a lot of other people but you don't care.

The difference is: If something doesn't work in X11, then it likely never has. --> It may lack features, but does not take anything away

With Wayland, things are no longer working properly that have worked nicely until Wayland came into the picture. --> It takes away things that we took for granted over the decades

Big difference!

From what I can see you are just a smart troll at this point, almost everything was designed with X11 in mind and something relatively new comes out and you keep acting surprised when things don't just snap in place anymore, and even with things being changed to make it work on Wayland you go out of your way to just leave the status as "broken"; You see growing pains as a means to say Wayland is bad and will be bad forever, and you see the upsides to Wayland as non-existent, your prerogative I guess.

@Slayer5934 Growing pains.. for over a decade? Enough is enough. Wayland will be forced on everyone who can't be bothered to do anything that isn't sanctioned from up high to do.. But I will.

Wayland does not control my system and never will. SystemD's days are numbered on my system as anything past basic unit files is annoying as hell to deal with and a sysvinit script would simply be easier. Pipewire MOSTLY works but hell I am not even sure why I need PulseAudio.. But it has a mixer I use so its okay.

It isn't trolling to be ABSOLUTELY LIVID that not only have things NOT gotten over all better (because what is broken or missing changes from release to release) and the fact it is being MANDATED and if you don't agree you're a <insert whatever here/>.

I am tired of it and just want off this perpetual trainwreak at least long enough to get my shit in place so everyone else can destroy everything and it won't impact me.. AS much.

Nobody can mandate what display server you use etc if you are coder enough even to know what github is much less wayland. You can use distros like Gentoo that give you a lot of control over how you set your system up, or modify an existing distro. The only way this might fail is if down the road you come into posession of newer hardware for which only wayland video drivers are available and/or for which any compatable kernel is going to have issues with the "modesetting" x11 driver. Even then a nonaccelerated desktop will work, and CPU's have gotten so powerful that even compiz can now be used with LLVMpipe and work surprisingly well. When I was first setting up a bottom of the barrel AMD laptop back in 2022, I noticed compiz was a little slow and one plugin wasn't loading. Turned out memory encryption meant for servers was turned on in my kernel build, and was incompatable with the AMDGPU driver for on-chip graphics that use system RAM for video memory as well. I only found out this was why compiz was a little slow and one plugin failed by looking at Xorg.0.log, thus finding I was not even on the Radeon/ AMDGPU driver at all. Fixing my kernel build make the hardware driver work fine, use that machine until it got smashed.

With Wayland, things are no longer working properly that have worked nicely until Wayland came into the picture. --> It takes away things that we took for granted over the decades

have worked nicely until Wayland came into the picture.

No. Until *you* started to use wayland.

Is there a xrandr --setmonitor equivalent in wayland? It seems only sway has implemented something similar that only works for fullscreen applications.