[Bug] Linux arm64 (v3.12.2): RDP unusable — crash on missing 'undici', then ironrdp "invalid state" vs gnome-remote-desktop

Environment: Tempest Desktop v3.12.2, Linux arm64/aarch64 (Ubuntu 24.04, NVIDIA GB10). Installed from the official arm64 .deb. RDP target: an Ubuntu 24.04 host running gnome-remote-desktop 46 (FreeRDP 3.5.1 backend, NLA-required). SSH works flawlessly; RDP is completely unusable due to two separate bugs.

Bug 1 — main process crashes instantly on RDP connect (arm64 packaging)

Opening any RDP connection crashes the whole app. From journalctl:

Uncaught Exception:
    Error: Cannot find module 'undici'
    Require stack:
    - /opt/Tempest/resources/app.asar/out/main/index.js
        at Module._resolveFilename (node:internal/modules/cjs/loader:1507:15)

`out/main/index.js` does `require('undici')`, but **undici (declared ^7.0.0) is not present in the packaged node_modules on the arm64 build** — looks like an electron-builder files/asar omission for the arm64 target.

Workaround that fixes it: drop `undici@7` into `/opt/Tempest/resources/node_modules/` (Node resolves it there as the first real-FS path outside the read-only asar). RDP then launches.

## Bug 2 — ironrdp asserts an internal "invalid state" (after CredSSP succeeds)

After patching Bug 1, connecting to gnome-remote-desktop with NLA (CredSSP) + valid credentials fails at:

    connect finalize: [invalid state (this is a bug) @ ironrdp-connector-0.9.0/src/lib.rs:405] general error

The server requires NLA — `xfreerdp3 /sec:tls` and `/sec:rdp` are both rejected with HYBRID_REQUIRED_BY_SERVER; only `/sec:nla` is accepted. And **FreeRDP 3.5.1 connects to this exact host successfully** (NLA negotiates, CredSSP authenticates, proceeds into the RDP licensing/capability sequence). ironrdp 0.9.0 reaches post-CredSSP finalize and trips its own "invalid state (this is a bug)" assertion.

Repro: any gnome-remote-desktop (GNOME 46 "Remote Desktop") target. Since FreeRDP handles it fine, this looks like an ironrdp connector bug — please bump/patch ironrdp. Happy to provide full logs, thanks!

Hi, we’ll fix it and get back to you soon.

Hi, please try the v3.12.4 release, and hopefully it resolves this issue :slight_smile:

You are awesome , it worked buit i will test further

Surely. Any questions please let me know