[ISSUE] Waybar clock module broken with latest tzdata

[ISSUE] Waybar clock module broken with latest tzdata

[icp1994]

[-- Attachment #1: Type: text/plain, Size: 657 bytes --]

New issue by icp1994 on void-packages repository

https://github.com/void-linux/void-packages/issues/54018

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.10_1 x86_64 GenuineIntel uptodate ...

### Package(s) Affected

Waybar-0.11.0_2 tzdata-2025a_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/Alexays/Waybar/issues/3891

### Expected behaviour

The clock module should show timezone the specified tz in config.

### Actual behaviour

It shows time in UTC

### Steps to reproduce

Launch Waybar along it's default config with system clock set to a non-UTC tz.

Re: Waybar clock module broken with latest tzdata

[rationalize-zz]

[-- Attachment #1: Type: text/plain, Size: 476 bytes --]

New comment by rationalize-zz on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2599853077

Comment:
Did some testing, don't think its a Waybar issue directly.  When calling c++ std::chrono function current_zone(), always returns UTC (nothrow behavior).  When specifying a time zone, call locate_zone(), which throws exception with message around "tzdb: cannot locate zone:".  Maybe our build of libstdc++ or gcc is the issue?

Re: Waybar clock module broken with latest tzdata

[camj2]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

New comment by camj2 on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2600246400

Comment:
I'm also using Void Linux.

Re: Waybar clock module broken with latest tzdata

[camj2]

[-- Attachment #1: Type: text/plain, Size: 168 bytes --]

New comment by camj2 on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2600246400

Comment:
I'm also using Void Linux.

Re: Waybar clock module broken with latest tzdata

[EnumuratedDev]

[-- Attachment #1: Type: text/plain, Size: 428 bytes --]

New comment by EnumuratedDev on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2600797015

Comment:
Having the same issue with the new tzdata update as well. Downgrading to 2024a_2 seems to fix the issue. From what I could see only Waybar seemed to be affected by this. Running the date command in a terminal showed the correct time and SDDM was showing the correct time as well

Re: Waybar clock module broken with latest tzdata

[eoli3n]

[-- Attachment #1: Type: text/plain, Size: 152 bytes --]

New comment by eoli3n on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2600986722

Comment:
Same here

Re: Waybar clock module broken with latest tzdata

[juipeltje]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

New comment by juipeltje on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2601015340

Comment:
yeah same issue here, just came back to void linux after using nixos for 6 months, so unfortunately i can't downgrade the package to fix it. from what i gather in other topics a gcc update solves the issue, but i'm not sure how long that would take in the case of void...

Re: Waybar clock module broken with latest tzdata

[lady-melinoe]

[-- Attachment #1: Type: text/plain, Size: 321 bytes --]

New comment by lady-melinoe on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2601418089

Comment:
Currently using gcc14, compiling waybar on my system it still has the same issue?

![Image](https://github.com/user-attachments/assets/4a33d928-b320-4d4b-b295-512b727a3d49)

Re: Waybar clock module broken with latest tzdata

[lady-melinoe]

[-- Attachment #1: Type: text/plain, Size: 363 bytes --]

New comment by lady-melinoe on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2601418089

Comment:
Currently using gcc14, compiling waybar on my system it still has the same issue? (first time in bar is `date '+%I:%M %p'`)

![Image](https://github.com/user-attachments/assets/4a33d928-b320-4d4b-b295-512b727a3d49)

Re: Waybar clock module broken with latest tzdata

[rationalize-zz]

[-- Attachment #1: Type: text/plain, Size: 717 bytes --]

New comment by rationalize-zz on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2601838032

Comment:
Fixed via update to gcc's libstdc++:

https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=0ca8d56f2085715f27ee536c6c344bc47af49cdd

Format change in tzdb wasn't implemented in the c++ std lib.  This is why updating tzdata works just fine for everything written in C (like 'date' command), or at the very least doesn't access tzdb via c++ std::chrono library.

For an extra bit of fun here, this commit didn't make it into gcc 14.2.  Distros that don't have this issue have it fixed via 14.2.1, which doesn't seem to be an tagged release, not at least as far as I can find.

Re: Waybar clock module broken with latest tzdata

[jwakely]

[-- Attachment #1: Type: text/plain, Size: 453 bytes --]

New comment by jwakely on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2603501017

Comment:
> Distros that don't have this issue have it fixed via 14.2.1, which doesn't seem to be an tagged release, not at least as far as I can find.

By definition, 14.2.1 means "some snapshot between the 14.2.0 and 14.3.0 releases" so it will never be a tagged release. Releases always end in .0 (since GCC 5.1.0).

Re: Waybar clock module broken with latest tzdata

[rationalize-zz]

[-- Attachment #1: Type: text/plain, Size: 352 bytes --]

New comment by rationalize-zz on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2603974862

Comment:
Understood.  I've submitted PR https://github.com/void-linux/void-packages/pull/54061, which backports https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=0ca8d56f2085715f27ee536c6c344bc47af49cdd to gcc 13.2

Re: [ISSUE] [CLOSED] Waybar clock module broken with latest tzdata

[sgn]

[-- Attachment #1: Type: text/plain, Size: 660 bytes --]

Closed issue by icp1994 on void-packages repository

https://github.com/void-linux/void-packages/issues/54018

Description:
### Is this a new report?

Yes

### System Info

Void 6.12.10_1 x86_64 GenuineIntel uptodate ...

### Package(s) Affected

Waybar-0.11.0_2 tzdata-2025a_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://github.com/Alexays/Waybar/issues/3891

### Expected behaviour

The clock module should show timezone the specified tz in config.

### Actual behaviour

It shows time in UTC

### Steps to reproduce

Launch Waybar along it's default config with system clock set to a non-UTC tz.

Re: Waybar clock module broken with latest tzdata

[eoli3n]

[-- Attachment #1: Type: text/plain, Size: 265 bytes --]

New comment by eoli3n on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2607348550

Comment:
This is not fix, I still get UTC in waybar-clock after the upgrade
```
➜ xbps-query -l | grep gcc
ii gcc-13.2.0_3  
```

Re: Waybar clock module broken with latest tzdata

[eoli3n]

[-- Attachment #1: Type: text/plain, Size: 326 bytes --]

New comment by eoli3n on void-packages repository

https://github.com/void-linux/void-packages/issues/54018#issuecomment-2607348550

Comment:
This is not fix, I still get UTC in waybar-clock after the upgrade
```
➜ xbps-query -l | grep gcc
ii gcc-13.2.0_3  
```

---

edit: no i don't, i just didn't reload waybar properly