Skip to main content

Labwc

A complete, productivity-focused Labwc desktop experience — thoughtfully configured, highly customizable, and unified by a powerful theme engine.

Archcraft's labwc configuration brings together a carefully selected collection of tools, utilities, scripts, and desktop components to deliver a cohesive and customizable desktop experience. From window management and application launchers to system controls, workflow utilities, and dynamic theming, every component is configured to work together.

Designed with both functionality and aesthetics in mind, it provides a practical desktop environment without unnecessary complexity.

labwc desktop showcase

Get Archcraft labwc

Get the complete labwc configuration from Ko-fi and support the continued development of Archcraft.

Features​

This is more than a collection of dotfiles. It's a complete, productivity-focused Labwc desktop setup, with carefully configured applications, integrated utilities, custom scripts, and a unified theme engine.

Desktop Environment​

  • Fully Configured Labwc — A comprehensive compositor configuration with window management, layouts, workspaces, decorations, keyboard shortcuts, mouse bindings, and other available options configured through rc.xml.
  • Feature-Rich Desktop Menu — An extensive menu system with multiple styles, icon support, and dynamic pipemenus for launching applications, running commands, managing windows, browsing files and locations, and accessing system utilities.
  • Advanced Display Management — Automatic display profile switching when monitors are connected or disconnected, saved display configurations, resolution and scaling controls, and virtual monitor management through integrated menus and scripts.
  • Multiple Statusbar Layouts — A fully configured Waybar setup with modular configuration files, independently managed modules, and multiple statusbar layouts.
  • Crystal Dock — A fully configured dock with customizable appearance, panel settings, positioning, and visibility options.

Applications and Launchers​

  • Three Configured Terminals — Alacritty, Kitty, and Foot, each with dedicated configuration files for appearance, colors, fonts, and general settings.
  • Rofi Applets — A collection of menus and applets for launching applications, running commands, browsing files, taking screenshots, managing themes, browsing and setting wallpapers, gtk appearances, controlling media and sessions, handling network connections, accessing clipboard history, and launching applications with elevated privileges.
  • Wofi Alternative Launcher — An alternative application launcher and session power menu.
  • Wlogout Session Manager — An alternative graphical interface for logging out, rebooting, shutting down, and managing the session.

Desktop Utilities​

  • Custom Notification Daemon — Mako is configured with dedicated settings, modular configuration options, and custom notification icons.
  • Dedicated OSD — An on-screen display for system feedback, with configurable positioning, appearance, and icons that adapt their colors to the active theme.
  • Extensive Script Collection — A range of utilities for managing the desktop, launching applications with custom configurations, displaying system information, and controlling system functions.
  • Hardware Controls — Integrated brightness and volume controls with support for multiple backends.
  • Screenshot and Screen Recording — Dedicated tools and menus for capturing screenshots(selection, annotation, and editing through satty) and recording the desktop(GPU Screen Recorder integration), with configurable options.
  • Clipboard Management — Clipboard history and retrieval through Cliphist and Rofi.

Session and Power Management​

  • Automatic Idle Management — Swayidle integration for managing idle behavior and triggering configured actions.
  • Automatic Screen Locking — Integrated idle-triggered locking with support for the configured lockscreen options.
  • Display Power Management — Automatic display power control during idle periods.
  • Session Controls — Integrated session and power menus for locking, logging out, rebooting, and shutting down.

Theme Engine​

  • 45 Handcrafted Static Themes — A collection of carefully designed themes with distinct color palettes and visual styles.
  • Dynamic Theme Generation — Generate an unlimited variety of color schemes using Pywal and randomly selected wallpapers.
  • Unified Appearance — Apply themes consistently across Labwc, terminals, Waybar, dock, notifications, OSD, launchers, lock screens, GTK applications, and other supported components.
  • Application Theme Integration — Theme switching also updates GTK appearance, Geany color schemes, and Satty window colors.

Lock Screen​

  • Veila — The default lockscreen, integrated with the desktop theme engine.
  • Hyprlock — An alternative lockscreen with static and dynamic theme support.
  • Swaylock — An additional fallback lockscreen option.

Customization and Management​

  • Comprehensive Keyboard and Mouse Bindings — Extensive shortcuts and mouse actions for window management, application launching, workspace navigation, display control, and system operations.
  • Configurable Menus — Multiple menu styles, icon support, and preferences for changing menu appearance, editing configuration files, managing displays, switching themes, and viewing system information.
  • Modular Configuration — Components are organized into dedicated directories and separate configuration files, making individual applications and desktop features easier to customize and maintain.

Obtain Files​

There are two ways to get the Labwc Desktop configuration: a one-time purchase through Ko-fi or a monthly subscription through GitHub Sponsors.

Both options provide the complete configuration. The difference is how you access future releases and updates.

One-Time Purchase (Ko-fi)​

Purchase the configuration directly from the Ko-fi Shop with a single payment.

  • Pay once: No subscription or recurring charges.
  • Choose your version: Purchase the specific release you want, such as v1.0 or v2.0.
  • Download anytime: Access your purchased version through your Ko-fi order.
  • Future releases: Major versions are sold separately and require an additional purchase.

After completing your purchase, download the configuration archive from your Ko-fi order.

Version-Specific Access

A one-time purchase grants access to the selected version only. For example, purchasing v1.0 does not automatically include v2.0 or later releases.

Monthly Sponsorship (GitHub)​

Become a monthly sponsor through GitHub Sponsors to access the configuration and receive ongoing updates.

  • Monthly subscription: Select the sponsorship tier that includes Labwc Desktop.
  • Private repository: Get access to the dedicated GitHub repository containing the configuration files.
  • Regular updates: Receive new releases, improvements, and bug fixes while your sponsorship remains active.
  • Support development: Help fund continued development, maintenance, and future improvements.

This option is ideal for users who want to stay up to date with the latest improvements without purchasing each new release separately.

GitHub Repository Access

Access to the private repository requires an active sponsorship under an eligible tier. If your sponsorship ends, repository access will be revoked.

Previously downloaded files remain yours to use in accordance with the included license.

Compare Your Options​

FeatureKo-fiGitHub Sponsors
PaymentOne-timeMonthly
Complete desktop configuration✅✅
Access to selected version✅✅
Future releases and updatesSeparate purchaseIncluded while active
Private GitHub repository❌✅
Recurring payment❌✅
Supports development✅✅

License and Usage​

The Labwc Desktop configuration is distributed under a personal-use license, regardless of the purchase method.

You may customize the files for your own use and maintain private backups, including in private repositories.

However, redistributing, reselling, publicly uploading, or sharing the configuration files with others is not permitted, whether the files are original or modified.

Please read the included LICENSE file for the complete terms and conditions.


Installation​

The Labwc Desktop configuration is distributed as a compressed archive containing the complete desktop setup, including configuration files, scripts, themes, and supporting resources.

Before proceeding with the installation, obtain the configuration files using one of the available options above.

Download and Extract​

After obtaining the configuration, download the labwc_YYYY-MM-DD.tar.gz archive and save it to a directory of your choice.

Open a terminal in that directory and extract the archive:

tar -xzvf labwc_YYYY-MM-DD.tar.gz

Navigate to the extracted labwc directory:

cd labwc

The archive includes prebuilt packages for Archcraft, along with the configuration files and resources required for manual installation on other Linux distributions.

Choose your distribution below to continue with the installation.

Install on Archcraft​

On Archcraft, installation is straightforward. The provided package automatically installs the configuration along with all required dependencies.

Navigate to the archcraft directory and install the package using pacman:

cd archcraft
sudo pacman -U archcraft-labwc-X.Y-Z-any.pkg.tar.zst

Replace the package filename with the actual version included in the archive.

Once the installation is complete, log out and select labwc from your display manager's session menu.

tip

Archcraft users can install the provided package directly. Manual configuration deployment and dependency installation are not required for this installation method.

Archcraft Prime / WSE

labwc is not pre-installed in the Archcraft WSE or Archcraft Prime ISOs.

You can still install it separately using the Archcraft installation package.


Configuration​

The labwc desktop is built around a collection of independently configurable components, each responsible for a specific part of the desktop experience. These components are integrated through configuration files, scripts, and shared resources to provide a consistent and cohesive environment.

This section provides an overview of the configuration structure, explains the purpose of each component, and identifies the files you can modify to customize your desktop.

Configuration Structure​

The main configuration files are stored in ~/.config/labwc. This directory contains the compositor settings, application configurations, themes, wallpapers, and scripts used throughout the desktop.

The directory structure is organized as follows:

~/.config
└── labwc
├── alacritty # Alacritty terminal configuration
├── dock # Crystal Dock configuration
├── foot # Foot terminal configuration
├── kitty # Kitty terminal configuration
├── mako # Notification daemon configuration
├── osd # OSD scripts and configuration
├── rofi # Rofi themes and configuration
├── scripts # Desktop utilities and helper scripts
├── themes # Theme definitions and management scripts
├── veila # Veila lockscreen configuration and themes
├── wallpapers # Desktop wallpapers
├── waybar # Waybar configuration and modules
├── wlogout # Wlogout configuration
├── wofi # Wofi configuration
├── autostart # Session startup commands
├── environment # Environment variables
├── hyprlock.conf # Hyprlock configuration
├── kanshi.conf # Display profile configuration
├── menu-glyphs.xml.in # Menu template
├── menu-icons.xml.in # Menu template
├── menu-minimal.xml.in # Menu template
├── menu-simple.xml.in # Menu template
├── menu.xml # Compositor menu configuration
├── rc.xml # Main labwc configuration
├── shutdown # Session shutdown commands
└── themerc-override # Window decoration theme overrides

/usr/share/archcraft
└── labwc
├── icons # Icons used by compositor menus
├── menulib # Shared pipemenu functions
└── pipemenus # Compositor pipemenu scripts
Configuration Locations

The desktop configuration is organized across two directories:

  • ~/.config/labwc contains user-level configuration files, application settings, themes, and scripts.
  • /usr/share/archcraft/labwc contains shared resources used by the labwc configuration, including menu icons, pipemenu scripts, and shared menu functions.

Both directories are part of the labwc configuration and should be deployed at their respective paths, regardless of the Linux distribution being used.

Terminal Emulators​

The desktop includes three configured terminal emulators: Alacritty, Kitty, and Foot.

Alacritty is the default terminal, while Kitty and Foot are available as alternatives. Each terminal is launched with its corresponding configuration files from the labwc configuration directory.

Alacritty is the default terminal emulator. Its configuration is stored in ~/.config/labwc/alacritty and organized into separate files for general settings, appearance, colors, and fonts.

FileDescription
alacritty.tomlMain configuration file
appearance.tomlAppearance settings
colors.tomlColor scheme
fonts.tomlFont settings

For detailed configuration options, refer to the Alacritty documentation or run man 5 alacritty in a terminal.

Notifications​

Mako is used as the notification daemon, handling desktop notifications from applications and system utilities.

The configuration is stored in:

~/.config/labwc/mako/config

You can modify this file to customize notification appearance, positioning, timing, and other supported options.

For a complete list of available settings, refer to the Mako documentation or run man 5 mako in a terminal.

Wallpaper Management​

swaybg is used to display desktop wallpapers, while the rofi-wallpaper applet provides a convenient interface for managing them.

The applet supports multi-monitor setups and saves wallpaper preferences, allowing your selected wallpapers to persist across sessions.

To change your wallpaper, launch the applet using Super + Z or navigate to Preferences > Change Wallpaper in the Labwc menu.

Desktop Interface​

The rofi-appearance applet provides a convenient way to customize the desktop interface in your Labwc session.

You can use it to change the GTK theme, icon theme, cursor theme, and fonts. Your appearance preferences are saved and persist across sessions, so your selected settings are restored automatically.

To customize the desktop interface, launch the applet using Super + A or navigate to Preferences > Change Appearance in the Labwc menu.

Status Bar​

Waybar is used as the desktop status bar, providing access to workspaces, system information, connectivity, audio controls, and other desktop utilities.

Its configuration is stored in ~/.config/labwc/waybar.

The configuration is divided into several files and directories:

File / DirectoryDescription
waybar/configMain Waybar configuration
waybar/modules/Individual module configurations
waybar/menus/Menu configurations
waybar/style.cssMain stylesheet
waybar/colors.cssColor definitions

You can modify the main configuration to add, remove, rearrange modules or switch layout. Use the CSS files to customize the appearance of the status bar.

For available modules and configuration options, refer to the Waybar documentation or run man waybar in a terminal.

Dock​

Crystal Dock is used to provide an application dock for the desktop. Its configuration is stored in ~/.config/labwc/dock/labwc.

The dock configuration is divided into two files:

FileDescription
appearance.confControls the dock's appearance, including themes, colors, and icon size
panel_1.confControls panel settings, including visibility and screen position

On-Screen Display (OSD)​

The desktop includes a custom On-Screen Display (OSD) implemented in Python. It provides visual feedback for system controls such as volume, brightness, and other supported actions.

The OSD configuration is stored in ~/.config/labwc/osd.

File / DirectoryDescription
osd.pyMain OSD script
osd.confControls the OSD's appearance and positioning, including margins, padding, and colors
icons/Icons used by the OSD

Lock Screen​

The desktop provides three lock screen implementations: Veila, Hyprlock and swaylock.

Veila is the primary lock screen, featuring its own configuration and theme system. Hyprlock is included as an alternative. Swaylock is used as fallback lockscreen.

Veila is the default lock screen. Its configuration is stored in:

~/.config/labwc/veila/
├── config.toml
└── themes/
File / DirectoryDescription
config.tomlMain Veila configuration
themes/Veila theme files

Launchers and Applets​

The desktop provides several application launchers and utility menus for common tasks. These are primarily powered by Rofi, with Wofi and Wlogout available as alternatives for specific functions.

Rofi is the primary application launcher and menu framework. It is used for launching applications, executing commands, managing clipboard history, controlling media playback, and accessing various system utilities.

The scripts responsible for these functions are located in:

~/.config/labwc/scripts/

The available launchers and applets include:

ScriptDescription
rofi-appearanceBrowse and apply gtk, icon, cursor themes and fonts
rofi-askpassPassword prompt frontend for sudo
rofi-asrootLaunch applications with elevated privileges
rofi-bluetoothDiscover and connect to Bluetooth devices
rofi-clipboardBrowse and manage clipboard history
rofi-launcherApplication launcher and task manager
rofi-mpdControl MPD music playback
rofi-mprisControl media players through MPRIS
rofi-networkManage network connections
rofi-powermenuAccess power and session management options
rofi-runnerExecute commands
rofi-screenshotCapture screenshots using Grim
rofi-spotifyControl Spotify playback
rofi-themesBrowse and switch desktop themes
rofi-wallpapersBrowse and apply wallpapers

Customizing Rofi​

Rofi's appearance is controlled through configuration files stored in ~/.config/labwc/rofi.

Each launcher or applet has its own theme file. For example, to customize the application launcher, edit:

~/.config/labwc/rofi/launcher.rasi

Shared appearance, color and font definitions are maintained separately:

FileDescription
rofi/shared/colors.rasiShared color definitions
rofi/shared/fonts.rasiShared font definitions
rofi/shared/window.rasiShared appearance definitions

You can modify these files to customize the appearance of individual menus or adjust their shared styling.

For more information, refer to the Rofi documentation or run man rofi-theme in a terminal.

Display Management​

Kanshi is used to manage display configurations and automatically apply monitor profiles when displays are connected or disconnected.

The configuration is stored in:

~/.config/labwc/kanshi.conf

This file contains display profiles and their associated output settings. You can define different profiles for laptop-only, external-monitor, and multi-monitor setups.

To identify available display outputs and their supported modes, run:

wlr-randr

Use the output names and available display modes when defining your profiles in kanshi.conf.

For more information about supported profile options, refer to the Kanshi documentation.

labwc Compositor​

The compositor itself is configured through a set of files stored in ~/.config/labwc. These files control session startup, environment variables, window management, menus, and window decorations.

FileDescription
rc.xmlMain compositor configuration, including keybindings, window rules, and other settings
autostartCommands executed when the labwc session starts
shutdownCommands executed when the session ends
environmentEnvironment variables for the session
menu.xmlDesktop menu definition
themerc-overrideWindow decoration theme overrides

The configuration also includes menu templates (menu-*.xml.in) used to generate different desktop menu layouts.

For details about available settings and supported options, refer to the official labwc documentation.

Theme Management​

The desktop includes a centralized theme management system that coordinates the appearance of its various components.

Rather than maintaining separate color configurations for every application, the theme engine uses shared functions and templates to generate and update component-specific configurations.

The theme engine is located in:

~/.config/labwc/themes/
├── apply-theme
├── functions/
├── templates/
└── themes/
File / DirectoryDescription
apply-themeMain theme application script that executes the theme functions
functions/Functions responsible for sourcing theme data, generating colors, and updating component configurations
templates/Configuration templates used by the theme engine
themes/Static theme definitions

How It Works​

The theme engine follows a centralized workflow:

  1. A theme is selected through the theme applet or desktop menu.
  2. The apply-theme script is executed.
  3. The corresponding theme functions are sourced and executed.
  4. Theme colors and other required settings are generated from the selected theme.
  5. The relevant component configurations are updated using the provided templates.

This keeps the appearance of the desktop components synchronized whenever a new theme is applied.

Static and Dynamic Themes​

The configuration includes a collection of predefined static themes, each with its own color scheme and associated appearance settings.

Dynamic themes are also supported through pywal, which generates color schemes based on wallpaper colors.

A theme change updates the appearance of the entire desktop, including:

  • Desktop: Wallpaper and labwc theme
  • Terminals: Alacritty, Kitty, and Foot
  • Panels and notifications: Waybar, Crystal Dock, Mako, and OSD
  • Launchers and menus: Rofi, Wofi, and Wlogout
  • Lockscreens: Veila and Hyprlock
  • Applications: GTK theme, Geany color schemes, and Satty window colors
  • Colors: Shared color palette used across the desktop components

For information about available themes and how to switch between them, see the Themes section.

Configuration Compatibility

The desktop's theme engine updates configuration files across multiple components to maintain a consistent appearance. This includes terminal emulators, Waybar, Rofi, Wofi, Mako, Wlogout, dock, OSD, and lock screen configurations.

Avoid changing the structure, filenames, or expected variables of theme-managed configuration files unless you also update the corresponding theme functions and templates. Otherwise, theme switching may fail or overwrite your customizations.

For persistent customizations, prefer modifying the appropriate theme functions rather than editing generated configuration files directly.


Keybindings​

The labwc configuration includes keyboard shortcuts for launching applications, managing windows, navigating workspaces, controlling displays, and accessing desktop utilities.

Modifier Keys​

KeyDescription
WSuper / Windows key
CControl
AAlt
SShift

For example, W-Return means Super + Enter, while W-C-Right means Super + Control + Right Arrow.

Applications and Terminals​

ShortcutAction
W-ReturnOpen Alacritty terminal
W-S-ReturnOpen Kitty terminal
W-A-ReturnOpen Foot terminal
W-C-ReturnOpen Foot terminal in selected geometry
W-fOpen file manager (Thunar)
W-wOpen web browser (Firefox)
W-eOpen text editor (Geany)

Application Launcher and Applets​

ShortcutAction
SuperOpen application launcher
W-dOpen application launcher
A-F1Open application launcher
A-F2Open command runner
W-nOpen network manager
W-bOpen Bluetooth manager
W-mOpen media player controls
W-xOpen power menu
W-sOpen screenshot menu
W-rOpen application as root
W-vOpen clipboard manager
W-tOpen theme selector
W-aOpen appearance selector
W-zOpen wallpaper selector
ShortcutAction
W-SpaceOpen desktop menu at the cursor
A-SpaceOpen focused window's menu
A-S-SpaceOpen combined window list
C-S-SpaceOpen window workspace menu
C-A-SpaceOpen application menu

Window Switching​

ShortcutAction
W-TabCycle through windows across all workspaces and outputs
A-TabCycle through windows on the current workspace and output

Workspace Navigation​

ShortcutAction
W-1 to W-5Switch to workspace 1–5
W-0Switch to the last workspace
C-A-RightMove to the next workspace
C-A-LeftMove to the previous workspace
C-A-S-RightMove to the next occupied workspace
C-A-S-LeftMove to the previous occupied workspace
W-S-1 to W-S-5Send focused window to workspace 1–5
W-S-0Send focused window to the last workspace
W-S-RightSend focused window to the next workspace
W-S-LeftSend focused window to the previous workspace
W-A-S-RightSend focused window to the next occupied workspace
W-A-S-LeftSend focused window to the previous occupied workspace

Display and Monitor Management​

ShortcutAction
W-C-1Focus display eDP-1
W-C-2Focus display HDMI-A-1
W-CommaFocus the display to the left
W-PeriodFocus the display to the right
W-C-S-1Move focused window to eDP-1
W-C-S-2Move focused window to HDMI-A-1
W-S-CommaMove focused window to the display on the left
W-S-PeriodMove focused window to the display on the right
W-S-EqualCreate the ScreenCasting virtual output
W-S-MinusRemove the ScreenCasting virtual output

Note: The numbered display shortcuts use the output names eDP-1 and HDMI-A-1. If your displays use different names, update the corresponding bindings in rc.xml. The virtual output shortcut also contains display-specific resolution and scaling commands.

Window Positioning and Resizing​

ShortcutAction
W-LeftSnap window to the left edge
W-RightSnap window to the right edge
W-UpMaximize window
W-DownSnap window to the center
W-S-UpSnap window to the top edge
W-S-DownSnap window to the bottom edge
W-A-UpMove window upward
W-A-DownMove window downward
W-A-LeftMove window left
W-A-RightMove window right
W-C-RightIncrease window width
W-C-LeftDecrease window width
W-C-DownIncrease window height
W-C-UpDecrease window height

The following shortcuts position windows in the four corners:

ShortcutAction
W-hMove window to the top-left corner
W-kMove window to the top-right corner
W-jMove window to the bottom-left corner
W-lMove window to the bottom-right corner
W-S-hSnap window to the top-left corner
W-S-kSnap window to the top-right corner
W-S-jSnap window to the bottom-left corner
W-S-lSnap window to the bottom-right corner

Window Actions​

ShortcutAction
W-cClose focused window
W-qForcefully terminate focused window
A-F4Close focused window
A-F5Minimize focused window
A-F6Toggle maximize
A-F7Toggle window shading
A-F8Toggle window decorations
A-F9Toggle window visibility across all workspaces
A-F10Toggle fullscreen
A-F11Toggle always on top
A-F12Toggle always on bottom
W-S-dToggle desktop visibility
W-EscapeEnable or disable keyboard shortcuts
W-S-tToggle tearing

Screenshots​

ShortcutAction
PrintCapture screenshot immediately
A-PrintCapture screenshot after 5 seconds
S-PrintCapture screenshot after 10 seconds
C-PrintCapture the focused window
W-PrintCapture a selected area

Hardware Controls​

ShortcutAction
XF86MonBrightnessUpIncrease screen brightness
XF86MonBrightnessDownDecrease screen brightness
XF86AudioRaiseVolumeIncrease audio volume
XF86AudioLowerVolumeDecrease audio volume
XF86AudioMuteToggle audio mute
XF86AudioMicMuteToggle microphone mute
XF86AudioPlayPlay or pause media
XF86AudioStopStop media playback
XF86AudioPrevPlay previous track
XF86AudioNextPlay next track

Command-line Utilities​

ShortcutAction
C-A-tOpen Alacritty in fullscreen
C-A-vOpen Vim in Alacritty
C-A-hOpen htop in Alacritty
C-A-rOpen Ranger in Alacritty

Session and Desktop Utilities​

ShortcutAction
C-A-lLock the screen using Veila
C-A-DeleteExit labwc after confirmation
C-S-rReload labwc configuration
W-pOpen color picker
W-SlashDismiss all notifications
W-EqualZoom in
W-MinusZoom out
W-BackslashToggle screen magnification

Mouse Bindings​

Mouse bindings provide additional ways to move, resize, and control windows without relying on keyboard shortcuts.

Window Movement and Resizing​

Mouse ActionResult
W + Left-click on window frameFocus and raise window
W + Left-drag on window frameMove window
W + Right-click on window frameFocus and raise window
W + Right-drag on window frameResize window
Left-click on window borderFocus and raise window
Left-drag on window borderResize window
Left-drag on window titleMove window
Double-click on window titleToggle maximize

Window Edges and Corners​

Mouse ActionResult
Double-click top or bottom edgeToggle vertical maximize
Double-click left or right edgeToggle horizontal maximize
W + Left-click top-left cornerMove window to top-left
W + Left-click top-right cornerMove window to top-right
W + Left-click bottom-left cornerMove window to bottom-left
W + Left-click bottom-right cornerMove window to bottom-right

Title Bar and Window Controls​

Mouse ActionResult
Left-click title barFocus and raise window
Right-click title barFocus and raise window
Scroll up on title barUnshade and focus window
Scroll down on title barUnfocus and shade window
Right-click window titleOpen window menu
Middle-click window titleOpen send-to-workspace menu
Left-click maximize buttonToggle maximize
Right-click maximize buttonToggle horizontal maximize
Middle-click maximize buttonToggle vertical maximize
Left-click shade buttonToggle window shading
Left-click all-desktops buttonToggle visibility across workspaces
Left-click minimize buttonMinimize window
Left-click close buttonClose window
Right-click close buttonForcefully terminate window

Window Menus and Icons​

Mouse ActionResult
Left-click window menu buttonOpen window menu
Right-click window menu buttonOpen send-to-workspace menu
Left-click window iconOpen window menu
Right-click window iconOpen send-to-workspace menu

Window Switching​

Mouse ActionResult
Side mouse buttonFocus next window
Extra mouse buttonFocus previous window

Desktop Menu and Workspace Navigation​

Mouse ActionResult
Left-click on desktopOpen desktop menu
Right-click on desktopOpen desktop menu
Middle-click on desktopOpen combined window list
Scroll up on desktopSwitch to previous workspace
Scroll down on desktopSwitch to next workspace

NVIDIA​

Labwc uses Wayland, which requires NVIDIA's DRM kernel mode setting (KMS) support to be enabled when using the proprietary NVIDIA driver.

Archcraft​

If you're using Archcraft and installed the provided Labwc package, no additional NVIDIA configuration should be necessary. Archcraft handles the required setup automatically.

Other Arch-based distributions​

If you're installing this configuration manually on Arch Linux or an Arch-based distribution, make sure the proprietary NVIDIA driver is installed and configured correctly.

1. Install the NVIDIA driver​

Install the appropriate NVIDIA driver package for your GPU and kernel.

Refer to the ArchWiki NVIDIA guide for driver selection and installation instructions.

2. Verify DRM kernel mode setting​

Wayland compositors require NVIDIA DRM modesetting. On current NVIDIA driver packages, this is generally enabled by default.

Check its current status:

$ cat /sys/module/nvidia_drm/parameters/modeset

The expected output is:

Y

If the output is N, or the parameter is not enabled, consult the NVIDIA documentation for your driver version.

For NVIDIA drivers older than version 560, you may need to enable modesetting manually by adding the following kernel parameter:

nvidia_drm.modeset=1

Add it to your bootloader's kernel command line and regenerate the bootloader configuration if required.

For GRUB, edit /etc/default/grub and append the parameter to GRUB_CMDLINE_LINUX_DEFAULT:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia_drm.modeset=1"

Then regenerate the GRUB configuration:

$ sudo grub-mkconfig -o /boot/grub/grub.cfg

3. Enable early module loading (Optional)​

If you experience display initialization issues or need the NVIDIA modules loaded during the initramfs stage, you can configure early module loading.

For systems using mkinitcpio, edit /etc/mkinitcpio.conf and add the NVIDIA modules to the MODULES array:

MODULES=(nvidia nvidia_modeset nvidia_uvm nvidia_drm)

Preserve any existing modules in the array rather than replacing them.

Regenerate the initramfs:

$ sudo mkinitcpio -P

This step is not required for every NVIDIA installation. Use it when early loading is needed.

4. Reboot and verify​

Reboot your system and start the Labwc session. You can verify that DRM modesetting is enabled by checking:

$ cat /sys/module/nvidia_drm/parameters/modeset

The expected result is Y.

Other distributions​

The instructions above are specific to Arch Linux and systems using mkinitcpio and GRUB. Other distributions may use different driver packages, initramfs generators, and bootloaders.

Install the appropriate NVIDIA driver and follow your distribution's documentation to enable DRM kernel mode setting and, if necessary, early module loading.

Further Reading​


Screenshots & Themes​

Explore the Labwc desktop, its collection of themes, dynamic color schemes, and lock screen designs. The screenshots below showcase the different visual styles and customization options available with this setup.

Desktop​

A look at the labwc desktop, showcasing its layout, components, and overall appearance.

Desktop 1Desktop 2Desktop 3Desktop 4Desktop 5
imgimgimgimgimg
Desktop 6Desktop 7Desktop 8Desktop 9Desktop 10
imgimgimgimgimg
Desktop 11Desktop 12Desktop 13Desktop 14Desktop 15
imgimgimgimgimg
Desktop 16Desktop 17Desktop 18Desktop 19Desktop 20
imgimgimgimgimg
Desktop 21Desktop 22Desktop 23Desktop 24Desktop 25
imgimgimgimgimg
Desktop 26Desktop 27Desktop 28Desktop 29Desktop 30
imgimgimgimgimg

Themes​

The desktop includes 45 handcrafted static themes, each with its own color palette and visual identity, with support for dynamically generated color schemes using pywal. Browse the available themes via Theme applet or in the labwc menu under Preferences → Change Theme.

The theme menu lists all available static themes, along with a Random Theme option at the top. Selecting any theme applies it across the desktop.

Static Themes​

Browse the collection of available themes below.

DefaultAbyssAfterglowAmethystAsh
imgimgimgimgimg
AuroraBlossomDraculaDreamwaveDusk
imgimgimgimgimg
EclipseEmberEverforestFrappeGruvbox
imgimgimgimgimg
HanamiIvoryKanagawaKoiLagoon
imgimgimgimgimg
LandscapeLiquidMacchiatoMarigoldMatrix
imgimgimgimgimg
MechMochaMonsoonMountainNightbloom
imgimgimgimgimg
NightcityNordObsidianOrchidPelagic
imgimgimgimgimg
ShinkaiSkyscraperSolitudeSolsticeSteel
imgimgimgimgimg
TideTokyoTokyonightWisteriaWoodland
imgimgimgimgimg

Dynamic Themes​

Dynamic themes use pywal to generate a color palette from a randomly selected wallpaper from ~/Pictures/wallpapers, then applies the resulting theme across the desktop.

You can generate and apply a random dynamic theme using either of these methods:

  • Open the theme applet with Super + T and select Random Theme.
  • Right-click on the desktop and navigate to Preferences → Change Theme, then select Random Theme.

gif

Lock Screens​

Both Veila and Hyprlock are supported as lockscreen options. Static and dynamic themes are applied to both, keeping their appearance consistent with the rest of the desktop.

Veila​

Static ThemeDynamic Theme
gifgif

Hyprlock​

Static ThemeDynamic Theme
gifgif

Managing Themes​

You can browse and apply themes directly from the desktop without manually editing configuration files.

Open the theme selector:

  • Press Super + T to launch the theme applet.
  • Alternatively, right-click on the desktop and navigate to Preferences → Change Theme.

Apply a theme:

  • Browse the available static themes and select the one you want to use.
  • To generate a new wallpaper-based color scheme, select Random Theme.

The theme system applies the selected appearance across the supported desktop components, keeping their colors and styling consistent.


Misc Features​

Lock Screen Selection​

The ac-lockscreen script selects the lock screen automatically based on which supported program is installed. It checks the available implementations in the following priority order:

  1. Veila — preferred when available.
  2. Hyprlock — used when Veila is not installed.
  3. Swaylock — used as the fallback when neither Veila nor Hyprlock is available.

The selection logic is handled by ~/.config/labwc/scripts/ac-lockscreen. The script uses the first available implementation in the listed priority order. To change the preference, edit the script and adjust the order in which the lock screen programs are checked.

Idle and Power Management​

Swayidle manages idle behavior during the Labwc session. It is launched from ~/.config/labwc/autostart and runs a sequence of actions when the system remains idle for configured periods.

The default configuration is:

swayidle -w \
timeout 150 "light -O && light -S 5" \
resume 'light -I' \
timeout 300 "$SCRIPTS_DIR/ac-lockscreen" \
timeout 600 'wlopm --off "*"' \
resume 'wlopm --on "*"' \
before-sleep "$SCRIPTS_DIR/ac-lockscreen" \
timeout 1200 'systemctl suspend' \
>/dev/null 2>&1 &

The default idle actions are:

TimeoutAction
150 secondsSave the current brightness and dim the display to 5%.
On activityRestore the saved brightness.
300 secondsLock the session using the configured lockscreen selection script.
600 secondsTurn off all displays using wlopm.
On activityTurn the displays back on.
Before system sleepLock the session before the system suspends.
1200 secondsSuspend the system using systemctl suspend.

You can change the idle timers or commands by editing the Swayidle block in ~/.config/labwc/autostart. For example, adjust the timeout values to change when the screen dims, the session locks, displays turn off, or the system suspends.

Screen Capture and Recording​

The desktop includes dedicated screenshot and screen-recording workflows, accessible through the configured Rofi applets and scripts.

Screenshots​

Screenshots are captured with Grim and Slurp, with Satty available for annotating and editing captures. The screenshot utility provides the following modes:

  • Capture the full screen and open it in Satty.
  • Select a screen area and open the capture in Satty.
  • Select a window and open the capture in Satty.
  • Capture the full screen after a 5-second delay.
  • Capture the full screen after a 10-second delay.
  • Capture the full screen without opening the editor.
  • Select an area and capture it without opening the editor.

The screenshot applet/menu/keybinds provides access to these capture modes. You can use the corresponding options when invoking the screenshot script directly.

Make sure you press Control + S to save it, or Right Click to copy it to clipboard directly without saving it.

Screen Recording​

Screen recording is powered by GPU Screen Recorder. The recording frontend lets you choose between recording the entire desktop of your choice or a selected area, and select an audio configuration:

  • No audio
  • System audio
  • Microphone
  • System audio and microphone

The frontend also provides recording settings, allowing you to adjust the recording configuration before starting a capture.


FAQs​

How do I uninstall the configuration or restore my previous setup?

The uninstall procedure depends on how you installed the configuration.

Manual installation on other distributions

Remove the user configuration and the shared Labwc resources installed by this setup:

rm -rf ~/.config/labwc
sudo rm -rf /usr/share/archcraft/labwc

Only remove /usr/share/archcraft/labwc if it was installed for this setup and is not being used by another configuration.

Restore a previous user configuration

If you followed the manual installation instructions, your previous ~/.config/labwc directory was moved to a timestamped backup. Remove the newly installed configuration and rename your backup directory back to its original location. Replace the example timestamp below with the one created during installation:

rm -rf ~/.config/labwc
mv ~/.config/labwc.backup-YYYYMMDD-HHMMSS ~/.config/labwc

The installation instructions do not create a backup of /usr/share/archcraft/labwc. If you need to restore pre-existing shared resources, make sure you back them up separately before installation.

Archcraft package installation

Remove the installed package using pacman:

sudo pacman -R archcraft-labwc

If the package leaves the user configuration in your home directory, remove ~/.config/labwc separately if you no longer need it.

How do I update to the latest configuration?

Updates depend on how you obtained the configuration:

  • Ko-fi: Download your purchased version again from your Ko-fi order. New versions require a separate purchase.
  • GitHub Sponsors: Download the latest release from the private repository while your sponsorship is active.

Once downloaded, follow the installation instructions to apply the updated configuration.

Can I install this setup on distributions other than Archcraft?

Yes. The configuration can be used on other Linux distributions, provided all required dependencies are installed.

Refer to the Installation section for the dependency list and installation instructions.

Why is my cursor invisible?

With certain graphics drivers or virtual machines, the hardware cursor may not render correctly.

You can work around this by enabling software cursors. Edit ~/.config/labwc/environment and add:

WLR_NO_HARDWARE_CURSORS=1

Restart your Labwc session for the change to take effect.

How do I change the GTK theme, icons, fonts, and cursor?

Use the rofi-appearance (press Super + A) applet to change the GTK theme, icon theme, cursor theme, and fonts. Your selections are saved and persist across sessions.

Alternatively, you can edit the corresponding variables in ~/.config/labwc/scripts/ac-gtkthemes:

THEME='Dracula-Pink'
ICONS='Zafiro-Nord-Black'
FONT='Noto Sans 9'
CURSOR='Bibata'

Save the changes and execute the script to apply your settings.

How do I manage multiple monitors and display resolutions?

Display profiles are managed by Kanshi.

  1. Run wlr-randr in a terminal to identify your connected displays and their supported modes.
  2. Edit ~/.config/labwc/kanshi.conf and configure your display profiles.

For example:

## Laptop — HiDPI
profile LaptopOnly {
output "Lenovo*" mode 2944x1840@60Hz position 0,0 scale 2.0 transform normal adaptive_sync off
}

## External monitor only
profile MonitorOnly {
output "Samsung*" mode 1920x1080@60Hz position 0,0 scale 1.0 transform normal adaptive_sync off
}

## Dual-screen setup
profile DualScreen {
output "Lenovo*" mode 2944x1840@90Hz position 0,0 scale 2.0 transform normal adaptive_sync off
output "Samsung*" mode 1920x1080@60Hz position 1472,0 scale 1.0 transform normal adaptive_sync off
}

Replace the output names, resolutions, refresh rates, positions, and scaling values with those appropriate for your displays.

Why is Alacritty not working on my computer?

Alacritty uses OpenGL for rendering, which may cause issues on some hardware or graphics configurations.

You can try launching it with software rendering enabled:

LIBGL_ALWAYS_SOFTWARE=1 alacritty

To make this permanent, update the Alacritty launch command in ~/.config/labwc/rc.xml or the corresponding launcher script.

Alternatively, edit /usr/share/applications/Alacritty.desktop and change its Exec entry to:

Exec=env LIBGL_ALWAYS_SOFTWARE=1 alacritty
Why are my configuration changes overwritten when I change themes?

The theme engine updates configuration files across multiple desktop components to keep the appearance consistent.

Some files, including terminal colors, Waybar styles, Rofi colors, wallpaper settings, and lockscreen configurations, are regenerated when a theme is applied.

For persistent customizations, modify the appropriate theme templates, functions, or static theme definitions in ~/.config/labwc/themes rather than editing generated configuration files directly.

Refer to the Theme Management section for more details.

How do I change the desktop wallpaper?

Use the rofi-wallpaper (press Super + Z) applet to select and apply a wallpaper. It supports multi-monitor setups and saves your wallpaper preferences across sessions.

Alternatively, you can set a custom wallpaper by editing the WALLPAPER variable in ~/.config/labwc/scripts/ac-wallpaper:

WALLPAPER='/path/to/your/wallpaper'

Keep in mind that applying a theme updates the wallpaper through the theme engine, so your manual change may be overwritten when switching themes.

How do dynamic themes work?

Dynamic themes use pywal to generate a color palette from a randomly selected wallpaper in ~/Pictures/Wallpapers.

Select Random Theme from either the Rofi theme applet (Super+T) or the Labwc menu under Preferences → Change Theme.

The generated palette is applied across the desktop, including the wallpaper, terminals, panels, launchers, applications, and both supported lockscreens.

How do I change or add keyboard shortcuts?

All Labwc keyboard and mouse bindings are defined in:

~/.config/labwc/rc.xml

Edit this file to modify existing shortcuts or add your own bindings.

After making changes, reload the Labwc configuration using:

Control + Shift + R

You can also refer to the Keybindings section for the available shortcuts.