Repository navigation
Start menu doesn't appear after shutdown — can't access Resources → Configure to change RAM #183
Description
Try Omarchy version: latest DMG
macOS: Apple Silicon, 16 GB RAM
Omarchy version inside VM: 4.0.2-1
Problem:
When I shut down Omarchy from inside (Super + Alt + Space → System → Shutdown),
the Try Omarchy app closes completely instead of returning to the start menu.
When I reopen Try Omarchy from Applications it boots directly into Omarchy
without showing the start menu, so I have no way to access Resources → Configure
to increase RAM allocation.
What I tried:
- OMARCHY_QEMU_MEMORY_MIB=8192 via environment variable — no effect
- Running the binary directly with the env var — no effect
- defaults write dev.tryomarchy.native memoryMiB -integer 8192 — no effect
- Checked ~/Library/Application Support/Try Omarchy/ — no config file found
Expected behavior:
After shutdown, Try Omarchy should return to the start menu so I can
access Resources → Configure before the next launch.
Mac has 16 GB RAM so the 8 GiB allocation should be available.
Activity
resolvicomai commentedon Sep 16, 2026
I traced the host launcher at
58cbac574f9b6ab7454cee9771c752f5e48bce8e.applicationDidFinishLaunchingcallsshowStartMenu()unconditionally; the initial VM start is wired to the menu Launch callback. This is source inspection, not a reproduction of your installed app's behavior.The reported
4.0.2-1identifies the guest Omarchy version, so it does not identify which host launcher is running. Could you share the Try Omarchy host app version from its About menu, and how you reopen it after shutdown (Applications, Dock, Spotlight, or a shell command)? That would help distinguish an installed-bundle/entry-point problem from a launcher regression without resetting your VM or changing its disk.AI disclosure: this source triage was prepared by an AI coding agent under
resolvicomai's authorization.berin41289 commentedon Sep 17, 2026
I am opening tryomarchy from Spotlight
themartiano commentedon Sep 22, 2026
Weird behavior, but I couldn't reproduce. It should always open the launcher on open.
This should be fixed on the next release, likely addressed by changes in #152.
Closing this, but feel free to reopen if the problem persists.