Logs and diagnostics
When something goes wrong, the window keeps a log, remembers what crashed, and says which libraries it needs and cannot find. None of it leaves the machine unless you send it.
The Diagnostics panel
Diagnostics, Ctrl+Shift+D or the Help menu, shows in one place:
- where passwords are kept;
- the log, as Log: and the file’s name, a line that opens the folder it is written in;
- Crashes: each kind of failure the application hit, how often, and Forget these;
- Libraries this application does not ship: whether Oracle Instant Client was found, and where to put it if not.
When one of them needs looking at, the window says Diagnostics: something needs looking at.
The log
The log is a text file a day, mantichora.2026-11-13.log and so on, and a new one when a file passes four megabytes, in the folder the panel opens: %LOCALAPPDATA%\dev.mantichora.desktop\logs on Windows, ~/Library/Logs/dev.mantichora.desktop on macOS and ~/.local/share/dev.mantichora.desktop/logs on Linux. Sixteen files are kept, and the oldest go first.
Crashes
A crash is written down on this machine, by its kind and where in the program it happened, never by a message that could quote your data. It goes anywhere only if you ticked Send crash reports, and then only a crash that happened after you did. The support page lists what a report holds.
Reporting a problem
Help → Copy this installation’s details copies one line, the version, the system and the processor, ready to paste. With it, say what you did, what you expected and what happened instead, and add the lines of the log from that moment. The support page says where reports go.