Environment
- Ubuntu 24.04.3 LTS (x86_64), headless cloud server
- ZTM v1.0.4-rc4 (generic Linux build)
- Intended role: hub + agent, no GUI
Problem
ZTM v1.0.4-rc4 cannot be initialized or run in true headless mode, even when using --no-ui.
Observed behavior
-
Running ztm init --no-ui fails with:
Failed to initialize GTK backend
-
Installing libwebkit2gtk-4.1.so.0 resolves the missing library error but does not fix GTK initialization.
-
Running under Xvfb (xvfb-run -a ztm init --no-ui) avoids the GTK panic but the process hangs, repeatedly attempting to connect to http://127.0.0.1:7777, with no successful initialization.
-
The binary still links against GTK / WebKit via Tauri, even in --no-ui mode.
Expected behavior
A fully functional headless / CLI-only mode where:
- No GTK, WebKit, or display server is required
ztm init --no-ui works on a server without X11 / Wayland
- Suitable for hub deployments on cloud and minimal Linux hosts
Impact
- v1.0.4-rc4 is currently not usable on headless servers
- Users must either install a full GUI stack or remain on rc3 (which lacks tunnel deletion and poses security concerns)
Request
- Provide a true headless build (no GTK/Tauri dependency), or
- Ensure
--no-ui fully bypasses GUI initialization paths
Environment
Problem
ZTM v1.0.4-rc4 cannot be initialized or run in true headless mode, even when using
--no-ui.Observed behavior
Running
ztm init --no-uifails with:Installing
libwebkit2gtk-4.1.so.0resolves the missing library error but does not fix GTK initialization.Running under
Xvfb(xvfb-run -a ztm init --no-ui) avoids the GTK panic but the process hangs, repeatedly attempting to connect tohttp://127.0.0.1:7777, with no successful initialization.The binary still links against GTK / WebKit via Tauri, even in
--no-uimode.Expected behavior
A fully functional headless / CLI-only mode where:
ztm init --no-uiworks on a server without X11 / WaylandImpact
Request
--no-uifully bypasses GUI initialization paths