Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4462GitHub issuePublicReceived

Waybar clock shows time 1 hour behind (DST not applied) on Pacific timezone with tzdata 2026b

Reported by Chase78712002 · filed Jun 13, 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.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Waybar clock shows time 1 hour behind (DST not applied) on Pacific timezone with tzdata 2026brevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 3.8.2

What's wrong?

The Waybar clock module displays time 1 hour behind the actual local time
for the Pacific timezone. It shows PST (-0800) instead of PDT (-0700), so
during daylight saving the clock is off by an hour. Every other system tool
(date, timedatectl) shows the correct time, only the Waybar clock is wrong.

System details

  • Omarchy (Waybar v0.15.0)
  • Timezone: America/Vancouver (should be PDT, -0700)
  • tzdata: 2026b

Steps to reproduce

  1. Set timezone to America/Vancouver or Canada/Pacific (timedatectl set-timezone America/Vancouver)
  2. Have tzdata 2026b installed
  3. Look at the Waybar clock, it's 1 hour behind

Things that are NOT the cause (already ruled out)

  • /etc/localtime correctly points to /usr/share/zoneinfo/America/Vancouver
  • date and timedatectl both show correct local time
  • zdump -v America/Vancouver shows the correct 2026 DST transitions
  • No TZ env var set, no leftover timezone field in config.jsonc
  • Reproduces with a bare clock config and with "timezone": "America/Vancouver" set explicitly

Root cause

This is upstream Waybar issue Alexays/Waybar#5006: tzdata 2026b breaks
C++20 std::chrono timezone handling in Waybar (which is compiled with
HAVE_CHRONO_TIMEZONES=1). C applications are unaffected, which is why only
the Waybar clock is wrong.

Workaround

Downgrade tzdata to 2026a from your cache:
sudo pacman -U /var/cache/pacman/pkg/tzdata-2026a-*.pkg.tar.zst

Then restart Waybar. Clock shows the correct time after that.

View raw text
### System details

Omarchy 3.8.2

### What's wrong?

The Waybar clock module displays time 1 hour behind the actual local time
for the Pacific timezone. It shows PST (-0800) instead of PDT (-0700), so
during daylight saving the clock is off by an hour. Every other system tool
(`date`, `timedatectl`) shows the correct time, only the Waybar clock is wrong.

**System details**

- Omarchy (Waybar v0.15.0)
- Timezone: America/Vancouver (should be PDT, -0700)
- tzdata: 2026b

**Steps to reproduce**

1. Set timezone to America/Vancouver or Canada/Pacific (`timedatectl set-timezone America/Vancouver`)
2. Have tzdata 2026b installed
3. Look at the Waybar clock, it's 1 hour behind

**Things that are NOT the cause (already ruled out)**

- `/etc/localtime` correctly points to `/usr/share/zoneinfo/America/Vancouver`
- `date` and `timedatectl` both show correct local time
- `zdump -v America/Vancouver` shows the correct 2026 DST transitions
- No `TZ` env var set, no leftover `timezone` field in config.jsonc
- Reproduces with a bare clock config and with `"timezone": "America/Vancouver"` set explicitly

**Root cause**

This is upstream Waybar issue Alexays/Waybar#5006: tzdata 2026b breaks
C++20 std::chrono timezone handling in Waybar (which is compiled with
HAVE_CHRONO_TIMEZONES=1). C applications are unaffected, which is why only
the Waybar clock is wrong.

**Workaround**

Downgrade tzdata to 2026a from your cache:
`sudo pacman -U /var/cache/pacman/pkg/tzdata-2026a-*.pkg.tar.zst`

Then restart Waybar. Clock shows the correct time after that.

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.