Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
GTK apps (e.g. Nautilus) freeze on close under Hyprland/NVIDIA unless forcing GSK_RENDERER=ngl
Reported by bitclaw · filed Aug 18, 2025 · open at source
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
Summary
Hit an issue where Nautilus froze every time I closed the window. To debug:
- Ran Nautilus from terminal with GDK_BACKEND=wayland to watch logs
- Tailed journalctl --user -f and dmesg -w — no OOM/segfaults, just a hang
- Verified that GDK_BACKEND=x11 closed cleanly → narrowed to Wayland path
- Tried GTK_USE_PORTAL=0 alone and it still froze
- Forced GSK_RENDERER=gl, it closed cleanly, but showed a deprecated warning
- Finally used GSK_RENDERER=ngl, works, closes fine
So it’s GTK4’s Vulkan renderer hanging on teardown (NVIDIA Quadro M1200 here, but likely all NVIDIA).
FYI I also confirmed the calculator hangs as well.
Steps to Reproduce
- Run Nautilus under Wayland:
GDK_BACKEND=wayland nautilus --no-desktop- Close the window
- Observe freeze (no crash, just hang)
Workaround
Run the app with ngl renderer instead of Vulkan:
GDK_BACKEND=wayland GTK_USE_PORTAL=0 GSK_RENDERER=ngl nautilus --no-desktop
Permanent local fixes
a) App-specific (minimal):
Patch the desktop entry so Nautilus always runs with ngl:
# In case it doesn’t already exist
mkdir -p ~/.local/share/applications
cp /usr/share/applications/org.gnome.Nautilus.desktop ~/.local/share/applications/
# Then edit ~/.local/share/applications/org.gnome.Nautilus.desktop
# Change this line:
# Exec=nautilus --new-window %U
# To this:
Exec=env GSK_RENDERER=ngl nautilus --new-window %Ub) Global (affects all GTK4 apps):
Add to Hyprland envs:
# ~/.config/hypr/envs.conf
env = GSK_RENDERER,nglView raw text
**Summary** Hit an issue where Nautilus froze every time I closed the window. To debug: - Ran Nautilus from terminal with GDK_BACKEND=wayland to watch logs - Tailed journalctl --user -f and dmesg -w — no OOM/segfaults, just a hang - Verified that GDK_BACKEND=x11 closed cleanly → narrowed to Wayland path - Tried GTK_USE_PORTAL=0 alone and it still froze - Forced GSK_RENDERER=gl, it closed cleanly, but showed a deprecated warning - Finally used GSK_RENDERER=ngl, works, closes fine So it’s GTK4’s Vulkan renderer hanging on teardown (NVIDIA Quadro M1200 here, but likely all NVIDIA). FYI I also confirmed the calculator hangs as well. **Steps to Reproduce** 1. Run Nautilus under Wayland: ```bash GDK_BACKEND=wayland nautilus --no-desktop ``` 2. Close the window 3. Observe freeze (no crash, just hang) **Workaround** Run the app with ngl renderer instead of Vulkan: `GDK_BACKEND=wayland GTK_USE_PORTAL=0 GSK_RENDERER=ngl nautilus --no-desktop` **Permanent local fixes** a) App-specific (minimal): Patch the desktop entry so Nautilus always runs with ngl: ```bash # In case it doesn’t already exist mkdir -p ~/.local/share/applications cp /usr/share/applications/org.gnome.Nautilus.desktop ~/.local/share/applications/ # Then edit ~/.local/share/applications/org.gnome.Nautilus.desktop # Change this line: # Exec=nautilus --new-window %U # To this: Exec=env GSK_RENDERER=ngl nautilus --new-window %U ``` b) Global (affects all GTK4 apps): Add to Hyprland envs: ```bash # ~/.config/hypr/envs.conf env = GSK_RENDERER,ngl ```
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-08 23:49 UTC