[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| wiki:user:pghvlaans [2023/12/23 00:16 (UTC)] – [Sources] pghvlaans | wiki:user:pghvlaans [2023/12/23 00:57 (UTC)] (current) – Made the new page. pghvlaans | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== Running X11 Environments in Xwayland ===== | ||
| - | <note important> | ||
| - | > Being able to read xorg.conf is not one my goals, nor achieving a bug-for-bug compatibility with Xorg - Xwayland with !901 (merged) allows to run a full X11 desktop, even the most legacy ones (I demoed it internally here using CDE from an XDMCP remote connection for the fun 😉).((Olivier Fourdan, xserver issue [[https:// | ||
| - | |||
| - | This is a how-to guide for running an X11 window manager or desktop environment in Xwayland on Slackware 15.0 and beyond. | ||
| - | |||
| - | At the time of writing (December 2023), this is a purely academic question for most -- if not all -- users. As both KDE Plasma and Xfce continue to move in the direction of Wayland, however, it is not impossible that full X servers become unavailable on Slackware in future years. Xwayland provides a workaround, if an imperfect one. The process of running an X11 environment from inside a rootful((" | ||
| - | |||
| - | * Choosing a Wayland compositor \\ | ||
| - | * Configuration \\ | ||
| - | * Running the Wayland compositor \\ | ||
| - | * Starting the X11 environment on Xwayland \\ | ||
| - | |||
| - | All outside packages mentioned here can be found on [[https:// | ||
| - | ==== Choosing a Wayland compositor ==== | ||
| - | The following considerations are important in choosing a Wayland compositor: | ||
| - | |||
| - | * Lightweight | ||
| - | * Stacking window management | ||
| - | <note important> | ||
| - | * Able to suppress client-side decorations | ||
| - | * Compatible with [[https:// | ||
| - | |||
| - | This how-to will use [[https:// | ||
| - | |||
| - | ==== General Configuration ==== | ||
| - | General configuration requirements are limited. It is only necessary to ensure that Xwayland-capable programs open under Xwayland rather than Wayland, and that startx does something productive. | ||
| - | |||
| - | === Forcing Xwayland === | ||
| - | Any program opening in Wayland mode will be managed by the Wayland compositor directly. This can result in the appearance of poorly-behaved windows with incorrect decoration and the non-appearance of system tray items. Place the following lines in ''/ | ||
| - | |||
| - | GDK_BACKEND=x11 | ||
| - | QT_QPA_PLATFORM=xcb | ||
| - | |||
| - | For X keyboard maps other than US, it may also be necessary to specify a keymap here: | ||
| - | |||
| - | XKB_DEFAULT_LAYOUT=jp | ||
| - | |||
| - | === startx === | ||
| - | Instructions for starting an X session should be contained in '' | ||
| - | |||
| - | ==== Configuring labwc ==== | ||
| - | === For Slackware 15.0 === | ||
| - | Create an autostart file at '' | ||
| - | |||
| - | #!/bin/sh | ||
| - | | ||
| - | DISPLAY=:1 startx -- / | ||
| - | |||
| - | This variant closes labwc after quitting the Xorg environment to return cleanly to tty or the display manager: | ||
| - | |||
| - | #!/bin/sh | ||
| - | | ||
| - | DISPLAY=:1 startx -- / | ||
| - | wmpid=$! | ||
| - | wait $wmpid | ||
| - | pkill -x labwc | ||
| - | |||
| - | To stop labwc from decorating the Xwayland server window, write the following to a file at '' | ||
| - | |||
| - | < | ||
| - | < | ||
| - | < | ||
| - | </ | ||
| - | </ | ||
| - | | ||
| - | If auto-starting xset tends to fail, try adding a few seconds of sleep before startx. | ||
| - | |||
| - | === For Other Versions === | ||
| - | These changes reflect post-15.0 Xwayland development: | ||
| - | |||
| - | * Rootful Xwayland windows are no longer decorated, so '' | ||
| - | * The initial geometry of the Xwayland server must be specified. Replace the Xwayland line in the autostart script above with the following | ||
| - | | ||
| - | '' | ||
| - | | ||
| - | Ideally, the '' | ||
| - | ==== Running ==== | ||
| - | The Wayland compositor should be known to the display manager for Run Level 4 users, assuming that its package includes a desktop file. Run Level 3 users can run the Wayland compositor directly from the command line: | ||
| - | |||
| - | $ / | ||
| - | |||
| - | Once the autostart script has started the X11 environment, | ||
| - | $ pgrep Xorg | ||
| - | $ pgrep Xwayland | ||
| - | If there is at least one Xwayland process (may vary by Wayland compositor) and no Xorg process, feel free to take a screenshot (optional) and tell your friends (not advised). | ||
| - | |||
| - | ==== Caveats ==== | ||
| - | The following caveats bear mentioning: | ||
| - | |||
| - | * Mouse pointer warping does not work. EdgeScroll in Fvwm is an example of an impacted feature. | ||
| - | * xrandr is non-functional in Xwayland versions before 22.1.3, and an extra program such as wlr-randr would be needed for screen management. Effectively, | ||
| - | * GPU memory usage is slightly higher relative to running an ordinary xserver. | ||
| - | * Wayland-only programs and any other program that runs in Wayland mode will be managed by the Wayland compositor rather than the X11 environment. | ||
| - | * Neither xinput nor synclient will work to turn off touchpads, for example. | ||
| - | * If an input device does not work in the chosen Wayland compositor, running an Xwayland server will not cause it to start working. | ||
| - | * xbacklight does not work; echoing values to ''/ | ||
| - | * If audio sharing fails, try using pipewire with [[https:// | ||
| - | |||
| - | The above list is non-exhaustive. | ||
| - | |||
| - | ===== Sources ===== | ||
| - | * Xwayland(1) | ||
| - | * labwc(1) | ||
| - | * [[https:// | ||
