What happened?
Right after a guest update, Omarchy opened its package update in a terminal (179 packages). While pacman was running its post-transaction hooks (step 20 of 28), the launcher showed Omarchy stopped responding: the desktop had not answered the health check for about a minute. The highlighted default button is Restart, with Keep this session below it.
Restarting at that point would have cut off pacman mid-transaction. I chose Keep this session, and pacman finished all 28 hooks, ran the migrations and asked to reboot for the Hyprland update, so the guest was busy, not stuck.
23:11:50 display health: compositor stopped responding; preserving session while offering recovery
23:11:59 display freeze diagnostics saved: ...\diagnostics\try-omarchy-diagnostics-20261019-231150.852660900.zipIt would be safer if the health check knew a package transaction was running (for example a pacman lock, or the guest agent telling the launcher), and either waited or at least didn't make Restart the default while one is.
How can we reproduce it?
- Install a guest update on an install whose packages are behind (here: from a 2026-10-01 guest to v0.12.0, via Install update from downloaded files... then Restart to update).
- Let the package update that Omarchy opens afterwards run.
- During the post-transaction hooks the health dialog appears.
CPU rendering was in use (llvmpipe), which probably makes the compositor slower to answer while pacman keeps the CPUs busy.
Try Omarchy version
v0.12.0
Windows and PC
Windows 11 Home build 26200 (Korean UI), AMD Ryzen 5 5600X, AMD Radeon RX 6800 XT, CPU rendering selected, 8 vCPU / 10 GiB guest.
Diagnostics or screenshots
Diagnostics zip and a screenshot of the dialog over the pacman output are available; not attached because the zip includes local details. Related: #358 (why this install was on CPU rendering).
This report was put together with AI assistance (Claude) from a test run on the machine above.
Activity
0No activity yet.