diff --git a/docs/skills/index.json b/docs/skills/index.json index 6641f793a..15d5f2e32 100644 --- a/docs/skills/index.json +++ b/docs/skills/index.json @@ -106,7 +106,7 @@ ], "description": "Local validation loop: build-ghcr, bootc install to-disk, QEMU/noVNC boot, live ISO boot paths, and Secure Boot strategy. Use when validating changes end-to-end or debugging boot, GDM, or live-session failures.", "version": "1.0", - "last_updated": "2026-09-18", + "last_updated": "2026-09-21", "doc_type": "runbook" }, { diff --git a/docs/skills/local-testing.md b/docs/skills/local-testing.md index 616f57046..a374ec3e5 100644 --- a/docs/skills/local-testing.md +++ b/docs/skills/local-testing.md @@ -1,7 +1,7 @@ --- name: local-testing version: "1.0" -last_updated: "2026-09-18" +last_updated: "2026-09-21" id: local-testing one_line_purpose: Build, install, and boot Utah locally in a VM or live ISO. entry_point: docs/skills/local-testing.md @@ -209,6 +209,18 @@ kernel output, and `UTAH_E2E_REQUIRE_SCREENSHOTS=1` to reject missing PNGs. CI retains the tested commit/image digest and proposes evidence updates in a documentation PR only after all flavors pass. See [ci-workflows.md](ci-workflows.md). +Ghostty is the only terminal the harness's fastfetch capture can show, and +this VM never has a GPU (plain stdvga, no `/dev/dri`), so its terminal +autostart entry (`iso/scripts/luks-e2e.sh`) launches it with +`LIBGL_ALWAYS_SOFTWARE=1 MESA_LOADER_DRIVER_OVERRIDE=llvmpipe`. A +`flatpak override --env=GDK_DISABLE=...` looks like the obvious fix but does +not work: Ghostty computes `GDK_DISABLE` from a hardcoded struct and +`setenv(3)`s it with `overwrite=1` right before `gtk_init`, clobbering any +inherited value, and an upstream build on 2026-09-20 dropped `gles-api` from +that struct and broke every flavor's harness run this way (#183). The two +Mesa variables above are never among the ones Ghostty itself sets, so they +are the ones that actually reach the process. + The harness blocks outbound guest networking while retaining loopback-only SSH forwards, so installation cannot silently fall back to an online pull. For digest-pinned builds, the builder exports the original registry blobs diff --git a/iso/scripts/luks-e2e.sh b/iso/scripts/luks-e2e.sh index 3b69fc136..232995979 100755 --- a/iso/scripts/luks-e2e.sh +++ b/iso/scripts/luks-e2e.sh @@ -525,11 +525,28 @@ window-height = ${TERMINAL_ROWS} CFG done mkdir -p ~/.config/autostart + # This VM never has a GPU (VGA_ARGS above is plain stdvga, no virtio-gpu, + # no /dev/dri), so Ghostty's GTK surface has to fall back to software + # rendering. It used to get there via GDK_DISABLE=gles-api,vulkan, which + # steered GDK away from the EGL/GLES path onto a GLX path that Mesa could + # still soften. Ghostty computes GDK_DISABLE itself from a hardcoded + # struct and setenv(3)s it with overwrite=1 right before gtk_init -- + # https://github.com/ghostty-org/ghostty src/apprt/gtk/class/application.zig, + # gtk_ghostty_application scope -- so any value this script or a flatpak + # override sets is clobbered unconditionally; only the fields Ghostty + # itself compiles in ever apply, and an upstream build on 2026-09-20 + # dropped gles-api from that struct, taking the GLX fallback with it + # (\"MESA: error: ZINK: failed to choose pdev\", then \"gtk_ghostty_surface: + # failed to initialize surface\") (#183). LIBGL_ALWAYS_SOFTWARE and + # MESA_LOADER_DRIVER_OVERRIDE are never touched by Ghostty's own setenv + # calls (only LANG, GDK_DEBUG and GDK_DISABLE are), so they survive into + # the sandboxed process and force llvmpipe directly, without depending on + # whichever GDK path Ghostty's own default happens to select. cat > ~/.config/autostart/${TERMINAL_APP}.desktop <