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

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
howtos:window_managers:running_xorg_environments_in_xwayland [2023/12/23 00:52 (UTC)] – Move the xserver issue quote. pghvlaanshowtos:window_managers:running_xorg_environments_in_xwayland [2024/01/25 11:06 (UTC)] (current) – [Caveats] Wrong file path. pghvlaans
Line 1: Line 1:
 ====== Running Xorg Environments in Xwayland ====== ====== Running Xorg Environments in Xwayland ======
 This is a how-to guide for running an Xorg window manager or desktop environment in a Wayland compositor((In Wayland terms, the "compositor" is the program responsible for displaying and managing windows. KWin is the only Wayland compositor included in Slackware 15.0.)) on Slackware 15.0 and beyond. This is a how-to guide for running an Xorg window manager or desktop environment in a Wayland compositor((In Wayland terms, the "compositor" is the program responsible for displaying and managing windows. KWin is the only Wayland compositor included in Slackware 15.0.)) on Slackware 15.0 and beyond.
- 
-> 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://gitlab.freedesktop.org/xorg/xserver/-/issues/1332#note_1431672|#1332]])) 
  
 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 Xorg environment from inside a rootful(("Rootful" here means that the Wayland compositor does not manage the Xwayland window.)) Xwayland session is straightforward: 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 Xorg environment from inside a rootful(("Rootful" here means that the Wayland compositor does not manage the Xwayland window.)) Xwayland session is straightforward:
Line 12: Line 10:
  
 All outside packages mentioned here can be found on [[https://slackbuilds.org|SlackBuilds Online]]. All outside packages mentioned here can be found on [[https://slackbuilds.org|SlackBuilds Online]].
 +
 +> 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://gitlab.freedesktop.org/xorg/xserver/-/issues/1332#note_1431672|#1332]]))
 +
 ==== Choosing a Wayland compositor ==== ==== Choosing a Wayland compositor ====
 The following considerations are important in choosing a Wayland compositor to run the Xwayland server: The following considerations are important in choosing a Wayland compositor to run the Xwayland server:
Line 71: Line 72:
   * Rootful Xwayland windows are no longer decorated, so ''rc.xml'' is unnecessary.    * Rootful Xwayland windows are no longer decorated, so ''rc.xml'' is unnecessary. 
   * The initial geometry of the Xwayland server must be specified. Replace the Xwayland line in the autostart script above with the following:   * The initial geometry of the Xwayland server must be specified. Replace the Xwayland line in the autostart script above with the following:
-   + 
-  ''DISPLAY=:1 startx -- /usr/bin/Xwayland -fullscreen -geometry 1920x1200'' +  DISPLAY=:1 startx -- /usr/bin/Xwayland -fullscreen -geometry 1920x1200 
-  +
 Ideally, the ''geometry'' option will match the dimensions of the monitor. xrandr can change the resolution afterwards. Ideally, the ''geometry'' option will match the dimensions of the monitor. xrandr can change the resolution afterwards.
 ==== Running ==== ==== Running ====
Line 92: Line 93:
   * GPU memory usage is slightly higher relative to running an ordinary xserver.   * 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.   * 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.+  * Neither xinput nor synclient will work to adjust input device settings; instead, use the file ''$HOME/.config/labwc/rc.xml''. See the ''LIBINPUT'' section in labwc-config(5) for details.
   * If an input device does not work in the chosen Wayland compositor, running an Xwayland server will not cause it to start working.   * 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 ''/sys/class/backlight/*/brightness'' may be a workaround, depending on the system.   * xbacklight does not work; echoing values to ''/sys/class/backlight/*/brightness'' may be a workaround, depending on the system.

Trace: • inst_sa64_rk3399_pinebookpro • zfs_home • inst_sa64_lx2160a_honeycomb • development_refguide_di • ar • google-chrome • inst_sa64_bcm2711_rpi4 • package_management_hands_on • slackpkg • external

howtos:window_managers:running_xorg_environments_in_xwayland ()