OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
omarchy-core medium common DISPUTE

Web app launchers open the wrong page or fail after a browser update or default-browser change

omarchy-4
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Cause is exact. bin/omarchy-launch-webapp is reproduced character for character, including the whitelist google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*, the *) browser="chromium.desktop" fallback, and the exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}" line, so the empty-command-substitution analysis and the Opera-is-whitelisted-but-ignores---app analysis are both right. bin/omarchy-webapp-install writes EXEC_COMMAND="${CUSTOM_EXEC:-omarchy-launch-webapp $APP_URL}" into Exec=, its documented args really are [name url icon-url-or-name [custom-exec] [mime-types]] (so the 4th-argument override is correct), and it really does refuse a name containing '/' with that exact rationale. Issues #7034 and #8298 exist with titles matching the two failure modes, and omarchy-webapp-remove and omarchy-install-browser exist. The keybinds are right too: default/hypr/bindings/applications.lua has SUPER + SHIFT + A ChatGPT, SUPER + SHIFT + ALT + A Grok, SUPER + SHIFT + X X. But that is exactly the defect: those binds do not go through any .desktop file. default/hypr/helpers.lua resolves { webapp = url } to the literal string "omarchy-launch-webapp " .. shell_quote(url) (or omarchy-launch-or-focus-webapp for sole-instance apps), so editing ~/.local/share/applications/ChatGPT.desktop or reinstalling with a custom exec fixes the launcher icon and leaves Super+Shift+A just as broken. The record leads with the keybinds in its symptom and then offers a fix that cannot address them, so a Firefox/Opera user following it will conclude the fix failed.

The cause above was not rewritten and may still contain the error described. The fix below is the corrected version.
RISK

omarchy-webapp-remove-all deletes every web-app launcher in ~/.local/share/applications, including ones you wrote by hand, and omarchy-remove-preinstalls has been reported to remove user-created web apps too (issue #4830). Copy ~/.local/share/applications somewhere safe first. Never put a / in a web app name: it creates a nested .desktop path that omarchy-webapp-remove cannot delete, leaving an entry stuck in the launcher (issue #7914). Editing a .desktop by hand means an omarchy update that regenerates preinstalled web apps can overwrite it, so keep custom apps under names Omarchy does not ship.

Symptom

The Omarchy web-app launchers stop working while their icons stay in the launcher. Super+Shift+A (ChatGPT), Super+Shift+Alt+A (Grok), Super+Shift+X, and omarchy launch webapp <url> either do nothing, open the browser on its start page instead of the site, or fail outright with:


error: path "--app=https://messenger.com" does not exist!

Typically starts right after installing Firefox/Opera and making it default, after removing Chromium, or after a Chromium-family package rename.

Cause

Every .desktop file written by omarchy-webapp-install has Exec=omarchy-launch-webapp <url>. omarchy-launch-webapp reads xdg-settings get default-web-browser, keeps only chromium-family desktop ids (google-chrome*, brave*, microsoft-edge*, opera*, vivaldi*, helium*) and otherwise falls back to a hardcoded chromium.desktop, then greps the Exec= line out of that desktop file and appends --app=<url>:


exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' \
  {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}"

With Firefox default and Chromium uninstalled, chromium.desktop does not exist, the command substitution yields an empty binary path, and uwsm-app treats --app=... as the executable (issue #7034). With Opera default, it *is* whitelisted so the launch "succeeds", but Opera ignores --app=, so the flag is dropped and you get the start page (issue #8298).

Fix


# 1. What does Omarchy think your default browser is, and does that file exist?
xdg-settings get default-web-browser
ls /usr/share/applications/chromium.desktop ~/.local/share/applications/chromium.desktop 2>/dev/null

# 2. Simplest fix, and the only one that fixes the keybinds and the launcher
#    icons at once: keep a chromium-family browser installed and default.
omarchy-install-browser                 # or: sudo pacman -S --needed chromium
ls /usr/share/applications | grep -iE 'chromium|brave|vivaldi|edge'
xdg-settings set default-web-browser chromium.desktop     # use the id you saw above

To keep Firefox or Opera as your default browser you have to fix **two separate things**: the keybinds and the launcher entries do not share a code path.

**a) The keybinds (Super+Shift+A and friends).** These are Lua, not .desktop files: { webapp = "..." } expands to a direct omarchy-launch-webapp <url> call, so no amount of .desktop editing reaches them. Rebind them in ~/.config/hypr/bindings.lua:


-- ~/.config/hypr/bindings.lua
hl.unbind("SUPER + SHIFT + A")
o.bind("SUPER + SHIFT + A", "ChatGPT", "firefox --new-window https://chatgpt.com")

hl.unbind("SUPER + SHIFT + ALT + A")
o.bind("SUPER + SHIFT + ALT + A", "Grok", "firefox --new-window https://grok.com")

hl.unbind("SUPER + SHIFT + X")
o.bind("SUPER + SHIFT + X", "X", "firefox --new-window https://x.com/")

Or drop the whole preinstalled set in one line and add back only what you want, in ~/.config/hypr/hyprland.lua **before** require("default.hypr.omarchy"):


omarchy_preinstalled_bindings = false

hyprctl reload
hyprctl binds | grep -A3 ChatGPT

**b) The launcher entries.** omarchy-webapp-install takes a custom exec as its 4th argument:


omarchy-webapp-install "ChatGPT" "https://chatgpt.com" \
  "https://chatgpt.com/apple-touch-icon.png" \
  "firefox --new-window https://chatgpt.com"

or edit the desktop entry directly:


# ~/.local/share/applications/ChatGPT.desktop
[Desktop Entry]
Type=Application
Name=ChatGPT
Exec=setsid uwsm-app -- firefox --new-window https://chatgpt.com
Icon=chatgpt
Terminal=false
StartupNotify=true

update-desktop-database ~/.local/share/applications
gtk-update-icon-cache ~/.local/share/icons/hicolor

Rebuild a broken or wrongly-named entry from scratch:


omarchy-webapp-remove "ChatGPT"
omarchy-webapp-install            # interactive; it refuses names containing '/'

Verify

omarchy-launch-webapp https://example.com opens an app-mode window on that URL. gio launch ~/.local/share/applications/ChatGPT.desktop opens ChatGPT, not a start page.

Sources

webapp-launchers-broken-after-browser-change