Known software issues

Some software issues deserve special mention. This is what this page is for.

Unfixed issues

baxter-oom

Trigger

Triggers during a measurement.

Symptoms

All subsequent measurements fail with:

[Errno 111] Connection refused

Recovery

Restart your BactoBox® to recover.

Metadata

🪲 Introduced in initial version

🔧 Fixed in N/A (not fixed yet)

🎲 Likelihood is Rare. Approximately 1 in 1000 measurements.

🌡️ Severity is Low. No data loss.

Fixed issues

wal-db-corruption

Trigger

Triggers after first connection to Access.

Symptoms

Symptoms include:

• Data loss (rare but this is the worst case scenario)
• Stuck at spinner

• Unable to start any program (even after reboot)

Recovery

First, try to restart your BactoBox®.

If you are unable to start any program, delete all user data and then restart your BactoBox®.

Metadata

🪲 Introduced in v2026.02-alpha.0

🔧 Fixed in v2026.02a . We accidentally released a POSIX advisory lock on the database.

🎲 Likelihood is Rare

🌡️ Severity is High. Worst case is complete data loss.

sudden-system-failure

Trigger

Triggers at any point in time.

Symptoms

One or more of the following happens:

• Screen hangs (freezes)
• Screen glitches
• Software becomes completely unresponsive to further user input (button presses)
• Device powers itself off
• Various error messages (e.g., "no response")

Recovery

Restart your BactoBox® to recover.

Metadata

🪲 Introduced in initial version

🔧 Fixed in v2024.03 . Was a bug in the spi-xilinx linux kernel driver. We sent a patch to Xilinx (now AMD).

🎲 Likelihood is Rare. Once every 100 hours if left powered on at idle. Slightly more frequent if device is under constant use.

🌡️ Severity is Low. No data loss.