zlaunch

Troubleshooting

Common issues and debugging

Debug Logging

Run zlaunch with verbose logging:

RUST_LOG=debug zlaunch

This outputs detailed information about configuration, compositor detection, IPC, and module initialization.


Common Issues

Daemon Won't Start

Error: Address already in use

A previous daemon didn't clean up. Remove the socket:

rm $XDG_RUNTIME_DIR/zlaunch.sock
zlaunch

Already running

Only one daemon can run at a time:

zlaunch quit
zlaunch

Launcher Doesn't Appear

Check compositor integration

echo $HYPRLAND_INSTANCE_SIGNATURE  # for Hyprland
echo $NIRI_SOCKET                   # for Niri

Window Switching Not Working

Unsupported compositor

Window switching requires Hyprland or Niri. KDE support is experimental. Other compositors fall back to no-op.

Socket permission issues

Verify you can access the compositor socket. Check $XDG_RUNTIME_DIR permissions.


Clipboard History Empty

IssueSolution
Protocol not supportedRequires wlr-data-control-v1 (KDE doesn't fully support)
Monitor not runningCheck debug logs for clipboard errors

Applications Not Launching

Check the .desktop file's Exec field—some apps have malformed entries.

Set $TERMINAL environment variable:

export TERMINAL=kitty

Add to your shell profile.

Apps inherit the daemon's environment. Restart daemon if you changed shell variables.


Theme Not Loading

IssueSolution
Theme not foundCheck name matches exactly (case-sensitive)
Custom themeVerify file is in ~/.config/zlaunch/themes/ with .toml extension
Invalid TOMLValidate syntax with a TOML checker

Config Not Applied

File location

Must be at ~/.config/zlaunch/config.toml (not ~/.zlaunch/config.toml)

Reload required

Most changes auto-reload. For major changes, run zlaunch reload.


High VRAM Usage

Set explicit window size:

window_size = [1920.0, 1080.0]

This prevents allocating an 8K buffer on some compositors.


Blur Not Working (Hyprland)

Ensure blur is enabled in Hyprland

decoration:blur:enabled = true

Check auto-blur is enabled

hyprland_auto_blur = true

Or add manual layer rules

layerrule = blur on,match:class zlaunch
layerrule = blur_popups on,match:class zlaunch
layerrule = ignore_alpha 0.35,match:class zlaunch

AI Mode Errors

IssueSolution
No responseVerify API key is set in environment
Ollama not workingEnsure service is running, model exists (ollama list)
Wrong providerzlaunch uses first configured: Ollama → Gemini → OpenAI → OpenRouter

Getting Help

If you can't resolve an issue:

  1. Run with RUST_LOG=debug and capture output
  2. Check existing issues on GitHub
  3. Open a new issue with:
    • Compositor and version
    • zlaunch version
    • Configuration file
    • Debug log output
    • Steps to reproduce

On this page