ROG Control Center from the current Omarchy stable mirror aborts immediately at startup. The exact Arch packaging bug was fixed in 6.4.0-3 on September 8, but the stable mirror still serves 6.4.0-2 as of September 29, 2026. Installing the signed Arch 6.4.0-3 GUI package fixes the crash on this machine.

### Reproduction

1. Use Omarchy stable with `extra/rog-control-center 6.4.0-2` and `asusctl 6.4.0-2`.
2. Launch ROG Control Center from the application launcher (`org.opengamingcollective.rog-control-center.desktop`).
3. The application aborts before opening a window; systemd-coredump records SIGABRT.

Expected: the control window opens.

### Evidence and cause

Four launch-time SIGABRT crashes were recorded on September 29 at 22:02, 22:03, 22:15, and 22:17 EDT, including two before that evening's package updates. The latest core contains:

```text
thread 'main' (611086) panicked at /build/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/console-subscriber-0.5.0/src/lib.rs:266:9:
task tracing requires Tokio to be built with RUSTFLAGS="--cfg tokio_unstable"!
```

The installed executable matched its package SHA256. The crashing main-thread stack ends in libc `abort()`; worker threads mostly wait. There were no OOM events. Debug-symbol retrieval failed, so application frames were not symbolized; the exact panic was recovered directly from the core. No core or process environment is attached.

Arch fixed this by removing `--all-features`, which had enabled `tokio-debug`, in [commit 89a707b5355f93d1459faf7a50c4347919240918](https://gitlab.archlinux.org/archlinux/packaging/packages/asusctl/-/commit/89a707b5355f93d1459faf7a50c4347919240918).

### Why this is reported to Omarchy

`/etc/pacman.d/mirrorlist` points to `https://stable-mirror.omarchy.org/$repo/os/$arch`. I downloaded the live stable `extra.db` on September 29 and confirmed it still contains `rog-control-center-6.4.0-2`. The configured order is core, extra, multilib, omarchy; `pacman -Si` also lists Omarchy's own 6.4.0-1 package. A normal update therefore did not provide Arch's corrected build.

Please make a corrected ROG Control Center build available through the supported stable update path. This is a request to distribute the existing fix; the underlying Rust assertion is already fixed in Arch packaging.

### Verified local fix

Installed only the official signed `rog-control-center-6.4.0-3-x86_64.pkg.tar.zst` from the Arch Linux Archive. Its signature was verified with the installed Arch keyring. Its build used the same glibc, libgcc, fontconfig, and systemd-libs versions installed here, and all package dependencies were satisfied. `asusctl` remains 6.4.0-2, satisfying the GUI dependency `asusctl=6.4.0`.

After installation, ROG Control Center remained running and Hyprland reported a mapped window with title `ROG Control`. No new core dump was recorded, and `asusd.service` remained active. ASUS daemon configuration files were unchanged.

### System

- Omarchy 4.0.4-1, stable channel, x86_64
- ASUS ROG Zephyrus G14 GA402XI
- AMD Ryzen 9 7940HS, AMD integrated graphics, NVIDIA RTX 4070 Laptop GPU
- Running kernel: 6.18.7-arch1-1-g14
- Hyprland 0.56.2-2
- glibc 2.44+r24+g16be1518495f-1
- libgcc 16.2.1+r23+gd564253eb6c8-1
- systemd-libs 261.2-1
- fontconfig 2:2.18.3-2

The skill-requested `omarchy debug --no-sudo --print` command is unavailable in this installed Omarchy version, so targeted diagnostics are provided above.

I searched open and closed Omarchy issues and PRs for `rog-control-center`, `asusctl`, and `tokio_unstable`. Issue #10603 concerns a different 6.3.8 exit-time SIGSEGV; PR #12341 discusses repository priority and was closed without merging. Neither describes this startup assertion.

Filed by GPT-6 via Codex.