-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
"Windows protected your PC" on first run. Expected. The build is unsigned — a code-signing certificate is a recurring cost that has not been taken on for a free tool. Click More info → Run anyway. Signing proves who published a file; it cannot prove a file is safe. The SHA-256 fingerprint gives you the same integrity guarantee for free, so verify that instead.
Antivirus flags the download. It may. PyInstaller single-file executables unpack themselves at runtime, which structurally resembles a packed dropper, and a newly published file has no reputation yet. UPX compression is explicitly disabled and full version information is embedded to reduce this. Verify the SHA-256, then report it to your vendor as a false positive — and please say which scanner, it is useful.
The icon looks generic in Explorer.
Windows icon cache, not the build; the icon is embedded at seven sizes. Run
ie4uinit.exe -show, or copy the file to a new name to confirm. A fresh
download never shows this.
The browser opens but the page is unstyled black text. The bundled assets did not unpack. Re-download and verify the checksum.
It will not start at all.
Read the log. It is written to logs/app.log:
| Build | Log location |
|---|---|
| Windows | next to the .exe, falling back to %LOCALAPPDATA%\BreakthroughSimulator\logs
|
| Linux | in the extracted folder, beside run-breakthrough-simulator.sh, falling back to ~/.local/state/BreakthroughSimulator
|
The first line of every run records the exact environment — Python, NumPy, SciPy, scikit-sundae, BLAS and the thread limits — and each solve appends its CVODE statistics. Include those lines when reporting a problem. The same text is visible in the app under Advanced Logs.
Port 8000 is already in use. Close the other program using it, or close a previous copy of this app that is still running, and try again. A running copy holds the port even after you close the browser tab, for about half a minute.
./run-breakthrough-simulator.sh: Permission denied.
The executable bit was lost — usually by copying through Windows, a zip tool or
a network share. bash run-breakthrough-simulator.sh works regardless, or
restore it: chmod +x run-breakthrough-simulator.sh install.sh BreakthroughSimulator/BreakthroughSimulator.
bad interpreter: /usr/bin/env bash^M.
Windows line endings in the script, not a missing interpreter. sed -i 's/\r$//' run-breakthrough-simulator.sh.
GLIBC_2.XX not found.
The build is compiled against the glibc of its build distribution. A newer
distribution runs it; an older one cannot. The release notes state which
distribution each build came from.
Nothing happens, or the binary is not found.
The download is a folder, not a single file. The launcher needs
BreakthroughSimulator/_internal/ beside it, so extract the whole archive and
keep the layout intact. Running the inner binary directly also works.
The application-menu entry does nothing.
install.sh writes absolute paths into the menu entry, so the entry breaks if
the folder moves or was in a temporary location. Re-run ./install.sh from the
folder's current location. It refuses /tmp outright — use
./install.sh --copy-to "$HOME/Applications" to relocate first. Remove an old
entry with ./install.sh --uninstall, or --uninstall --purge to delete the
folder and logs too.
The server starts but no browser opens.
The app looks for $BROWSER, then xdg-open, gio, gnome-open, kde-open,
x-www-browser, and the common browsers by name. Install xdg-utils or set
$BROWSER if none is present. Either way the address is always
http://127.0.0.1:8000 — open it yourself. The [browser] lines in the log say
which opener was tried and how it failed.
Every release ships a SHA256SUMS file. Check the file you received against it
before running:
certutil -hashfile BreakthroughSimulator-windows.exe SHA256 Windows
sha256sum -c SHA256SUMS Linux
Compare the result with the line for your file in SHA256SUMS. They must match
exactly. If they do not, the file is not the one that was published — delete it.
Each release also ships requirements-lock.txt, the exact library versions that
build was compiled from.
Wiki: Home · The Model · Isotherm Models · Mass Transfer · Adsorbent Presets · Using the App · Limitations · Privacy & Security · Troubleshooting