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.
hyprsunset restart after sunset drops night light until the next evening
Reported by roehrbacher · filed Sep 17, 2026 · 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
What happened
After hyprsunset restarts at night, the screen goes back to a neutral (~6000K) look. Warmth (4000K) only comes back at the next sunset, not immediately.
hyprsunset profiles fire at their clock time going forward. They do not apply the last elapsed profile on start. Default on start is ~6000K (hyprsunset --help: --temperature default 6000). That reads as “night light off.”
omarchy-toggle-nightlight already retries hyprctl hyprsunset temperature after a fresh start for this reason. A restart in the middle of the night still leaves the display cold until sunset.
Reproduced on Omarchy 4.0.4-1 (Vienna, after 00:10). Manual Super+Ctrl+N brings 4000K back.
Expected
If it is already after sunset / before sunrise, a hyprsunset restart should stay at 4000K (same as Super+Ctrl+N), not snap to identity/default.
Suggested fix
After writing config and (re)starting hyprsunset, if local time is after sunset or before sunrise, immediately:
hyprctl hyprsunset temperature 4000Retry a few times until it sticks (same loop as omarchy-toggle-nightlight), then omarchy-shell -q nightlight refresh.
Do not wait for the next profile { time = sunset }.
Steps
- Night light on after sunset (4000K).
- Restart hyprsunset (
pkill hyprsunsetthen start it again, or any path that reloads it). - Screen goes neutral until the next sunset unless you toggle.
System
- Omarchy 4.0.4-1
- Hyprland + hyprsunset
- Night light 4000K / identity ~6000K
Filed by grok-4.6 via Hermes Agent.
View raw text
## What happened
After hyprsunset restarts at night, the screen goes back to a neutral (~6000K) look. Warmth (4000K) only comes back at the **next sunset**, not immediately.
hyprsunset profiles fire at their clock time going forward. They do not apply the last elapsed profile on start. Default on start is ~6000K (`hyprsunset --help`: `--temperature` default 6000). That reads as “night light off.”
`omarchy-toggle-nightlight` already retries `hyprctl hyprsunset temperature` after a fresh start for this reason. A restart in the middle of the night still leaves the display cold until sunset.
Reproduced on Omarchy 4.0.4-1 (Vienna, after 00:10). Manual Super+Ctrl+N brings 4000K back.
## Expected
If it is already after sunset / before sunrise, a hyprsunset restart should stay at 4000K (same as Super+Ctrl+N), not snap to identity/default.
## Suggested fix
After writing config and (re)starting hyprsunset, if local time is after sunset or before sunrise, immediately:
```bash
hyprctl hyprsunset temperature 4000
```
Retry a few times until it sticks (same loop as `omarchy-toggle-nightlight`), then `omarchy-shell -q nightlight refresh`.
Do not wait for the next `profile { time = sunset }`.
## Steps
1. Night light on after sunset (4000K).
2. Restart hyprsunset (`pkill hyprsunset` then start it again, or any path that reloads it).
3. Screen goes neutral until the next sunset unless you toggle.
## System
- Omarchy 4.0.4-1
- Hyprland + hyprsunset
- Night light 4000K / identity ~6000K
Filed by grok-4.6 via Hermes Agent.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 15:03 UTC