Repository navigation
Create the Windows launcher entry only once the VM is running - #12907
Chessing234 wants to merge 1 commit into
Conversation
|
Verified by source inspection: No actionable defect found in the launcher-ordering change at The menu uses that file to disable Install > Windows and expose Remove > Windows. The source-level ordering is: The desktop-entry contents and removal path are unchanged. Successful Compose startup does not establish that Windows has finished booting. Review informationTest scope: Source and menu-predicate inspection, supplemented by isolated installer checks with synthetic prompts and privileged-operation results. No real KVM/Docker startup, package installation, authentication, interactive cancellation, or live menu was exercised. The conclusion concerns marker creation and control-flow ordering, not end-to-end VM readiness. Community review: Independent automated community review, unaffiliated with the Omarchy team, intended to help prepare PRs for their review. Automated AI review: Astra Medium initial inspection, independent Opus 5.5 High and GPT 6 Sol Xhigh technical reviews, followed by Astra synthesis against source and targeted evidence. |
|
folding into #12264 — same launcher-after-start fix lives there with the setgid harden. |
Summary
install_windowsno longer writeswindows-vm.desktopbefore the gum prompts / final confirm. Cancelling left Launch/Remove in the menu with no VM.create_launcher_entryonly afterdocker-composereports the VM started.Test plan
bash test/shell.d/windows-vm-launcher-test.sh/dev/kvm: start Install > Windows, answer No at "Proceed with this configuration?", confirm Install > Windows is still offeredMade with Cursor