# Troubleshooting Start with `libbui doctor`. It checks the terminal (colour depth, Unicode, image support, size), the configuration and the pairing without touching the network; `libbui doctor --online` also asks Libby once whether the pairing still works. - **"This device is not paired"** (exit code 3): pair with a fresh code. Codes expire after a short time, so generate a new one if pairing fails. - **"Your library has suspended this card"**: contact your library. libbui has stopped using that card and will not retry. - **A title says "Download not supported"**: libbui has no download path for the offered format. Press `o` to open the title in Libby and see its other reading or device-transfer options. - **"libbui could not tell whether registering this device with Adobe finished"**: the first Adobe download was interrupted while it registered this device. libbui registers again by itself 15 minutes later; run `libbui adobe reset` to do it at once. Registering again uses no Adobe device activation. - **Odd characters or broken borders**: use a font with box drawing characters, or start with `--ascii`. - **Colours look wrong**: try `--theme dark`, `--theme light` or `--theme high-contrast`; set `COLORTERM=truecolor` if your terminal supports it. - **Covers do not show**: run inside a terminal with the kitty, iTerm2 or sixel graphics protocol, or set `images = "halfblocks"`. - **Something else**: run with `--log libbui=debug,libby=debug` and look in the log folder from `libbui paths`. Logs never contain your token.