Skip to content
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

debug ntp/timezones with respect to chrome(ium) and Firefox #17

Open
ejmg opened this issue Oct 2, 2018 · 1 comment
Open

debug ntp/timezones with respect to chrome(ium) and Firefox #17

ejmg opened this issue Oct 2, 2018 · 1 comment

Comments

@ejmg
Copy link
Owner

ejmg commented Oct 2, 2018

This is definitely in connection with #16.

timedatectl status yields:

               Local time: Tue 2018-10-02 01:24:12 CDT
           Universal time: Tue 2018-10-02 06:24:12 UTC
                 RTC time: Tue 2018-10-02 06:24:12
                Time zone: America/Chicago (CDT, -0500)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: no

At face, it seems chrome(ium) and firefox should be displaying time stamps correctly in applications like gmail and twitter, but they don't. I think this may have something to do with NPT not being configured correctly and or my initial failure to setup the system timezone as directed via the wiki.

@ejmg
Copy link
Owner Author

ejmg commented Oct 2, 2018

hmmmmmmmmmmmmmmmmmmmmmmmm, end of that thread either indicates user incompetence or that there is a legitimately packaging issue at play for chromium.

Leaning towards former given that Firefox also shows this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant