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.
fix(waybar): clock module displays UTC instead of local time
Reported by LeoLakers · filed Apr 21, 2026Closed upstream on 2026-07-18 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
System details
Intel(R) Core(TM) i5-2310 (4) @ 3.20 GHz - Omarchy 3.5.1
What's wrong?
Description
The clock module in the top bar (Waybar) defaults to UTC time even when the system's local timezone is correctly set via timedatectl. This causes a discrepancy between the terminal time and the displayed time in the bar.
Current Behavior
In my case (Argentina, GMT-3), while the system correctly identifies the local time, the bar shows UTC time (3 hours ahead).
Steps to Reproduce
Install Omarchy with a non-UTC timezone.
Check the time in the terminal using timedatectl status.
Observe that the top bar displays Universal Time (UTC) instead of Local Time.
Proposed Solution
Modify the clock module configuration in the Waybar config file (typically ~/.config/waybar/config.jsonc) to include the timezone parameter or ensure it points to the system's local setting.
Current config:
JSON
"clock": {
"format": "{:L%A %H:%M}",
...
}Fixed config:
JSON
"clock": {
"timezone": "America/Argentina/Buenos_Aires", // Leaving it empty or specifying the zone forces local time sync
"format": "{:L%A %H:%M}",
...
}Note: Adding "timezone": "" or the specific path to the zone fixes the rendering issue.
Additional Context
Running timedatectl set-local-rtc 0 is also recommended to clear the RTC warning and ensure the hardware clock follows the standard UTC protocol, preventing further drifts.
Observed Limitation with Built-in Tools
The existing automated method to update the timezone does not resolve this discrepancy. Specifically, the following action:
"Update the TZ based on your current IP location by right-clicking on the clock or via Update > Timezone in the menu."
Successfully updates the system's timezone (as seen in timedatectl), but it fails to update the Waybar display, which remains stuck in UTC. This confirms that the issue lies in the Waybar module configuration rather than the system's global settings.
View raw text
### System details
Intel(R) Core(TM) i5-2310 (4) @ 3.20 GHz - Omarchy 3.5.1
### What's wrong?
Description
The clock module in the top bar (Waybar) defaults to UTC time even when the system's local timezone is correctly set via timedatectl. This causes a discrepancy between the terminal time and the displayed time in the bar.
Current Behavior
In my case (Argentina, GMT-3), while the system correctly identifies the local time, the bar shows UTC time (3 hours ahead).
Steps to Reproduce
Install Omarchy with a non-UTC timezone.
Check the time in the terminal using timedatectl status.
Observe that the top bar displays Universal Time (UTC) instead of Local Time.
Proposed Solution
Modify the clock module configuration in the Waybar config file (typically ~/.config/waybar/config.jsonc) to include the timezone parameter or ensure it points to the system's local setting.
Current config:
```
JSON
"clock": {
"format": "{:L%A %H:%M}",
...
}
```
Fixed config:
JSON
```
"clock": {
"timezone": "America/Argentina/Buenos_Aires", // Leaving it empty or specifying the zone forces local time sync
"format": "{:L%A %H:%M}",
...
}
```
Note: Adding "timezone": "" or the specific path to the zone fixes the rendering issue.
Additional Context
Running timedatectl set-local-rtc 0 is also recommended to clear the RTC warning and ensure the hardware clock follows the standard UTC protocol, preventing further drifts.
Observed Limitation with Built-in Tools
The existing automated method to update the timezone does not resolve this discrepancy. Specifically, the following action:
"Update the TZ based on your current IP location by right-clicking on the clock or via Update > Timezone in the menu."
Successfully updates the system's timezone (as seen in timedatectl), but it fails to update the Waybar display, which remains stuck in UTC. This confirms that the issue lies in the Waybar module configuration rather than the system's global settings.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.