For xfce 4.18, the plan is to ensure our applications work okay on wayland (those that already work or can be made to work with low effort). so basically start testing with weston and see if all menus etc behave normally and ifdef Xlib code.
Check the table in the component specific section for details.
It is not clear yet which xfce release will target a complete xfce wayland transition (or if such a transition will happen at all). Below a list of bigger junks which would need to be done in some way for such a transition.
Some of them are mostly agreed by xfce devs, others are controversial (or no decision was made so far).
- Do not depend on xwayland
- No xsettings
- Use libmutter as compositor library to show desktop and panels (similar to gnome-shell, but in plain C)
- That most likely would require xfdesktop and xfce4-panel to be merged into a single component
- The idea would be to dont fork, but to just use libmutter
- libmutter-7-0 seems to depend on libgnome-desktop-3-19 (debian bullseye). Can we drop that dependency somehow ?
- A big pro would be that ofourdan also is a gnome developer contributing to mutter
- Using wlroots instead would enable us to keep xfdesktop and xfce4-panel as separate components
- Possibility to exchange only xfdesktop or xfce4-panel, but not the other.
- Other implications ? What would need to be done to use wlroots ?
- Downsides ?
- Which plugin system to use for panel plugin if GtkSocket/GtkPlug will not work any more ?
- What about X11 backward compatibility ?
- Wayland compositors which were written from scratch like weston or sway will never run as a x11 window manager. But others which started as x11 window managers such as kwin or mutter still keep their x11 window management code
- We do not have the resources to maintain our own wayland compositor
- Freebsd provides https://hikari.acmelabs.space, not sure what is the situation for OpenBSD (possibly libinput missing?)
|Component||native wayland||xwayland||Known Issues||Testing|
|exo||ok||not used||-||in other applications|
|thunar||ok (has bugs)||not used||Issues||Default|
|xfdesktop||no (crash on startup)|
|parole||no (crash on startup)|
|xfce4-screenshooter||no (crash after region is selected)|
|thunar-archive-plugin||ok||not used||-||see thunar|
|thunar-vcs-plugin||ok (tested git)||not used||-||see thunar|
The panel's plugin system currently is based on GtkSocket/GtkPlug. This most likely won't work on Wayland or the wlroots approach. (or is there a way?). To be checked which plugin system could replace GtkSocket/GtkPlug.
Info about testing specific components.
Regarding the version to test: master, or latest dev release would be best, though latest stable release as well will do. Currently there is not much difference for most components. If you dont test master, best add info on which version you tested.
In general, xwayland only is relevant if native wayland does not work.
So first make sure xwayland is not installed on your system and test with weston. If that fails, take another try with xwayland installed (Not sure yet if xwayland needs to be configured in some way or activated to work)
- Install Weston with your distribution package manager
westonin a terminal emulator
- Make sure the component to test isn't already running in your X11 session (e.g Thunar as daemon)
- Open a terminal in the Weston session and start the component which is to be tested