Logs

Sonora keeps a log file on every platform. It never leaves your machine unless you send it to someone, and if you're filing a bug, please do.

Location

SettingsGeneralLog fileOpen log opens it in your default text editor. On Windows it opens in Notepad. Or find it yourself:

Linux~/.local/state/sonora/sonora.log
Flatpak~/.var/app/io.github.nolight132.sonora/.local/state/sonora/sonora.log
macOS~/Library/Caches/sonora/sonora.log
Windows%LOCALAPPDATA%\sonora\sonora.log

The log is capped at 16 MB. When it fills up it becomes sonora.log.1 and a fresh file starts, so you never have more than 32 MB of logs. Sonora also keeps only the last five runs, the current one included, so grab the log soon after something goes wrong. Every run begins with a line naming the version that wrote it.

More detail

By default you get warnings and selected debug output. If a bug is hard to pin down, start Sonora with SONORA_LOG=debug and it logs everything.

Linux
SONORA_LOG=debug sonora
Flatpak
flatpak run --env=SONORA_LOG=debug io.github.nolight132.sonora
macOS, then start Sonora
launchctl setenv SONORA_LOG debug
Windows, then start Sonora
setx SONORA_LOG debug

On macOS and Windows the variable sticks around, and debug logs grow fast. Clear it when you're done with launchctl unsetenv SONORA_LOG on macOS or reg delete HKCU\Environment /v SONORA_LOG /f on Windows.

Terminal output

Start Sonora from a terminal and it also prints warnings to stderr. RUST_LOG controls that output and leaves the file alone. Windows builds don't open a console.