Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

ძიება მხარდაჭერაში

ნუ გაებმებით თაღლითების მახეში. აქ არავინ უნდა მოგთხოვოთ ტელეფონზე დარეკვა, შეტყობინების გაგზავნა ან პირადი მონაცემების გაზიარება. რამე საეჭვოს შემჩნევისას გთხოვთ გვაცნობოთ „დარღვევის მოხსენებით“.

ვრცლად

Thunderbird displaying wrong time

  • 3 პასუხი
  • 2 მომხმარებელი წააწყდა მსგავს სიძნელეს
  • 109 ნახვა
  • ბოლოს გამოეხმაურა mozilla113

სხვა პარამეტრები

The time shown in the Date column for TB is 2 hrs earlier than the actual time. The TB error console also displays the wrong time.

TB 128.6.0esr on freebsd-13.4-RELEASE-p5

System time is set to and displays as MDT (US Mountain/Denver) $ date Fri Apr 18 12:29:52 MDT 2025

TB error console: Date() "Fri Apr 18 2025 10:31:04 GMT-0800 (GMT-08:00)"

about:config timezone settings: calendar.timezone.local MST calendar.timezone.recent [] calendar.timezone.useSystemTimezone true mailnews.sender.date_senders_timezone false

Mail headers show proper time in mail file: Received: from mail-yb1-f187.google.com (mail-yb1-f187.google.com [209.85.219.187]) ... for <xxx>; Fri, 18 Apr 2025 11:55:40 -0600 (MDT) Received: by mail-yb1-f187.google.com with SMTP id 3f1490d57ef6-e5740c858besf2902470276.2 ... for <xxx>; Fri, 18 Apr 2025 10:55:39 -0700 (PDT)

And display properly in the TB headers display: Date Fri, 18 Apr 2025 11:55:29 -0600

Yet TB displays 2 hrs earlier in the Date column: 09:55

How to correct? I had set the Calendar timezone manually, but it is now set as above. I tried deleting calendar.timezone.local but it is rewritten when TB exits.

The time shown in the Date column for TB is 2 hrs earlier than the actual time. The TB error console also displays the wrong time. TB 128.6.0esr on freebsd-13.4-RELEASE-p5 System time is set to and displays as MDT (US Mountain/Denver) $ date Fri Apr 18 12:29:52 MDT 2025 TB error console: Date() "Fri Apr 18 2025 10:31:04 GMT-0800 (GMT-08:00)" about:config timezone settings: calendar.timezone.local MST calendar.timezone.recent [] calendar.timezone.useSystemTimezone true mailnews.sender.date_senders_timezone false Mail headers show proper time in mail file: Received: from mail-yb1-f187.google.com (mail-yb1-f187.google.com [209.85.219.187]) ... for <xxx>; Fri, 18 Apr 2025 11:55:40 -0600 (MDT) Received: by mail-yb1-f187.google.com with SMTP id 3f1490d57ef6-e5740c858besf2902470276.2 ... for <xxx>; Fri, 18 Apr 2025 10:55:39 -0700 (PDT) And display properly in the TB headers display: Date Fri, 18 Apr 2025 11:55:29 -0600 Yet TB displays 2 hrs earlier in the Date column: 09:55 How to correct? I had set the Calendar timezone manually, but it is now set as above. I tried deleting calendar.timezone.local but it is rewritten when TB exits.

გადაწყვეტა შერჩეულია

I finally solved this problem. The timezone is normally installed at /etc/localtime. It is a specially formatted binary file, selected from /usr/share/zoneinfo/ The file in /etc/localtime was installed back in 2020 and never updated, and differed in some way from the file in /usr/share/zoneinfo/America/Denver Replacing /etc/localtime with /usr/share/zoneinfo/America/Denver solved the issue. This article was helpful. At the same time I also changed calendar.timezone.local to America/Denver but I don't think that was related.

პასუხის ნახვა სრულად 👍 0

ყველა პასუხი (3)

სხვა პარამეტრები

what does your operating system return as the content of the TZ variable? What shows in the Date: header of the messages, that is the critical item here not the various received headers.

სხვა პარამეტრები

Thanks for the reply, sorry I left out the Date header.

The TZ environment variable is not set.

The Date: header is 2 hrs past the date displayed by TB, e.g.:

Date Sun, 20 Apr 2025 16:44:10 +0000

but TB shows:

04/20/2025 08:44 (should be 10:44, UDT-6 for MDT)

სხვა პარამეტრები

შერჩეული გადაწყვეტა

I finally solved this problem. The timezone is normally installed at /etc/localtime. It is a specially formatted binary file, selected from /usr/share/zoneinfo/ The file in /etc/localtime was installed back in 2020 and never updated, and differed in some way from the file in /usr/share/zoneinfo/America/Denver Replacing /etc/localtime with /usr/share/zoneinfo/America/Denver solved the issue. This article was helpful. At the same time I also changed calendar.timezone.local to America/Denver but I don't think that was related.