Xfce Wiki

Sub domains
 

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
releng:wayland_roadmap [2024/12/04 09:44] – [Native Wayland] Update gaelreleng:wayland_roadmap [2025/05/28 09:16] (current) – [Component specific status] Remove misleading info about xfwm4 gael
Line 44: Line 44:
     * Prevent dependency on libgnome-desktop     * Prevent dependency on libgnome-desktop
     * xfce4-panel and xfdesktop have been ported to Wayland assuming our compositor will be based on wlroots.     * xfce4-panel and xfdesktop have been ported to Wayland assuming our compositor will be based on wlroots.
-    * There is also an [[https://github.com/adlocode/xfwm4/tree/wayland|unofficial port of xfwm4]] in progress.+    * We plan to port xfwm4 to Wayland using wlroots but it will only be for Xfce 4.22 at best.
   * Keep X11 compatibility for the foreseeable future   * Keep X11 compatibility for the foreseeable future
     * Nvidia support to Wayland is still problematic, one more reason to keep X11 backward compatibility (nouveau driver usually is slower)     * Nvidia support to Wayland is still problematic, one more reason to keep X11 backward compatibility (nouveau driver usually is slower)
Line 69: Line 69:
 | xfconf | yes | | | xfconf | yes | |
 | [[#xfdesktop]] | yes | See below | | [[#xfdesktop]] | yes | See below |
-[[#xfwm4]] | no | |+| xfwm4 | no | |
 | [[#xfce4-power-manager]] | yes | See below | | [[#xfce4-power-manager]] | yes | See below |
 | tumbler | yes | | | tumbler | yes | |
Line 87: Line 87:
   * Workspaces support needs an X11/Wayland abstraction, and could use the wlr-workspace-unstable-v1 protocol on Wayland.   * Workspaces support needs an X11/Wayland abstraction, and could use the wlr-workspace-unstable-v1 protocol on Wayland.
   * Listing all toplevel windows (windowlist menu, window icons on desktop) needs an X11/Wayland abstraction, and could use the wlr-foreign-toplevel-management-unstable-v1 protocol on Wayland.   * Listing all toplevel windows (windowlist menu, window icons on desktop) needs an X11/Wayland abstraction, and could use the wlr-foreign-toplevel-management-unstable-v1 protocol on Wayland.
- 
-=== xfwm4 === 
- 
-  * Unofficial port to Wayland in progress: https://github.com/adlocode/xfwm4/tree/wayland 
  
 === xfce4-settings === === xfce4-settings ===
Line 119: Line 115:
 | catfish | yes | | | catfish | yes | |
 | xfburn | yes | | | xfburn | yes | |
-| parole | yes | no systray icon ([[https://gitlab.xfce.org/apps/parole/-/issues/126|parole#126]]) |+| parole | yes | player window is not embedded ([[https://gitlab.xfce.org/apps/parole/-/issues/134|parole#134]]), no systray icon ([[https://gitlab.xfce.org/apps/parole/-/issues/126|parole#126]]) |
 | [[#xfce4-screenshooter]] | yes | partial, see below | | [[#xfce4-screenshooter]] | yes | partial, see below |
 | xfce4-screensaver | no | Port to Wayland is essentially done [[https://gitlab.xfce.org/apps/xfce4-screensaver/-/merge_requests/28|xfce4-screensaver!28]] \\ But this requires [[https://gitlab.xfce.org/kelnos/libwlembed|libwlembed]], which is still experimental and has no release at this stage (2024-02-04) | | xfce4-screensaver | no | Port to Wayland is essentially done [[https://gitlab.xfce.org/apps/xfce4-screensaver/-/merge_requests/28|xfce4-screensaver!28]] \\ But this requires [[https://gitlab.xfce.org/kelnos/libwlembed|libwlembed]], which is still experimental and has no release at this stage (2024-02-04) |
Line 134: Line 130:
 === xfce4-screenshooter === === xfce4-screenshooter ===
  
-Wayland does not specify a native interface for the compositor for taking screenshots and it [[https://gitlab.freedesktop.org/wayland/wayland/-/issues/32|looks like]] it never willWe decided to use wlroots' [[https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/blob/master/unstable/wlr-screencopy-unstable-v1.xml|screencopy protocol]] because that's probably what our compositor will support.+Originally Wayland wasn't meant to have protocols allowing screenshots ([[https://gitlab.freedesktop.org/wayland/wayland/-/issues/32|see here]]), that is about to change with [[https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4545|new proposed protocols]]. In the meantime we decided to use wlroots' [[https://gitlab.freedesktop.org/wlroots/wlr-protocols/-/blob/master/unstable/wlr-screencopy-unstable-v1.xml|screencopy protocol]] because that's probably what our compositor will support.
  
 At the moment only Entire Screen screenshots are supported ([[https://gitlab.xfce.org/apps/xfce4-screenshooter/-/merge_requests/52|xfce4-screenshooter!52]]), Rectangle Selection will be implemented next but Active Window is going to be much trickier, perhaps we'll need a custom protocol for our compositor to take care of that. At the moment only Entire Screen screenshots are supported ([[https://gitlab.xfce.org/apps/xfce4-screenshooter/-/merge_requests/52|xfce4-screenshooter!52]]), Rectangle Selection will be implemented next but Active Window is going to be much trickier, perhaps we'll need a custom protocol for our compositor to take care of that.
  
-If we want to support compositors that don't implement the protocol above, we have to add DBus Support for [[https://github.com/flatpak/xdg-desktop-portal|org.freedesktop.portal.Screenshot]]. This however is not planned and it's unlikely we'll ever fully support other compositors.+If we want to support compositors that don't implement the protocols mentioned above, we have to add DBus Support for [[https://github.com/flatpak/xdg-desktop-portal|org.freedesktop.portal.Screenshot]]. This however is not planned and it's unlikely we'll ever fully support other compositors.
  
 ---- ----
Line 188: Line 184:
 | xfce4-weather-plugin | yes | | | xfce4-weather-plugin | yes | |
 | xfce4-whiskermenu-plugin | yes | icons issue, menu window floating | | xfce4-whiskermenu-plugin | yes | icons issue, menu window floating |
-| xfce4-windowck-plugin | no | does not work (Libwnck) +| xfce4-windowck-plugin | no | [[https://gitlab.xfce.org/panel-plugins/xfce4-windowck-plugin/-/issues/37|to be fixed]], exits early and removes itself on Wayland for now 
-| xfce4-xkb-plugin | no | crashes (Libwnck) |+| xfce4-xkb-plugin | no | Non-portable to Wayland in the near future, exits early and removes itself for now |
  
 ---- ----
Line 199: Line 195:
 If you run a NVidia GPU, you will need to use the "Nouveau" driver for testing, Since the proprietary NVidia driver does not provide Wayland support. (Though some things might work in some cases) If you run a NVidia GPU, you will need to use the "Nouveau" driver for testing, Since the proprietary NVidia driver does not provide Wayland support. (Though some things might work in some cases)
  
-A wlroots compositor is almost a prerequisite for most core components, at least to ensure that all features ported to Wayland are available. The default compositor is labwc, but wayfire is another wlroots compositor on which tests have generally been carried out.+A wlroots compositor is almost a prerequisite for most core components (as well as panel plugins and some apps), at least to ensure that all features ported to Wayland are available. The default compositor is labwc, but wayfire is another wlroots compositor on which tests have generally been carried out.
  
-To start an Xfce session on Wayland, you can run ''startxfce4 %%--%%wayland'' from a tty, which will launch xfce4-session from labwc. A ''@datadir@/wayland-sessions/xfce-wayland.desktop'' file has also been added for display managers, such as lightdm, with which this has been tested. +To start an Xfce session on Wayland, you can run ''startxfce4 %%--%%wayland'' from a tty, which will launch xfce4-session from labwc. If you want to use wayfire instead, you'll need to run ''startxfce4 %%--%%wayland wayfire'' and add this configuration first, as wayfire doesn't have a ''%%--%%startup'' option like labwc (see ''startxfce4 %%--%%help'' for details):
- +
-If you want to use wayfire instead, you'll need to add this configuration first, as wayfire doesn't have a ''%%--%%startup'' option like labwc (see ''startxfce4 %%--%%help'' for details):+
 <file ini ~/.config/wayfire.ini> <file ini ~/.config/wayfire.ini>
 [autostart] [autostart]
Line 209: Line 203:
 </file> </file>
  
 +Configuration adaptations may be required for other compositors as well, if they also don't have a ''%%--%%startup'' option to pass to startxfce4.
  
-Configuration adaptations may be required for other compositors as well, if they also don't have a ''%%--%%startup'' option to pass to startxfce4.+''@datadir@/wayland-sessions/xfce-wayland.desktop'' file has also been added to xfce4-session for display managers, such as lightdm, with which this has been tested. The command line must also be modified in this file to use a compositor other than the default one.
  
 ---- ----