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.
Possibel fix for: HyperLock skipped on boot
Reported by apurbapokharel · filed Aug 27, 2025Closed upstream on 2025-08-27 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
Hello,
When I first boot my pc the lock screen is skipped and it logs in without asking for my password. But after that if the system is idle for long enough it will start the screensaver and then lock.
I noticed that in ~/.local/share/omarchy/default/hypr/autostart.conf had the following
exec-once = uwsm app -- hypridle
exec-once = uwsm app -- mako
exec-once = uwsm app -- waybar
exec-once = uwsm app -- fcitx5
exec-once = uwsm app -- swaybg -i ~/.config/omarchy/current/background -m fill
exec-once = uwsm app -- swayosd-server
exec-once = /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
exec-once = wl-clip-persist --clipboard regular --all-mime-type-regex '^(?!x-kde-passwordManagerHint).+'
exec-once = omarchy-cmd-first-runThere is no call to the script located in ~/.local/share/omarchy/bin/omarchy-lock-screen, which executes this
pidof hyprlock || hyprlock &as per this line the system will start up an instance of hyprlock if not present (which is never executed for me so no lock screen at boot). But it does start hypridle which does it's job and locks after idle time is exceeded.
So, I called that script at boot and that solved my problem
So, the fix is in
~/.config/hypr/autostart.conf add
exec-once = omarchy-lock-screenLet me know if there is anything. I'm not sure if this is the proper way to fix this, but it works for me. It might be useful for someone else who encounters this problem.
View raw text
Hello, When I first boot my pc the lock screen is skipped and it logs in without asking for my password. But after that if the system is idle for long enough it will start the screensaver and then lock. I noticed that in ~/.local/share/omarchy/default/hypr/autostart.conf had the following ``` exec-once = uwsm app -- hypridle exec-once = uwsm app -- mako exec-once = uwsm app -- waybar exec-once = uwsm app -- fcitx5 exec-once = uwsm app -- swaybg -i ~/.config/omarchy/current/background -m fill exec-once = uwsm app -- swayosd-server exec-once = /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1 exec-once = wl-clip-persist --clipboard regular --all-mime-type-regex '^(?!x-kde-passwordManagerHint).+' exec-once = omarchy-cmd-first-run ``` There is no call to the script located in ~/.local/share/omarchy/bin/omarchy-lock-screen, which executes this ``` pidof hyprlock || hyprlock & ``` as per this line the system will start up an instance of hyprlock if not present (which is never executed for me so no lock screen at boot). But it does start hypridle which does it's job and locks after idle time is exceeded. So, I called that script at boot and that solved my problem So, the fix is in ~/.config/hypr/autostart.conf add ``` exec-once = omarchy-lock-screen ``` Let me know if there is anything. I'm not sure if this is the proper way to fix this, but it works for me. It might be useful for someone else who encounters this problem.
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.