Closed general

Setup stopped at Ensure workspace runtime

John Lauer · 6d ago ·closed by John Lauer

Filed from Hydrogen Desktop 1.0.636 on winvm (setup card).

Device: Microsoft Corporation Virtual Machine (AMD64, 32 GB RAM, AMD EPYC 9V64 32-Core Processor). Microsoft Windows 11 Pro 24H2 build 26100. WSL: WSL version: 3.0.3.0.

Attachments: hydrogen-desktop-tail.log (last 300 KB of the app log), diagnostics.json (health, setup state, WSL status, the Doctor checks, build info, device), setup-steps-wsl.json (setup step log), setup-timing-wsl.json (setup step log).

Last 40 log lines:

15:30:56.374 [ad-supervisor] brand fonts: 0 installed now, 3 present, 0 failed
15:30:59.110 [wsl] masked kmod-static-nodes + systemd-binfmt; systemd is running
15:30:59.244 [cmd] $ wsl -d Adom-Workspace -u root -- systemctl daemon-reload && systemctl enable --now code-server.service
15:30:59.918 [wsl] systemd code-server.service active=true
15:30:59.918 [wsl] code-server managed by systemd, no HD-held child
15:31:00.060 [heartbeat] alive 10s
15:31:01.932 [cmd] $ wsl -d Adom-Workspace -u root -- <write /home/adom/.adom/api-key + /run/adom/api-key + /etc/tmpfiles.d/adom-api-key.conf>
15:31:02.064 [wsl] api-key persistence ensured (tmpfiles.d boot re-materialization + persistent copy + fresh token written to both layers)
15:31:02.420 [control] workspace exec (30s): python3 -c "import base64;exec(base64.b64decode('CmltcG9ydCBqc29uLCBvcywgZ2xvYgpyb290ID0gb
15:31:02.422 [proxy] Container discovery (local): /containers/local owner=john repo=container
15:31:02.900 [proxy] cloud mirror GET /api/workspaces/editor/john/container/shared -> 200
15:31:03.216 [wsl] masked kmod-static-nodes + systemd-binfmt; systemd is running
15:31:03.349 [cmd] $ wsl -d Adom-Workspace -u root -- systemctl daemon-reload && systemctl enable --now code-server.service
15:31:04.324 [wsl] systemd code-server.service active=true
15:31:04.325 [wsl] code-server managed by systemd, no HD-held child
15:31:08.647 [run_all_wsl] DONE 'ensure-workspace' in 13.2s (failed)
15:31:08.663 [run_all_wsl] HALT: step 'ensure-workspace' failed after 1 attempts; not advancing to later steps
15:31:08.666 [run_all_wsl] persisted setup-state.txt = in-progress (GET /setup/state matches the cascade)
15:31:08.666 [run_all_wsl] TIMING total 13.2s over 1 steps; slowest: ensure-workspace 13.2s
15:31:08.667 [cascade] setup released the editor (opportunistic healers re-armed)
15:31:08.671 [run_all_wsl] install-approval window closed, normal prompting restored
15:31:08.671 [taskbar] cascade ended with a failure, leaving the red progress bar up
15:31:08.708 [telemetry] setup_step ensure-workspace fail: HTTP 200
15:31:08.745 [telemetry] error_screen ensure-workspace : HTTP 200
15:31:08.788 [first-run] backdrop: glow denser (a message is on the card)
15:31:09.568 [updater] this login follows the insiders manifest
15:31:10.061 [heartbeat] alive 20s
15:31:10.066 [window-state] snapshot saved: 51,31 1946x1170 max=false
15:31:10.080 Update check: on latest (1.0.636 == 1.0.636)
15:31:10.114 [first-run] intro dismissed by the user
15:31:10.175 [telemetry] error_screen ensure-workspace : HTTP 200
15:31:10.216 [updater] fleet ping HTTP 200 (user 'john')
15:31:10.446 [first-run] intro dismissed, main window shown
15:31:10.457 [first-run] native glow backdrop closed
15:31:11.327 [frame-nav] ALL: about:blank
15:31:11.391 [frame-nav] ALL: http://localhost:7380/?folder=/home/adom/project
15:31:13.644 [app] WebView2 processes at above-normal priority: 9 (pass at +20s, adom/hydrogen#75)
15:31:20.061 [heartbeat] alive 30s
15:31:21.131 [ai-accounts] first-landing check, attempt 0
15:31:21.135 [ai-accounts] setup-state {"agents":[],"at":1792160019,"done":false,"ok":true,"presented":true,"skipped":false}

1 Reply

John Lauer · 6d ago

Filed by the setup-panel-report test scenario (docs/PROMOTION-GATE.md); closing.

Log in to reply.