Report a problem

A report that can be acted on says three things: which BeeBEEP, what happened, and what BeeBEEP wrote in its log while it happened.

What to send

• The version. Settings > About BeeBEEP shows it under the name, for example 6.0.0-1234. From a command line, beebeep --version prints the same, with the build's commit.
• The system. Its name and version, for example Windows 11 24H2.
• What happened. What you did, what you expected and what you saw, with the time it happened: the log is read by the time of day.
• The log of that day. BeeBEEP writes one file a day, beebeep-<year>-<month>-<day>.log, and deletes the ones older than 7 days, so send it soon. When you are asked for a more detailed one, turn on Settings > Log > Enable panic log, close and open BeeBEEP again, do what goes wrong once more, and send that day's file; then turn the panic log off.

Read the log before you send it: it names the people BeeBEEP met and the addresses of their computers, and a panic log holds more.

Where the log is

The log files are in BeeBEEP's data folder, with its settings and its database. On a computer, File > Open data folder opens it. A BeeBEEP started with --data-folder=<path> keeps them in that folder.

Windows

• Installed with the setup or the MSI: the folder %LOCALAPPDATA%\MarcoMastroddiSW\BeeBEEP, one for each Windows account. Type that line into the address bar of File Explorer to open it.
• The portable zip: the folder beebeep-data beside beebeep.exe, in the folder you unpacked, when that folder can be written; otherwise the installed copy's folder above.

An administrator may have moved the data folder for everyone; then it is where settings for administrators says.