### What happened

Google Chrome `152.0.7977.82-1` (`/opt/google/chrome/chrome`, installed 2026-09-06T16:23:32 from pacman.log) aborts on every normal launch with `SIGABRT`.

`coredumpctl info 253757` (and identically `243848` @16:23:43, plus 8 reproductions during diagnosis):
```
Signal: 6 (ABRT) si_code: SI_TKILL
Timestamp: Sun 2026-09-06 16:38:29 CEST
Command Line: /opt/google/chrome/chrome
Executable: /opt/google/chrome/chrome
Control Group: /user.slice/.../app-Hyprland-gtk\x2dlaunch-22edee39.scope
```

Journal at the same second:
```
chrome[253757]: qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in ""
chrome[253757]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
chrome[253757]: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
systemd-coredump[253863]: Process 253757 (chrome) of user 1000 dumped core.
```

Stack trace of crashing thread (symbolized, main thread 253757):
```
#0 libc.so.6 raise + abort
#3 libQt5Core.so.5 QMessageLogger::fatal
#4 libQt5Gui.so.5 QGuiApplicationPrivate::createPlatformIntegration
#5 libQt5Gui.so.5 QGuiApplicationPrivate::createEventDispatcher
#6 libQt5Core.so.5 QCoreApplicationPrivate::init
#9 libqt5_shim.so +0x4278
#10 libqt5_shim.so CreateQtInterface
#11 chrome +0xfc141b6 ...
#49 ChromeMain
```

Other threads are idle (`epoll_wait`, `pthread_cond_timedwait`, `g_main_context_iteration`), which matches diagnosis guidance to read whole core — no in-flight thumbnail/IPC work.

### What was expected

Chrome should start (or at least fallback to `xcb`).

### Steps to reproduce

1. On Omarchy 4.0.2-1 (Hyprland 0.56.2, Wayland, `QT_QPA_PLATFORM=wayland;xcb` from `/usr/share/omarchy/default/hypr/envs.lua:13`), with `qt5-wayland` **not** installed.
2. `pacman -Q | grep qt5` shows `qt5-base 5.15.19+kde+r96-1`, `qt5-declarative`, `qt5-tools`, `qt5-translations` — but no `qt5-wayland`. `qt6-wayland 6.11.2-1` is installed. `/usr/lib/qt/plugins/platforms/` lacks `libqwayland.so` (only `libqeglfs.so` … `libqxcb.so`).
3. Install or have `google-chrome 152.0.7977.82-1` (`/opt/google/chrome/chrome` + `libqt5_shim.so`).
4. Launch normally: `gtk-launch google-chrome` (or `uwsm app -- google-chrome`, or `systemd-run --user --scope -- gtk-launch google-chrome.desktop`, or directly `/opt/google/chrome/chrome --no-sandbox` in a Wayland session).
5. Observe `qt.qpa.plugin: Could not find "wayland" in ""` and `SIGABRT` in `coredumpctl list`; `coredumpctl list` shows repeatable crashes (`243848`, `253757`, plus 8 reproductions during testing, all identical stacks).

Note: `QT_QPA_PLATFORM=xcb /opt/google/chrome/chrome --no-sandbox` (and `systemd-run --setenv=QT_QPA_PLATFORM=xcb`) **still** aborts with the same Wayland error, and `strings` on the core shows `QT_QPA_PLATFORM=xcb` — proving env override is insufficient. Headless `chrome --headless --no-sandbox --dump-dom about:blank` succeeds because `libqt5_shim.so` not loaded.

### System information

- `omarchy version`: `omarchy 4.0.2-1` (`/usr/share/omarchy/version` `4.0.0.alpha`)
- `Hyprland 0.56.2`, `SDDM`, `kernel 7.1.9-arch1-2`, `Omarchy` distro (from `omarchy debug --no-sudo --print`)
- Full `omarchy debug --no-sudo --print` written to `/tmp/omarchy-debug.log` (also `inxi -Farz` therein). Key env: `QT_QPA_PLATFORM=wayland;xcb`, `QT_QPA_PLATFORMTHEME=gtk3`, `WAYLAND_DISPLAY=wayland-1`, `XDG_SESSION_TYPE=wayland`.

<details><summary>omarchy debug excerpt (inxi)</summary>

```
System: Kernel 7.1.9-arch1-2 arch x86_64 Desktop Hyprland v0.56.2 dm SDDM Distro Omarchy
Machine: HP OMEN by HP Laptop 15-ce0xx
CPU: Intel i5-7300HQ 4x3100
Graphics: Intel HD Graphics 630 + NVIDIA GTX 1050 Mobile (nvidia 580.178.04)
Display: wayland X.org 1.21.1.24 Xwayland 24.1.13 compositor Hyprland v0.56.2
Network: iwlwifi wlp4s0
Repos: pacman 1051 pkgs
Memory: 16GiB used 11.76GiB
```

</details>

<details><summary>Installed Qt packages / plugin dir</summary>

```
pacman -Q | grep qt => qt5-base 5.15.19+kde+r96-1, qt5-declarative, qt5-tools, qt5-translations, qt6-wayland 6.11.2-1 (qt5-wayland missing)
ls /usr/lib/qt/plugins/platforms/: libqeglfs.so libqlinuxfb.so libqminimal.so libqminimalegl.so libqoffscreen.so libqvnc.so libqxcb.so  (no libqwayland.so)
ls /usr/lib/qt6/plugins/platforms/: libqwayland.so present
```

</details>

### Why this implicates Omarchy config

- `envs.lua:13` forces `QT_QPA_PLATFORM=wayland;xcb` globally: `hl.env("QT_QPA_PLATFORM", "wayland;xcb")` (`/usr/share/omarchy/default/hypr/envs.lua:13`).
- `qt5-base` declares `qt5-wayland` as optional `to run Qt applications in a Wayland session`, but `omarchy` package `Depends` (`omarchy-keyring omarchy-settings ... hyprland quickshell uwsm sddm ...`) does not pull `qt5-wayland`.
- History: `migrations/1785351479.sh` comment says `qt5-wayland is explicitly installed, so the -s cascade leaves it` — true on 3.x where `omarchy-base.packages` listed it, but on fresh 4.x (post-fae4a9e0 "Drop the Qt5 stack") it is not installed, so chrome's Qt5 shim (via `libqt5_shim.so -> libQt5Core.so.5/libQt5Gui.so.5` from `qt5-base`) has no Wayland backend. Related issue #10302 describes the same Qt5-stack removal for SDDM greeter (themes `maya`/`maldives` without `QtVersion=6`); this is the Chrome counterpart (Qt5 app requiring Wayland plugin).

Resource exhaustion ruled out: `free -h` `15Gi/4.2Gi avail`, `journalctl -p 3` no `OOM`/`killed process` between `16:30-16:40`.

### What I tried

- Verified no OOM, checked `coredumpctl list` pattern, symbolized core (stale `QT_QPA_PLATFORM=wayland;xcb` via `strings`).
- Forced `QT_QPA_PLATFORM=xcb` via wrapper `~/.local/bin/google-chrome-stable`, desktop override, `systemctl --user set-environment`, `systemd-run --setenv` — all still abort with Wayland error (core `strings` confirms `xcb` yet crash persists).
- Headless mode works, confirming shim only on normal launch.
- Workarounds cleaned up; system left as found (no `QT_QPA_PLATFORM` override left; only proposed proper fix not yet applied due to sudo TTY).

### Fix / expectation

Proper fix keeps Wayland for Qt: `sudo pacman -S --needed qt5-wayland` (provides `/usr/lib/qt/plugins/platforms/libqwayland.so` + `wayland-decoration-client` etc.), then relogin. Verified `qt5-wayland 5.15.19+kde+r55-1` exists in `extra` (1129 KiB). Alternative global fallback `QT_QPA_PLATFORM=xcb` would lose Wayland for all Qt5 apps and still didn't fix Chrome in testing, so not recommended.

### Search before filing

- `gh issue list --state all --limit 200 --json title,body`: no open/closed issue mentions `qt5-wayland`, `QT_QPA_PLATFORM`, or `platform plugin` except #10302 (SDDM greeter Qt5 missing — related but different program/trigger). `chrome`/`wayland`/`crash` searches via `gh issue list --search` returned empty for `omacom/omarchy` (empty result, not error). `gh search issues` API returns 422 for this repo (permission/search scope), so manual scan above.

### Logs

- `coredumpctl info 253757` full trace attached above
- Journal tail attached above
- `/tmp/omarchy-debug.log` available; interactive `omarchy debug` can upload to `logs.omarchy.org` if desired

Filed by muse-spark-1.2-contributor-free via opencode.