AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Hotswitch between xorg and wayland1/30/2024 ![]() This toolkit does not currently support Wayland. Note that doing this on a system-wide basis isn't recommended, as many proprietary applications use statically-linked versions of SDL2 that are older and may break when forcing the usage of Wayland. Here's a tracking list of applications that need porting:įor games, applications, or other software that uses SDL2 as a toolkit, set the SDL_VIDEODRIVER environment variable to "wayland". In addition some SDL1 applications might crash if they are started with SDL_VIDEODRIVER set to "wayland". Otherwise applications using this toolkit need to be ported to SDL2. There's an SDL1 binary compatible wrapper that uses SDL2 as its backend (libsdl12-compat), that is being package ( 985170), that could make any SDL1 application transparently gain Wayland support. ![]() The toolkit is in maintenance mode, and it will not get Wayland support. The -platform wayland flag can also be used as a simpler means to force most Qt applications to use the Wayland backend. You can, of course, set this to also be specifically either "wayland" or "xcb" if you want to force one. You are recommended to set the environment variable QT_QPA_PLATFORM to "wayland xcb" which will have applications prefer Wayland only use X11 as a fallback. The qtwayland5 package will install the relevant platform plugin allowing Wayland apps to run natively with Qt. The CLUTTER_BACKEND environment variable, when set to "wayland", will forcibly run Clutter applications with the Wayland backend. Note that some Electron applications (Slack, Element, Discord, etc.) or chromium ( 861796) may break when setting GDK_BACKEND to "wayland". Similarly, setting the environment variable to "x11" will force it to run with the X11 backend (useful for forcing applications to use Xwayland that have compatibility issues when operating in their native Wayland mode). The GDK_BACKEND environment variable, when set to "wayland", will forcibly run a GTK3 application with the Wayland backend. To support screenshotting, screencasting and screensharing for example in Web Browsers pipewire is required in addition to one of the Desktop specific xdg-desktop-portal packages. When possible, using an application in its native Wayland mode is preferred. ![]() ![]() Some that use statically-linked versions of these, or which explicitly disable Wayland support for various reasons (e.g., KeePassXC), will require special flags or environment variables to be set.Īpplications using X11 will work fine in Wayland via the Xwayland compatibility layer, however there may be input issues or other bugs introduced. GTK3 and Qt 5 applications using the system libraries should default to Wayland automatically. Other X11 window managers unlikely to be supported.Window Managers and Compositors (unsupported) Phoc - Wayland compositor for mobile phones, Sway (a near drop-in replacement for i3): ( website, Github project) (Will stop supporting NVidia EGL/closed source driver from 1.0 onwards.)įireplace (no Debian package yet) (frozen upstream), Weston (the reference Wayland compositor), Other Wayland compositors of interest may include: Support planned, source (2014), an update (2019) This is often enough for basic functionality, however you are recommended to read the detailed wiki section for KDE on Wayland, especially if you are using an NVIDIA GPU. KDE Plasma requires the non-default plasma-workspace-wayland package to be installed. The Wayland session is built into GNOME and it should be an option in your display manager simply by having GNOME installed.Īs this is the default Debian desktop environment, Wayland is used by default in Debian 10 and newer, older versions use Xorg by default. All other compositors only support GBM and will not function with the proprietary NVIDIA driver in use. KDE Plasma (using KWin) supports GBM in all versions, and EGLStreams since Plasma 5.16. A Wayland compositor needs to explicitly support one or both of these APIs in order to function.Īs it stands, GNOME (using Mutter) supports GBM and EGLStreams well. NVIDIA GPUs using the proprietary driver support EGLStreams, while all other graphics cards and driver combinations support GBM. Buffer APIs currently supported are GBM and EGLStreams. How do I get the Wayland protocols supported by a Wayland compositor?įirstly, hardware should be checked for compatibility with a choice of desktop.I share monitors between systems using x2x.I run various programs over the network, e.g.I'm accustomed to running various programs (e.g.Applications can't share information with each other.Java Programs (supported since OpenJDK 16?).LibreOffice (supported, not by default).Window Managers and Compositors (unsupported).
0 Comments
Read More
Leave a Reply. |