Message timestamps shown in wrong timezone #43

ncraike · 2019-06-04T03:30:38Z

As of the last few days, when I run the Flatpak-installed Slack app, my messages are timestamped with the wrong timezone.

The timestamps seem to be UTC. My actual timezone is Brisbane/Australia (UTC+10). So for example, a message received at 1:23pm local time will be shown timestamped 03:23 instead of 13:23.

This doesn't happen if I login to the same Slack workspace through a web browser (e.g. Firefox). In Firefox the correct timestamps (local time) are shown.

I'm running Fedora release 30. I upgraded from Fedora release 29 a few weeks ago. This issue is more recent than that (the last few days).

$ timedatectl
              Local time: Tue 2019-06-04 13:26:01 AEST
          Universal time: Tue 2019-06-04 03:26:01 UTC
                RTC time: Tue 2019-06-04 13:26:01
               Time zone: Australia/Brisbane (AEST, +1000)

$ flatpak run com.slack.Slack
Gtk-Message: 13:20:05.439: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "pk-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "pk-gtk-module"
Creating Slack Application

The text was updated successfully, but these errors were encountered:

mvermaes · 2019-06-04T06:25:40Z

I see the same behaviour here, but I'm still on Fedora 28. It wasn't occurring until I updated Slack flatpak to 3.4.2 this morning. Pretty sure I was on 3.4.0 previously.

FakeShemp · 2019-06-04T07:07:29Z

Timestamps locale work here on Manjaro, so I don't think there's anything I've broken in the manifest itself.

If you could try to run

flatpak update --commit=014b6644d7f75120a47e7edce86a875c81b4e27a1844bfcfafcfe6280bdfafd6 com.slack.Slack

to install the version with just an update to 3.4.2. If that still doesn't work, then it's probably an issue with Slack itself.

mvermaes · 2019-06-04T07:31:05Z

Yep, same problem after using the commit you mentioned. Going one further back to 3.4.0 (810ae703) shows the correct timestamp again.

FakeShemp · 2019-06-04T08:16:14Z

I'm leaning towards this being a Slack or Electron issue. If you have the option to try out the official installs, that would narrow it down a bit.

mvermaes · 2019-06-04T08:31:53Z

slack-3.4.2-0.1.fc21.x86_64.rpm is working OK for me (edit: with the correct timestamp shown).

EspadaV8 · 2019-06-04T22:56:48Z

Also having the same issue in Fedora 30, also in Brisbane. Using the official RPM shows the correct timestamps for the messages. Changing the timezone settings within the app doesn't change the timestamps in the app.

trnubo · 2019-06-05T07:55:31Z

Also having this issue on Fedora 30 and the latest version from Flathub. Only after going back to 3.4.0 where the times correct.

flatpak update --commit 810ae703189dd439c5a7059accf33af495d415e2d46545a3bfcccf445ab7c092 com.slack.Slack

FakeShemp · 2019-06-05T09:05:35Z

I really have no idea why it happens. Any help is appreciated.

Comparing the binaries between the RPM and the Deb packages, they differ for some reason. I'm wondering if there's changes specifically for Fedora. I'll look into it.

mvermaes · 2019-06-06T05:32:41Z

This also works around the problem in my case:

flatpak run --env=TZ=Australia/Perth com.slack.Slack

Found from https://github.com/flathub/com.valvesoftware.Steam/wiki/Frequently-asked-questions#im-having-incorrect-timezone-in-steam

Also, in case it's relevant, I have the Slack flatpak installed as a user (--user) rather than system-wide.

(Edit: I can't reproduce this any more):
~~Checking the timezone info in the flatpak, 3.4.0 has /etc/localtime set to UTC:~~
$ flatpak run --command=bash com.slack.Slack
bash-4.4$ zdump /run/host/monitor/localtime
/run/host/monitor/timezone Thu Jun 6 05:00:03 2019
whereas 3.4.2 has it set to AWST (the local timezone):
$ flatpak run --command=bash com.slack.Slack
bash-4.4$ zdump /run/host/monitor/localtime
/run/host/monitor/localtime Thu Jun 6 13:05:00 2019 AWST

josmardias · 2019-06-28T15:03:03Z

Maybe related to
flatpak/flatpak#2190 ?

FakeShemp · 2019-07-09T13:35:33Z

I went back to this today by installing Fedora 30 and trying it out. I was not able to reproduce. However, I did add a note about it and how to fix it in the readme here on Github, in case others find themselves in the same situation.

NamelessVoice · 2019-07-26T09:53:25Z

I've also been seeing this recently, though it used to work correctly in the past.
In my case it thinks I'm in India time instead of GMT.

Explicitly passing in the timezone through the --env flag works around the problem.

Version 4.0.0 of the Flatpak on Linux Mint.
com.slack.Slack/x86_64/stable system, current

dolfandringa · 2019-08-26T00:55:30Z

The above workaround by mvermaes works for me too. But without it I have had the issue from (I think) Fedora 28 up to now in Fedora 30. I am running with gnome3 on kernel 5.2.9-200 and the flatpak install 4.0.1. The timestamps are off by 3 hours for me without the workaround
This is my timezone info (which is correct).

$ timedatectl
               Local time: Mon 2019-08-26 08:44:22 PST
           Universal time: Mon 2019-08-26 00:44:22 UTC
                 RTC time: Mon 2019-08-26 08:44:21
                Time zone: Asia/Manila (PST, +0800)
System clock synchronized: no
              NTP service: inactive
          RTC in local TZ: yes

I am running kernel 5.2.9-200 right now (but again, this has been bugging me since I think F28) and this is my Slack installation:

          ID: com.slack.Slack
         Ref: app/com.slack.Slack/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 4.0.1
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 2.8 MB
     Runtime: org.freedesktop.Platform/x86_64/18.08
         Sdk: org.freedesktop.Sdk/x86_64/18.08

      Commit: a10574ca28995af9d14a2510e369e458d47b0b35b78e80b7fae29995b607bd16
      Parent: dd864e4fc3d1eab1c29930e1f913bbc83c88cfdaa805a09e088b495563977703
     Subject: Update to 4.0.1 (bc4873db)
        Date: 2019-07-31 11:43:20 +0000

shnplr · 2019-09-10T23:59:15Z

worked for me
$ flatpak override --user --env=TZ=Australia/Sydney com.slack.Slack

bauermann · 2019-12-17T15:06:12Z

I have found one clue. If I change the /etc/localtime symlink to ../usr/share/zoneinfo/America/Sao_Paulo, then Slack shows the correct timestamps.¹

Original value of the /etc/localtime symlink (and also the /etc/timezone one):

$ ls -l /etc/localtime /etc/timezone
lrwxrwxrwx 1 bauermann bauermann 27 Dec 17 11:34 /etc/localtime -> /run/host/monitor/localtime
lrwxrwxrwx 1 bauermann bauermann 26 Dec 17 11:34 /etc/timezone -> /run/host/monitor/timezone
$ cat /etc/timezone
America/Sao_Paulo

So my suspicion is that something inside Slack doesn't know how to cope with the /etc/localtime symlink not being of the form some/path/America/Sao_Paulo

I'm also using Fedora 30. Flatpak is version 1.4.3.
The TZ override works around the problem for me as well.

--
¹ Well, it would if the runtime had up-to-date zoneinfo files. But that's another problem.

mvermaes · 2020-02-12T02:40:16Z

I've been testing each new release as they came out and they all had the same problem until the recent update to 4.3.2.

I no longer need to use the --env=TZ=... workaround with this version. I'm on Fedora 30 now as well, but the rest of the system is otherwise unchanged.

mopsfelder · 2020-02-12T13:17:33Z

For me, this issue no longer exists with slack-4.3.2-0.1.fc21.x86_64 on Fedora 31, i.e.: timestamps of the messages are displayed correctly without any timezone work-around in place.

Thank you!

barthalion · 2020-02-12T17:15:55Z

@mopsfelder Well, we're not Fedora, but you're welcome!

Yes, 4.3.2 landed today to stable branch. Closing if you say it's fixed.

FakeShemp added bug help wanted labels Jul 9, 2019

barthalion closed this as completed Feb 12, 2020

mattlong-finocomp mentioned this issue Oct 8, 2020

Message timestamps wrong after DST change #94

Closed

Aiz0 mentioned this issue Jul 1, 2022

Convert "Permieres on" UTC time to local time FreeTubeApp/FreeTube#1429

Closed

kaiwalyajoshi mentioned this issue Dec 7, 2022

Message Timestamps in wrong timezone. #187

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Message timestamps shown in wrong timezone #43

Message timestamps shown in wrong timezone #43

ncraike commented Jun 4, 2019

mvermaes commented Jun 4, 2019

FakeShemp commented Jun 4, 2019 •

edited

Loading

mvermaes commented Jun 4, 2019

FakeShemp commented Jun 4, 2019

mvermaes commented Jun 4, 2019 •

edited

Loading

EspadaV8 commented Jun 4, 2019

trnubo commented Jun 5, 2019

FakeShemp commented Jun 5, 2019

mvermaes commented Jun 6, 2019 •

edited

Loading

josmardias commented Jun 28, 2019

FakeShemp commented Jul 9, 2019

NamelessVoice commented Jul 26, 2019 •

edited

Loading

dolfandringa commented Aug 26, 2019

shnplr commented Sep 10, 2019 •

edited

Loading

bauermann commented Dec 17, 2019

mvermaes commented Feb 12, 2020 •

edited

Loading

mopsfelder commented Feb 12, 2020

barthalion commented Feb 12, 2020

Message timestamps shown in wrong timezone #43

Message timestamps shown in wrong timezone #43

Comments

ncraike commented Jun 4, 2019

mvermaes commented Jun 4, 2019

FakeShemp commented Jun 4, 2019 • edited Loading

mvermaes commented Jun 4, 2019

FakeShemp commented Jun 4, 2019

mvermaes commented Jun 4, 2019 • edited Loading

EspadaV8 commented Jun 4, 2019

trnubo commented Jun 5, 2019

FakeShemp commented Jun 5, 2019

mvermaes commented Jun 6, 2019 • edited Loading

josmardias commented Jun 28, 2019

FakeShemp commented Jul 9, 2019

NamelessVoice commented Jul 26, 2019 • edited Loading

dolfandringa commented Aug 26, 2019

shnplr commented Sep 10, 2019 • edited Loading

bauermann commented Dec 17, 2019

mvermaes commented Feb 12, 2020 • edited Loading

mopsfelder commented Feb 12, 2020

barthalion commented Feb 12, 2020

FakeShemp commented Jun 4, 2019 •

edited

Loading

mvermaes commented Jun 4, 2019 •

edited

Loading

mvermaes commented Jun 6, 2019 •

edited

Loading

NamelessVoice commented Jul 26, 2019 •

edited

Loading

shnplr commented Sep 10, 2019 •

edited

Loading

mvermaes commented Feb 12, 2020 •

edited

Loading