### System details

- Omarchy 4.0.0-1
- Hyprland 0.56.2-1
- quickshell-git 0.3.0.r20.g28771c7-2
- Linux 7.1.8-arch1-3
- Mesa 1:26.1.8-1
- Intel NUC10i7FNH, Intel Core i7-10710U
- Intel Comet Lake UHD Graphics `[8086:9bca]`, i915
- Intel JHL7540 Titan Ridge Thunderbolt / USB-C controller
- Single LG HDR 4K display on DP-2 over USB-C: [email protected], scale 1.5

### What's wrong?

Pressing the physical `Super+Space` shortcut can make the only display go
completely black. Initially, typing while the screen was black could also make
the monitor enter power-save mode. After disabling hardware cursors the monitor
stays powered, but the black screen is still reproducible.

The important distinction is that running the same menu operation from a
terminal (`omarchy menu toggle`, also tested with `omarchy menu summon root`)
works normally: the centered Omarchy menu appears over the dimmed desktop.
The failure is reproducible through the physical keybinding path.

No third-party launcher was installed during testing.

#### Steps to reproduce

1. Connect the LG 4K display to the Intel NUC through USB-C/DP Alt Mode.
2. Start the normal Omarchy/Hyprland session with the stock Omarchy Shell menu.
3. Physically press `Super+Space`.
4. The display intermittently/repeatedly becomes completely black, while the
   session itself remains running.

Expected: the Omarchy menu opens and the display remains active and visible.

#### What I tested

- Direct `omarchy menu toggle` / `omarchy menu summon root`: **works**.
- `render.non_shader_cm = 0`: **does not fix the black screen**.
- `cursor.no_hardware_cursors = 1`: **prevents the monitor from entering
  power-save, but the screen still goes black**.
- Rebound `Super+Space` to run on key release after a 200 ms delay: **does not
  fix the black screen**.
- `hyprctl reload` returned `ok`; `hyprctl configerrors` was empty; the options
  and release binding were confirmed active through `hyprctl`.
- No system suspend or `PrepareForSleep` event was logged in the reproduction
  window.

This looks like an interaction between the Omarchy Quickshell full-screen
layer-shell menu, Hyprland/Aquamarine, Intel i915, and the USB-C display path.
I am reporting it here first because the stock Omarchy shortcut/menu is the
user-visible trigger; please advise if the evidence points to Hyprland,
Aquamarine, Quickshell, or the kernel instead.

<details>
<summary>Privacy-filtered omarchy-debug and relevant logs</summary>

The full `omarchy-debug` output contained unrelated host/network details, so
this includes the relevant system and log sections only.

```text
Omarchy: 4.0.0-1
Hyprland: 0.56.2-1
Quickshell: quickshell-git 0.3.0.r20.g28771c7-2
Kernel: 7.1.8-arch1-3
Mesa: 1:26.1.8-1
Machine: Intel NUC10i7FNH / NUC10i7FNB
CPU: Intel Core i7-10710U (Comet Lake)
GPU: Intel Comet Lake UHD Graphics [8086:9bca], driver i915
Thunderbolt: Intel JHL7540 Titan Ridge
Display: LG HDR 4K on DP-2 over USB-C, [email protected], scale 1.5

Live monitor state after recovery:
  dpmsStatus: 1
  directScanoutTo: 0
  currentFormat: XRGB8888
  colorManagementPreset: srgb
  hardwareCursorsInUse: false

Hyprland/Aquamarine (repeated in the same session):
  ERR from aquamarine ]: drm: Cannot commit when a page-flip is awaiting
  ERR from aquamarine ]: drm: Cannot commit when a page-flip is awaiting

One output recovery sequence:
  DEBUG from aquamarine ]: drm: Modesetting DP-2 with [email protected]
  ERR from aquamarine ]: drm: Cannot commit when a page-flip is awaiting
  ERR from aquamarine ]: drm: Cannot commit when a page-flip is awaiting

Quickshell/Omarchy Shell during output-loss events in the same boot:
  2026-08-25T13:43:48+08:00 WARN quickshell.hyprland.ipc:
    Got removal for monitor "FALLBACK" which was not previously tracked.
  2026-08-25T13:43:48+08:00 INFO qt.qpa.wayland:
    There are no outputs - creating placeholder screen
  2026-08-25T13:43:48+08:00 WARN:
    Layershell screen does not correspond to a real screen. Letting the compositor pick.

  2026-08-25T13:56:53+08:00 INFO qt.qpa.wayland:
    There are no outputs - creating placeholder screen
  2026-08-25T13:56:58+08:00 WARN quickshell.hyprland.ipc:
    Got removal for monitor "FALLBACK" which was not previously tracked.

  2026-08-25T14:15:02+08:00 INFO qt.qpa.wayland:
    There are no outputs - creating placeholder screen
  2026-08-25T14:15:02+08:00 WARN quickshell.hyprland.ipc:
    Got removal for monitor "FALLBACK" which was not previously tracked.

Kernel, Thunderbolt USB controller (representative repetitions):
  2026-08-25T13:43:50+08:00 xhci_hcd 0000:39:00.0:
    xHC error in resume, USBSTS 0x401, Reinit
  2026-08-25T13:43:50+08:00 usb usb3: root hub lost power or was reset
  2026-08-25T13:43:50+08:00 usb usb4: root hub lost power or was reset

  2026-08-25T14:01:04+08:00 xhci_hcd 0000:39:00.0:
    xHC error in resume, USBSTS 0x401, Reinit
  2026-08-25T14:01:04+08:00 usb usb3: root hub lost power or was reset
  2026-08-25T14:01:04+08:00 usb usb4: root hub lost power or was reset

  2026-08-25T14:15:04+08:00 xhci_hcd 0000:39:00.0:
    xHC error in resume, USBSTS 0x401, Reinit
  2026-08-25T14:15:04+08:00 usb usb3: root hub lost power or was reset
  2026-08-25T14:15:04+08:00 usb usb4: root hub lost power or was reset
```

These log events occurred in the same boot/testing period. There are no
per-keystroke markers in the logs, so they are reported as correlated evidence,
not proof that every line was exclusively caused by `Super+Space`.

</details>