### System details

Omarchy 4.0.3-1 · aarch64 (Try Omarchy guest VM, CPU implementer 0x61) · kernel 7.2.6-1-aarch64-ARCH · virtio-gpu-gl-pci (virgl, no native GPU) · Chrome as default browser

### What's wrong?

`omarchy-launch-browser` decides which private-mode flag a browser takes by running it with `--help` and grepping for `MOZ_LOG`:

```bash
# /usr/share/omarchy/bin/omarchy-launch-browser, line 12
if $browser_exec --help 2>/dev/null | grep -q MOZ_LOG; then
  private_flag="--private-window"
elif [[ $browser_exec =~ edge ]]; then
  private_flag="--inprivate"
else
  private_flag="--incognito"
fi
```

Chrome's `--help` does not print to stdout — it `execlp("man", ...)` to show its manual page. **On an image where `man-db` is not installed, that `execlp` fails with ENOENT and Chrome dies with SIGTRAP.** So every call to `omarchy-launch-browser` produces a Chrome core dump before the browser it was asked to launch even starts.

The `2>/dev/null` hides it, so the symptom looks like unexplained Chrome crashes with nothing pointing at the launcher.

**Steps to reproduce**

1. On an image without `man-db`, set Chrome as the default browser.
2. Run `omarchy-launch-browser https://example.com`, or use any binding that calls it.
3. `coredumpctl list` shows a new Chrome core, signal SIGTRAP.

**Evidence the mechanism is what's claimed**

- `pacman -Q man-db` returned `package 'man-db' was not found`, with no install record in `pacman.log` — despite `man-db` being listed in the base package manifest.
- The mechanism was proven by putting a **stub `man` binary on `PATH`**, after which the probe completed and Chrome stopped crashing.
- 11 Chrome cores accumulated, all SIGTRAP. Installing `man-db` 2.13.1-2 resolved it.

One secondary effect worth noting: a diagnostic session investigating the crashes **re-triggered the probe while investigating**, taking the core count from 7 to 10. The bug amplifies itself when anything automated looks into it.

**Suggested fix**

Detect by executable name instead of probing `--help` — the same function already does this for Edge on the next line:

```bash
if [[ $browser_exec =~ firefox|librewolf|zen|floorp ]]; then
  private_flag="--private-window"
elif [[ $browser_exec =~ edge ]]; then
  private_flag="--inprivate"
else
  private_flag="--incognito"
fi
```

That removes the subprocess entirely, is faster, and cannot crash the browser it is about to launch. If probing is preferred for extensibility, `man-db` should be a hard dependency, and the probe shouldn't run a browser binary whose `--help` may exec a pager.

**Why it's worth fixing even though `man-db` is usually present**

The failure is silent, is attributed to the wrong component, and amplifies under automated investigation. A minimal or container-derived image is exactly where `man-db` goes missing — and exactly where someone is least likely to connect a crashing browser to a private-mode detection heuristic.