Usage
Logging
Where logs are written and how to adjust log output.
kwybars logs to stderr and to a file.
Default Log File
~/.local/state/kwybars/kwybars.logIf XDG_STATE_HOME is set, the log is written to:
$XDG_STATE_HOME/kwybars/kwybars.logkwybars doctor prints the path in use.
Adjust Log Level
Use KWYBARS_LOG or RUST_LOG to control the log level or filter:
KWYBARS_LOG=debug kwybarsOverride Log File Path
Use KWYBARS_LOG_FILE if you want to write logs to a different file:
KWYBARS_LOG_FILE=/tmp/kwybars.log kwybarsWhat You Will Find There
- which config file was found, or that the built-in defaults are used
- warnings about unknown, removed, or out-of-range config keys
- a missing theme or an overlay image that could not be read
- every config reload, and the error when a reload failed and the previous config was kept
- which monitors got a visualizer
- PipeWire connection problems
Notes
- timestamps use local time
- when the log file is larger than 1 MiB at startup, it is renamed to
kwybars.log.old(replacing an older one) and a new file is started - the file is the place to look when Kwybars was started from compositor autostart or the user service
- with the user service,
journalctl --user -u kwybars.serviceshows the same messages - the checking and config commands, such as
kwybars doctor, print their result and do not write to the log