Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-250GitHub issuePublicDecided· Out of scope

Omarchy Quattro Root Cause Analysis: Hyprland missing org.gnome.Mutter.ServiceChannel D-Bus service — multiple GTK3/GNOMEapplication failures

Reported by Pacray · filed Sep 21, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Omarchy Quattro Root Cause Analysis: Hyprland missing org.gnome.Mutter.ServiceChannel D-Bus service — multiple GTK3/GNOMEapplication failuresrevision 1 · captured 2026-09-28 21:23 UTC via poll

System details

Hardware: • CPU: AMD Ryzen 9 7945HX3D with Radeon Graphics (16 cores, 32 threads, up to 5.46 GHz, L1 1 MiB, L2 16 MiB, L3 192 MiB) • GPU: AMD Navi 31 RDNA3 [Radeon RX 7900 XTX] with 24 GB VRAM (rev c8) • RAM: 62 GiB Kingston Fury Impact DDR5 5600 (2x32 GiB SODIMM) (28 GiB buff/cache) • Storage: nvme0n1 SAMSUNG SSD 980 PRO 931.5G, nvme1n1 WD PC SN810 953.9G (NVMe SSDs) • Monitor: DP-1 3840x1080@144Hz ultrawide

What's wrong?

I've identified a systemic integration issue on Omarchy (Arch-based, QuickShell + Hyprland): Hyprland does not provide the org.gnome.Mutter.ServiceChannel D-Bus service that GTK3-based GNOME applications and services expected. This causes multiple failure modes across different applications.

I've documented this in detail in four separate reports (attached as ZIP):

• gjs-console / NautilusPreviewer crashes — Assertion _gtk_style_provider_private_get_settings → SIGSEGV in libgtk-3.so.0,with symbolized backtrace (debuginfod+GDB, full crash chain from D-Bus failure to segfault)

• xdg-open hangs indefinitely — xdg-desktop-portal-hyprland blocks on D-Bus wait for missing Mutter service, never returns

• Godot Asset Library script-load errors during workspace switching — Godot reacts to workspace switch with GTK resourcere-evaluation, exposes broken GTK3 state as script errors; succeeds without workspace switch

• Root cause analysis (overarching document) — unifies the three symptoms under one root cause, includes cross-references,external reports as context (TIC-80 #2971, NixOS #353990, end-4/dots-hyprland #1298, Hyprland #7471, Bottles #2812,openSUSE forums, Fedora/RHEL kickstart #1303), and upstream coordination strategy

Software:

• Distribution: Omarchy Quattro (4.0.0.alpha)
• Kernel: 7.2.5-3-omarchy
• Compositor: Hyprland with QuickShell 0.3.1-1
• GTK3: 3.24.52-1
• gjs: 2:1.88.1-1
• webkit2gtk-4.1: 2.52.6-1
• Godot: 4.7.2.stable.official (Steam, Linux-native, no compatibility layer)
• Session: Wayland/X11 hybrid via QuickShell

omarchy_bug_report_analysis.zip

The root cause is that Hyprland (and likely other non-Mutter compositors) lack the Mutter ServiceChannel that GTK3 expects.Other distributions (e.g., CachyOS with KDE/Wayland) do not exhibit these failures, confirming the environment-specificnature of the issue.

I've attached all four reports as omarchy_bug_report_analysis.zip — they are ready to be submitted upstream (Hyprland,GNOME/GTK3, xdg-desktop-portal-hyprland, Godot) with cross-references.

Any comments, questions, or suggestions are welcome.

View raw text
### System details

Hardware:  • CPU: AMD Ryzen 9 7945HX3D with Radeon Graphics (16 cores, 32 threads, up to 5.46 GHz, L1 1 MiB, L2 16 MiB, L3 192 MiB) • GPU: AMD Navi 31 RDNA3 [Radeon RX 7900 XTX] with 24 GB VRAM (rev c8) • RAM: 62 GiB Kingston Fury Impact DDR5 5600 (2x32 GiB SODIMM) (28 GiB buff/cache) • Storage: nvme0n1 SAMSUNG SSD 980 PRO 931.5G, nvme1n1 WD PC SN810 953.9G (NVMe SSDs) • Monitor: DP-1 3840x1080@144Hz ultrawide

### What's wrong?

I've identified a systemic integration issue on Omarchy (Arch-based, QuickShell + Hyprland): Hyprland does not provide the org.gnome.Mutter.ServiceChannel D-Bus service that GTK3-based GNOME applications and services expected. This causes multiple failure modes across different applications.

I've documented this in detail in four separate reports (attached as ZIP):

• gjs-console / NautilusPreviewer crashes — Assertion _gtk_style_provider_private_get_settings → SIGSEGV in libgtk-3.so.0,with symbolized backtrace (debuginfod+GDB, full crash chain from D-Bus failure to segfault)

• xdg-open hangs indefinitely — xdg-desktop-portal-hyprland blocks on D-Bus wait for missing Mutter service, never returns

• Godot Asset Library script-load errors during workspace switching — Godot reacts to workspace switch with GTK resourcere-evaluation, exposes broken GTK3 state as script errors; succeeds without workspace switch

• Root cause analysis (overarching document) — unifies the three symptoms under one root cause, includes cross-references,external reports as context (TIC-80 #2971, NixOS #353990, end-4/dots-hyprland #1298, Hyprland #7471, Bottles #2812,openSUSE forums, Fedora/RHEL kickstart #1303), and upstream coordination strategy

Software:

• Distribution: Omarchy Quattro (4.0.0.alpha)
• Kernel: 7.2.5-3-omarchy
• Compositor: Hyprland with QuickShell 0.3.1-1
• GTK3: 3.24.52-1
• gjs: 2:1.88.1-1
• webkit2gtk-4.1: 2.52.6-1
• Godot: 4.7.2.stable.official (Steam, Linux-native, no compatibility layer)
• Session: Wayland/X11 hybrid via QuickShell

[omarchy_bug_report_analysis.zip](https://github.com/user-attachments/files/32426513/omarchy_bug_report_analysis.zip)

The root cause is that Hyprland (and likely other non-Mutter compositors) lack the Mutter ServiceChannel that GTK3 expects.Other distributions (e.g., CachyOS with KDE/Wayland) do not exhibit these failures, confirming the environment-specificnature of the issue.

I've attached all four reports as omarchy_bug_report_analysis.zip — they are ready to be submitted upstream (Hyprland,GNOME/GTK3, xdg-desktop-portal-hyprland, Godot) with cross-references.

Any comments, questions, or suggestions are welcome.
  • omarchy_bug_report_analysis.zip

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 16:52 UTC