BlueZ

Where BlueZ keeps its logs

BlueZ logs to journalctl -u bluetooth.service on Linux.

Paths are printed exactly as BlueZ writes them. Environment variables like %LOCALAPPDATA% and $XDG_STATE_HOME are never expanded, so a path can be pasted straight into a shell. Where a path differs between installer types or shipping flavours, each one is racked as its own card below - why that happens.

Finding your way around Linux.