Troubleshooting

Is Wander behaving unexpectedly, crashing or refusing to do something? Kill it with fi This page explains how to find out the details and report the problem.

The action journal opens with the button on the left of the status bar. It records what happened during the session: which folders and files you opened and what you did in them, with timestamps. For an operation, you see where, how much and how long, and below it, a row per file: a renamed one as “old → new”, a failed one with the reason. A message that was replaced by the next one before you had time to read it is there too.

To report a problem, use ⋯ → “About Wander” → “Feedback” or Issues on GitHub. It helps to include the steps, what you expected and what happened, and the session log. Report a vulnerability privately, as described in SECURITY.md.

If Wander crashes, it offers a report: a prefilled GitHub issue and an archive in the crashes folder (see “Data and cache”). Nothing is sent automatically: it's up to you whether to send the report.

The session log is a technical file, one per launch, in the logs folder: version, system, opened folders, operations, errors. Paths in it are replaced by masks like <C:\~3fa91c\~0b2e4d.jpg> that show the drive, depth and extension but not the names, so you can attach the log to a report. To investigate a bug, turn on “Write real file paths” and “Record keystrokes, clicks and selection” in “Settings” → “Debug and reset”.

The “Debug” menu appears in ⋯ when you turn on “Show in the main menu” on the same page. Its “Session log” item opens the current session's log; the rest is for checks together with the author. The same page also has “Reset all settings…” at the bottom.