-
-
Notifications
You must be signed in to change notification settings - Fork 732
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clock.timezone field has no effect #1806
Comments
oh and for what it's worth, i don't see an error on output:
i mean i see a bunch but nothing related to the clock widget, as far as i can tell. looking at the source code, i was expecting this to show up:
... but i don't see it... so maybe this is a bug in the date library, as it's the one setting the
|
Did you try with another timezone just to check? |
yes, i have just tried |
I think "Etc/UTC" is not a valid timezone string. It doesn't work for me either. I tried with "GMT" and "UTC" and they both worked. I also tried with "America/Chicago" and that worked. |
On 2022-11-27 17:53:39, EN wrote:
I think "Etc/UTC" is not a valid timezone string. It doesn't work for me either. I tried with "GMT" and "UTC" and they both worked. I also tried with "America/Chicago" and that worked.
Well I don't know how you tell what a valid string is, but I have tried:
* UTC
* GMT
* Etc/UTC
* America/Chicago
... none of those work here. I'll also note that the wiki page about the
clock module:
https://github.com/Alexays/Waybar/wiki/Module:-Clock
explicitly links to this Wikipedia page:
https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
... which lists "Etc/UTC" as "Canonical" and "UTC" as a "link" to
"Etc/UTC". :p
So something else is going on here. Maybe I have the wrong locale?
…--
La mer, cette grande unificatrice, est l'unique espoir de l'homme.
Aujourd'hui plus que jamais auparavant, ce vieux dicton dit
littéralement ceci: nous sommes tous dans le même bateau.
- Jacques Yves Cousteau - Océanographe
|
Oops, yeah if I run |
I'm seeing the same behavior as the original author. I've tried several timezones as well. Waybar 0.9.9 on Ubuntu 22.04... So I guess my next step is to update to the latest version. The 0.9.9 is what was distributed with Ubuntu. Update: Using the latest, built from commit c692d7b, works fine. |
using the latest in debian (0.9.17) and i still have this problem. |
i have also tried with the latest HEAD, no luck still. is there some way i could debug this further? i have tried enabling debugging (log-level=trace), but it doesn't give that much info. |
for the record, that was d259307 |
I have the following modules:
and they both display show up on the bar. however, the
clock#utc
widget has the same time as the mainclock
widget, even though they are supposed to be in different time zones.here, right now, the local zone (
%Z
) is UTC-5 (EST
), not UTC. Yet both times are identical. The second widget even says it's also showing meEST
which leads me to believe thetimezone
parameter is completely ignored.I have also tried using the
timezones
parameter instead,UTC
andIceland
as timezones, nothing seems to work. I have also tried to set it for the first clock, no effect.This is on waybar 0.9.15 on debian testing ("bookworm").
The text was updated successfully, but these errors were encountered: