0.9.8 Windows crashing #21

Closed
opened 2026-05-14 08:55:06 +02:00 by harrygeier · 2 comments

Windows compiled version crashing , see screenshot

Win10

Python source works , but i do not see the 0.9.8 improvements..like uploaded prints etc. at all
data dir is not created too

Windows compiled version crashing , see screenshot Win10 Python source works , but i do not see the 0.9.8 improvements..like uploaded prints etc. at all data dir is not created too
Owner

Thanks for the report and the screenshot — that pinpointed it immediately.

Root cause: release.sh synced the source files into the Windows build repo, but missed config_loader.py (where list_printers() lives). The 0.9.8 kx-bridge.exe was therefore built against an outdated config_loader.py from a previous version → AttributeError: module 'config_loader' has no attribute 'list_printers' on startup.

Fixed:

Regarding the Python source: since 0.9.8 you can run kx-bridge without Docker — config/ and data/ are created next to the executable (or next to kobrax_moonraker_bridge.py when running from source). If you don't see data/ and the new features, you're likely running an older kobrax_moonraker_bridge.py. Make sure your source files are from the v0.9.8 release — specifically you need the matching config_loader.py, kobrax_client.py and env_loader.py alongside the main script.

On first start with no printer configured, the UI opens directly on the Printers tab with a "+ Add printer" button — just enter the printer IP and the credentials are imported automatically. No more wading through the settings dialog.

Closing this — please re-open if the new EXE still misbehaves.

Thanks for the report and the screenshot — that pinpointed it immediately. **Root cause:** `release.sh` synced the source files into the Windows build repo, but missed `config_loader.py` (where `list_printers()` lives). The 0.9.8 `kx-bridge.exe` was therefore built against an outdated `config_loader.py` from a previous version → `AttributeError: module 'config_loader' has no attribute 'list_printers'` on startup. **Fixed:** - Replaced the `kx-bridge-windows.zip` asset on the v0.9.8 release with a freshly built EXE that contains the correct `config_loader.py`. Same download link — please grab it again: https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases/download/v0.9.8/kx-bridge-windows.zip - Verified the new EXE contains the new symbols (`list_printers`, `_kx_fetch_credentials`, `handle_kx_printer_add`, `_default_data_dir`, …). - `SHA256SUMS.txt` updated with the new hash (`196d3492…f132fb` for the ZIP, `48c2aa11…6a25` for the EXE). - Fixed `release.sh` to include `config_loader.py` in the Windows build sync (commit https://gitea.it-drui.de/viewit/KX-Bridge/commit/30168f2) — won't happen again on future releases. **Regarding the Python source:** since 0.9.8 you can run `kx-bridge` without Docker — `config/` and `data/` are created **next to the executable** (or next to `kobrax_moonraker_bridge.py` when running from source). If you don't see `data/` and the new features, you're likely running an older `kobrax_moonraker_bridge.py`. Make sure your source files are from the [v0.9.8 release](https://gitea.it-drui.de/viewit/KX-Bridge-Release/src/tag/v0.9.8) — specifically you need the matching `config_loader.py`, `kobrax_client.py` and `env_loader.py` alongside the main script. On first start with no printer configured, the UI opens directly on the Printers tab with a **"+ Add printer"** button — just enter the printer IP and the credentials are imported automatically. No more wading through the settings dialog. Closing this — please re-open if the new EXE still misbehaves.
Owner

Follow-up: while debugging the EXE crash we found a second bug in the same area — when the web UI was opened via the LAN IP (e.g. http://192.168.x.y:7125), the bridge was returning bridge_url: http://localhost:7125 in /kx/printers, which caused the browser to fire cross-origin requests from the LAN IP to localhost. Those got silently blocked and produced a flood of TypeError: Failed to fetch poll errors in the log.

Fixed in v0.9.9 — release with both fixes (Windows EXE startup + bridge_url): https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases/tag/v0.9.9

If you grabbed the patched 0.9.8 EXE earlier, please update to v0.9.9 to get rid of the poll-error spam too.

Follow-up: while debugging the EXE crash we found a second bug in the same area — when the web UI was opened via the LAN IP (e.g. `http://192.168.x.y:7125`), the bridge was returning `bridge_url: http://localhost:7125` in `/kx/printers`, which caused the browser to fire cross-origin requests from the LAN IP to `localhost`. Those got silently blocked and produced a flood of `TypeError: Failed to fetch` poll errors in the log. **Fixed in v0.9.9** — release with both fixes (Windows EXE startup + bridge_url): https://gitea.it-drui.de/viewit/KX-Bridge-Release/releases/tag/v0.9.9 If you grabbed the patched 0.9.8 EXE earlier, please update to v0.9.9 to get rid of the poll-error spam too.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: viewit/KX-Bridge-Release#21
No description provided.