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.
Custom Hyprlock input field does not override the default input field
Reported by Chase78712002 · filed Sep 21, 2025Closed upstream on 2025-10-26 by ryanrhughes. 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
System details
AMD Ryzen 5 2600, NVIDIA GeForce GTX 1070, Omarchy v3.0.1
What's wrong?
Prior to the update, I customized the lock screen's input field in my theme's hyprlock.conf file.
After the new update, I notice the ~/.config/hypr/hyprlock.conf has the default for input field as well.
I assume my config under the theme directory would override the default. But it turns out both input fields are showing in the lock screen.
Deleting the default input-field could solve my issue, but I am curious about the supposed workflow when configuring hyprlock. Are we supposed to modify the hyprlock.conf under the theme directory? or the one in the ~/.config/hypr?
<img width="799" height="442" alt="Image" src="https://github.com/user-attachments/assets/333d0ab5-0330-4721-9678-3e8ce1cf6bd0">
View raw text
### System details AMD Ryzen 5 2600, NVIDIA GeForce GTX 1070, Omarchy v3.0.1 ### What's wrong? Prior to the update, I customized the lock screen's input field in my theme's `hyprlock.conf` file. After the new update, I notice the `~/.config/hypr/hyprlock.conf` has the default for input field as well. I assume my config under the theme directory would override the default. But it turns out both input fields are showing in the lock screen. Deleting the default input-field could solve my issue, but I am curious about the supposed workflow when configuring hyprlock. Are we supposed to modify the `hyprlock.conf` under the theme directory? or the one in the `~/.config/hypr`? <img width="799" height="442" alt="Image" src="https://github.com/user-attachments/assets/333d0ab5-0330-4721-9678-3e8ce1cf6bd0">
- 333d0ab5-0330-4721-9678-3e8ce1cf6bd0
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.