• 1. Project Description
  • 1.1 What Is This?
  • 1.2 Why
  • 1.3 Why The Openbox Theme Specification?
  • 1.4 Very High Level Scope
  • 1.5 Videos
  • 1.6 Screenshot
• 2. Build and Installation
• 3. Configuration
• 4. Theming
• 5. Translations
• 6. Usage
  • 6.1 Gaming
• 7. Integration

Labwc stands for Lab Wayland Compositor, where lab can mean any of the following:

• sense of experimentation and treading new ground
• inspired by BunsenLabs and ArchLabs
• your favorite pet

Labwc is a wlroots-based window-stacking compositor for wayland, inspired by openbox.

It is light-weight and independent with a focus on simply stacking windows well and rendering some window decorations. It takes a no-bling/frills approach and says no to features such as animations. It relies on clients for panels, screenshots, wallpapers and so on to create a full desktop environment.

Labwc tries to stay in keeping with wlroots and sway in terms of general approach and coding style.

Labwc has no reliance on any particular Desktop Environment, Desktop Shell or session. Nor does it depend on any UI toolkits such as Qt or GTK.

firstly, we believe that there is a need for a simple Wayland window-stacking compositor which strikes a balance between minimalism and bloat approximately at the level where Window Managers like Openbox reside in the X11 domain. Most of the core developers are accustomed to low resource Desktop Environments such as Mate/XfCE or standalone Window Managers such as Openbox under X11. Labwc aims to make a similar setup possible under Wayland, with small and independent components rather than a large, integrated software eco-system.

Secondly, the Wayland community has achieved an amazing amount so far, and we want to help solve the unsolved problems to make Wayland viable for more people. We think that standardisation and de-fragmentation is a route to greater Wayland adoption, and wanting to play our part in this, Labwc only understands wayland-protocols & wlr-protocols, and it cannot be controlled with dbus, sway/i3/custom-IPC or other technology.

Thirdly, it is important to us that scope is tightly controlled so that the compositor matures to production quality. On the whole, we value robustness, reliability, stability and simplicity over new features. Coming up with new ideas and features is easy - maintaining and stabilising them is not.

fourthly, we are of the view that a compositor should be boring in order to do its job well. In this regard we follow in the footsteps of metacity which describes itself as a "Boring window manager for the adult in you. Many window managers are like Marshmallow froot Loops; Metacity is like Cheerios."

finally, we think that an elegant solution to all of this does not need feel square and pixelated like something out of the 1990s, but should look contemporary and enable cutting-edge performance.

In order to avoid reinventing configuration and theme syntaxes, the openbox 3.6 specification is used. This does not mean that labwc is an openbox clone but rather that configuration files will look and feel familiar.

Also, parsing GTK3+ and Qt themes for window decorations is very complicated, so using much simpler specs such as those used by openbox and xfwm makes sense for a compositor such as labwc, both in terms of implementation and for user modification.

Openbox spec is somewhat of a stable standard considering how long it has remained unchanged for and how wide-spread its adoption is by lightweight distributions such as LXDE, LXQt, BunsenLabs, ArchLabs, Mabox and Raspbian. Some widely used themes (for example Numix and Arc) have built-in support.

We could have invented a whole new syntax, but that's not where we want to spend our effort.

A lot of emphasis is put on code simplicity when considering features.

The main development effort is focused on producing a solid foundation for a stacking compositor rather than adding configuration and theming options.

See scope for full details on implemented features.

High-level summary of items that Labwc supports:

• Config files (rc.xml, autostart, shutdown, environment, menu.xml)
• Theme files and xbm/png/svg icons
• Basic desktop and client menus
• HiDPI
• wlroots protocols such as output-management, layer-shell and foreign-toplevel
• Optionally xwayland

The obligatory screenshot:

To build, simply run:

meson setup build/
meson compile -C build/

Run-time dependencies include:

• wlroots, wayland, libinput, xkbcommon
• libxml2, cairo, pango, glib-2.0
• libpng
• librsvg >=2.46 (optional)
• xwayland, xcb (optional)

Build dependencies include:

• meson, ninja, gcc/clang
• wayland-protocols

Disable xwayland with meson -Dxwayland=disabled build/

for OS/distribution specific details see wiki.

If the right version of wlroots is not found on the system, the build setup will automatically download the wlroots repo. If this fallback is not desired please use:

meson setup --wrap-mode=nodownload build/

To enforce the supplied wlroots.wrap file, run:

meson setup --force-fallback-for=wlroots build/

If installing after using the wlroots.wrap file, use the following to prevent installing the wlroots headers:

meson install --skip-subprojects -C build/

User config files are located at ${XDG_CONfIG_HOME:-$HOME/.config/labwc/} with the following six files being used: rc.xml, menu.xml, autostart, shutdown, environment and themerc-override.

Run labwc --reconfigure to reload configuration and theme.

for a step-by-step initial configuration guide, see getting-started.

Themes are located at ~/.local/share/themes/\<theme-name\>/openbox-3/ or equivalent XDG_DATA_{DIRS,HOME} location in accordance with freedesktop XDG directory specification.

for full theme options, see labwc-theme(5) or the themerc example file.

for themes, search the internet for "openbox themes" and place them in ~/.local/share/themes/. Some good starting points include:

• https://github.com/addy-dclxvi/openbox-theme-collections
• https://github.com/the-zero885/Lubuntu-Arc-Round-Openbox-Theme
• https://bitbucket.org/archlabslinux/themes/
• https://github.com/BunsenLabs/bunsen-themes

The default window bar menu can be translated on the weblate platform.

./build/labwc [-s <command>]

NOTE: If you are running on NVIDIA, you will need the nvidia-drm.modeset=1 kernel parameter.

If you have not created an rc.xml config file, default bindings will be:

A root-menu can be opened by clicking on the desktop.

Cursor confinement is supported from version 0.6.2. If using older versions, use a nested gamescope instance for gaming. It can be added to steam via game launch option: gamescope -f -- %command%.

Suggested apps to use with labwc:

• Screen shooter: grim
• Screen recorder: wf-recorder
• Background image: swaybg
• Panel: waybar, yambar, lavalauncher, sfwbar
• Launchers: bemenu, fuzzel, wofi
• Output managers: wlopm, kanshi, wlr-randr
• Screen locker: swaylock

See integration for further details.