Try Omarchy 1.0.1: Superwhisper settings cannot save because the user CLI launcher is missing

Problem

Changing settings in the preinstalled Superwhisper produced:

No such file or directory (os error 2)

Reading settings worked. Tracing the settings process identified the failing operation:

execve("/home/kdk/.local/bin/superwhisper",
       ["/home/kdk/.local/bin/superwhisper", "general", "set", "language", "\"ru\""], ...) = -1 ENOENT

The same missing executable caused models select offline and models prepare to fail. /usr/bin/superwhisper existed, but ~/.local/bin/superwhisper did not.

Expected: changes made in the preinstalled application's settings can be saved.

Release and environment

• Try Omarchy 1.0.1, ARM64
• Factory built: 2026-10-17T13:26:05Z
• Factory SHA-256: fc200fc7731af454ba1e6cf997ddef6a1c75b0937331fac61435025953452fc0
• superwhisper-bin 1.0.2-1, included in the factory manifest
• Omarchy at runtime diagnosis: 4.0.0.r7038.gbf9ee5c-1

Observed in the installed guest; a separate clean-factory reproduction has not been performed.

Confirmed setup contract

The installed /usr/share/superwhisper/setup-user explicitly creates:

~/.local/bin/superwhisper -> /usr/bin/superwhisper
~/.local/share/superwhisper/app/current -> /opt/superwhisper

Both links were absent. The installed omarchy-install-dictation-superwhisper calls this setup script after installing the package. Package integrity verification (pacman -Qkk superwhisper-bin) reported 190 files and zero altered files.

These observations identify missing per-user setup artifacts. They do not establish whether setup was skipped or failed.

Verified workaround

ln -s /usr/bin/superwhisper ~/.local/bin/superwhisper

After creating the launcher link, saving through that CLI path succeeded and settings changes in the GUI worked, as confirmed by the user.

Suggested investigation

Check that the factory-preinstalled Superwhisper receives its required per-user initialization for the desktop user, including the launcher used by settings.