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.
Nightlight bar indicator doesn't reflect hyprsunset's scheduled temperature changes
Reported by danilosekulovikj · filed Aug 25, 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
The bar's nightlight indicator (omarchy.nightlight) doesn't update when hyprsunset applies its own time-based profile schedule (e.g. time = 19:00 in ~/.config/hypr/hyprsunset.conf). The icon only reflects reality right after a manual click on the widget, or immediately after a fresh shell start.
Expected
The indicator should reflect hyprsunset's live temperature at all times, including scheduled transitions hyprsunset applies on its own.
Root cause (from /usr/share/omarchy/shell/plugins/services/nightlight/Service.qml)refresh() — which runs hyprctl hyprsunset temperature and updates the cached state — is only called from Component.onCompleted and after a manual setNightlight()/toggle/IPC call. There's no Timer or subscription that re-polls hyprsunset periodically, so a schedule-driven change made entirely inside the hyprsunset daemon is invisible to the shell until something explicitly calls refresh().
Steps to reproduce
1. Set a scheduled profile in hyprsunset.conf, e.g.:
profile {
time = 19:00
temperature = 4000
}- Leave the shell running across 19:00 (or start it after 19:00)
- Compare
hyprctl hyprsunset temperatureagainst the bar icon /omarchy-shell nightlight status
Observed
$ hyprctl hyprsunset temperature
4000
$ omarchy-shell nightlight status
{"enabled":false,"temperature":null}System: Omarchy 4.0.1-1, Hyprland 0.56.2
Suggested fix: add a polling Timer inside Service.qml to periodically call refresh() so the indicator stays in sync with hyprsunset's own schedule.
View raw text
**What happened**
The bar's nightlight indicator (`omarchy.nightlight`) doesn't update when hyprsunset applies its own time-based `profile` schedule (e.g. `time = 19:00` in `~/.config/hypr/hyprsunset.conf`). The icon only reflects reality right after a manual click on the widget, or immediately after a fresh shell start.
**Expected**
The indicator should reflect hyprsunset's live temperature at all times, including scheduled transitions hyprsunset applies on its own.
**Root cause** (from `/usr/share/omarchy/shell/plugins/services/nightlight/Service.qml`)
`refresh()` — which runs `hyprctl hyprsunset temperature` and updates the cached state — is only called from `Component.onCompleted` and after a manual `setNightlight()`/toggle/IPC call. There's no `Timer` or subscription that re-polls hyprsunset periodically, so a schedule-driven change made entirely inside the hyprsunset daemon is invisible to the shell until something explicitly calls `refresh()`.
**Steps to reproduce**
1. Set a scheduled profile in `hyprsunset.conf`, e.g.:
```
profile {
time = 19:00
temperature = 4000
}
```
2. Leave the shell running across 19:00 (or start it after 19:00)
3. Compare `hyprctl hyprsunset temperature` against the bar icon / `omarchy-shell nightlight status`
**Observed**
```
$ hyprctl hyprsunset temperature
4000
$ omarchy-shell nightlight status
{"enabled":false,"temperature":null}
```
**System:** Omarchy 4.0.1-1, Hyprland 0.56.2
**Suggested fix:** add a polling `Timer` inside `Service.qml` to periodically call `refresh()` so the indicator stays in sync with hyprsunset's own schedule.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
- Related PRpr/14347· confirmed
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 09:09 UTC