User Tools

Site Tools


doc:appunti:hardware:raspberry_x_wayland

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
doc:appunti:hardware:raspberry_x_wayland [2025/04/07 11:16] – [Raspberry Pi: X11 or Wayland] niccolodoc:appunti:hardware:raspberry_x_wayland [2025/04/07 12:01] (current) niccolo
Line 2: Line 2:
  
 With the operating system **Raspbian GNU/Linux 12 (bookworm)** it is possibile to choose between the traditional **X11** graphical backend and the new **Wayland**. With X11 you can use only the **Openbox** window manager, while in Wayland you can choose **Wayfire** or the **Labwc** window manager. With the operating system **Raspbian GNU/Linux 12 (bookworm)** it is possibile to choose between the traditional **X11** graphical backend and the new **Wayland**. With X11 you can use only the **Openbox** window manager, while in Wayland you can choose **Wayfire** or the **Labwc** window manager.
 +
 +The default is **Wayland** + **Labwc** for all the Raspberry Pi models, including the Pi 2.
  
 Start the **raspi-config** and navigate the **Advanced Options** => **Wayland** to make your choice. Start the **raspi-config** and navigate the **Advanced Options** => **Wayland** to make your choice.
Line 72: Line 74:
 </code> </code>
  
-===== Wayland Wayfire not starting =====+===== Wayland Wayfire not starting on the Raspberry Pi 2 =====
  
-On my Raspberry Pi there is a problem which prevents Wayland Wayfire from starting. Fortunately enough the ''raspi-config'' added into the **/etc/lightdm/lightdm.conf** configuration file the **fallback-session** option, which launches the legacy X11.+On the Raspberry Pi 2 the Wayland Wayfire does not start. Fortunately enough the ''raspi-config'' added into the **/etc/lightdm/lightdm.conf** configuration file the **fallback-session** option, which launches the legacy X11.
  
 I discovered it because I installed the **hide-cursor** Wayfire plugin, but the plugin did not work. Actually the entire Wayfire was not running! I discovered it because I installed the **hide-cursor** Wayfire plugin, but the plugin did not work. Actually the entire Wayfire was not running!
  
-FIXME How to get the Wayfire running.+As per **Raspbian GNU/Linux 12 (bookworm)**, [[https://www.howtogeek.com/raspberry-pi-os-wayland-rollout/|Raspberry Pi OS Switches to Wayland on All Pi Models]], and [[https://hackaday.com/2024/10/28/raspberry-pi-oss-wayland-transition-completed-with-switch-to-labwc/|Raspberry Pi OS’s Wayland Transition Completed With Switch To Labwc]]. 
 + 
 +Wayfire is more resource-intensive than Labwc, so its use is discouraged and it will no start on the **Raspberry Pi 2**. Infact the **/usr/bin/xfallback.sh** script will return zero if run on the Pi 2. 
  
 ===== Starting the Wayland backend manually ===== ===== Starting the Wayland backend manually =====
doc/appunti/hardware/raspberry_x_wayland.1744017395.txt.gz · Last modified: 2025/04/07 11:16 by niccolo