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.
Hyprland 0.50.0 and newer versions might break if hyprutils-git is installed
Reported by adaryorg · filed Jul 20, 2025Closed upstream on 2025-08-13 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
I know that this is not necessarily an Omarchy issue, but the way I see it, a lot of people might be using Omarchy who are not exactly savvy in troubleshooting Arch linux, or have the knowhow to boot in single user mode and see why their PC is a brick :)
So here is the background. A few days ago I ran a full system update, and Hyprland was updated to 0.50.0-1 (vanilla Arch linux). Imediately after the reboot ,all I got after the Omarchy splash screen was black screen. Hyprland wouldn't start, I couldn't drop into text terminal since the current systemdl user service always restarts (even on failure) and unfortunately I don't keep sshd running at all times on my main PC, so single user mode it was to troubleshoot.
I disabled the omarchy desktop service, enabled GDM, rebooted, logged into gnome, did some troubleshooting and got something pretty from the log:
Hyprland: symbol lookup error: Hyprland: undefined symbol: _ZNK9Hyprutils4Math8Vector2D9transformENS0_10eTransformERKS1_
I didn't have the time to properly debug it, downgraded back to 0.49 Hyprland that was in pacman cache, and today properly debugged the issue.
For reasons totally unknown to me, i had hyprutils-git and hyprsunset-git installed. after removing hyprsunset-git, reinstalling hyprutls and hyprsunset packages, Hyprland 0.50.1 (and 0.50.1) work properly again.
My other solution to bad Hyprland bricking the system is a slight modification to the omarchy-seamless-login.service:
`[Unit]
Description=Omarchy Seamless Auto-Login
Documentation=https://github.com/basecamp/omarchy
[email protected]
After=systemd-user-sessions.service [email protected] plymouth-quit.service systemd-logind.service
PartOf=graphical.target
[Service]
Type=simple
ExecStart=/usr/local/bin/seamless-login uwsm start -- hyprland.desktop
Restart=on-success
RestartSec=2
User=adary
TTYPath=/dev/tty1
TTYReset=yes
TTYVHangup=yes
TTYVTDisallocate=yes
StandardInput=tty
StandardOutput=journal
StandardError=journal+console
PAMName=login
[Install]
WantedBy=graphical.target`
Change Restart=always to Resstart=on-success
this way a failed Hyprland session won't try to restart itself every two seconds, and the user can safely fall back to text terminal and stop the service and enable GDM (no need to go into single user mode)
View raw text
I know that this is not necessarily an Omarchy issue, but the way I see it, a lot of people might be using Omarchy who are not exactly savvy in troubleshooting Arch linux, or have the knowhow to boot in single user mode and see why their PC is a brick :) So here is the background. A few days ago I ran a full system update, and Hyprland was updated to 0.50.0-1 (vanilla Arch linux). Imediately after the reboot ,all I got after the Omarchy splash screen was black screen. Hyprland wouldn't start, I couldn't drop into text terminal since the current systemdl user service always restarts (even on failure) and unfortunately I don't keep sshd running at all times on my main PC, so single user mode it was to troubleshoot. I disabled the omarchy desktop service, enabled GDM, rebooted, logged into gnome, did some troubleshooting and got something pretty from the log: Hyprland: symbol lookup error: Hyprland: undefined symbol: _ZNK9Hyprutils4Math8Vector2D9transformENS0_10eTransformERKS1_ I didn't have the time to properly debug it, downgraded back to 0.49 Hyprland that was in pacman cache, and today properly debugged the issue. For reasons totally unknown to me, i had hyprutils-git and hyprsunset-git installed. after removing hyprsunset-git, reinstalling hyprutls and hyprsunset packages, Hyprland 0.50.1 (and 0.50.1) work properly again. My other solution to bad Hyprland bricking the system is a slight modification to the omarchy-seamless-login.service: `[Unit] Description=Omarchy Seamless Auto-Login Documentation=https://github.com/basecamp/omarchy [email protected] After=systemd-user-sessions.service [email protected] plymouth-quit.service systemd-logind.service PartOf=graphical.target [Service] Type=simple ExecStart=/usr/local/bin/seamless-login uwsm start -- hyprland.desktop Restart=on-success RestartSec=2 User=adary TTYPath=/dev/tty1 TTYReset=yes TTYVHangup=yes TTYVTDisallocate=yes StandardInput=tty StandardOutput=journal StandardError=journal+console PAMName=login [Install] WantedBy=graphical.target` Change Restart=always to Resstart=on-success this way a failed Hyprland session won't try to restart itself every two seconds, and the user can safely fall back to text terminal and stop the service and enable GDM (no need to go into single user mode)
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.
No decision has been recorded yet.