1902666 - wrong time

Status: RESOLVED WORKSFORME

(Thunderbird :: Untriaged, defect)

Description

[[e-mail]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:126.0) Gecko/20100101 Firefox/126.0

Steps to reproduce:

did nothing

Actual results:

when email received is plus 1 hour, thunderbird version 128.0b1 (32-bit)

Comment 1

[Andre Klapper]

Does this happen for every email? Can you attach a testcase email (which contains no personal data)? What are your exact timezone settings on your system?

Comment 2

[[e-mail]]

hello, time zone is +2 athens
time is correct on pcs, on some emails changed the time by plus 1 hour, now shows it is correct, anyway thank you for your assistance

Comment 3

[Vlad Lucaci, Thunderbird QA (:vlucaci)]

Hello,

I have tried to reproduce your issue using the STR from the description and comment 2 but did not succeed using Win11, macOS 14 and Ubuntu 22.04 with the affected build from 2024-06-14(20240614101619) as well as 129.0b1(20240708223515), 1280.esr(20240710185639), and 115.13.0(20240709183211).

If you can still reproduce this issue with the same repro steps, it would very helpful if you could indicate the affected versions on which you are able to reproduce it(besides the 128.0b1 on which you have encountered it) and if time allows, help us with a regression range for this issue.
I will provide the steps necessary.

You have to determine a build that reproduces the issue. In your case it seems Thunderbird v128.0b1 (64-bit), right?

Then you should find one that does NOT reproduce it. Detailed steps:

a. Open Mozregression app;
b. Click "File" -> "Run a single build";
c. On the "Single Run Wizard" pop-up, "Basic configuration", select "Thunderbird" and click "Next".
d. On the "Profile selection" page, just click the "Next" button.
e. On the "Build selection" select a date (dates before 2024-06-14 to have a better chance finding one that does not reproduce the issue) from the drop-down on the left and click "Finish".
f. Now the mozregression app will open a thunderbird build of the selected date and you can use it, close it and open another. (make a note of the version that does not reproduce the issue)

You will use mozregression app to "bisect" builds that reproduce the issue by builds that do not reproduce it in search of the one build/changeset that introduced the issue, in the first place:
a. Open mozregression-gui.exe
b. Click "File" -> "Run a new bisection"
c. On "Basic configuration" screen, select "Thunderbird" and click "Next" button.
d. Skip "Profile selection" screen by the "Next" button.
e. On the Bisection wizard screen, you will need to select a build that reproduces the issue and one that does not:
e1. In the "Last known good build:" section, select "date" on the right drop-down and the date of the build you found NOT to reproduce the issue.
e2. In the "First known bad build:" section, select "date" on the right drop-down and the date of the build you found to reproduce the issue.
f. Click "Finish" to start the bisection process.
g. Builds will open one-by-one, you will need to test each one of them and see whether the issue reproduces. If it reproduces, then you need to select the "bad" button in the mozregression window and if not, you need to select the "good" button.
h. When bisection is done, you will have the information in the "Log View" section of the mozregression window; bisection may also fail due to not enough builds, but the logs can always be useful.
Copy the logs in a text file and attach it to this bug.

If there is still information you need regarding the regression process, please request information from me.
Thank you for your contribution!

Comment 4

[Alfred Peters [:infofrommozilla]]

(In reply to [e-mail] from comment #2)

hello, time zone is +2 athens
time is correct on pcs, on some emails changed the time by plus 1 hour, now shows it is correct, anyway thank you for your assistance

If I understand correctly, the problem no longer occurs!?
Then I'll close the bug for now.
If it does occur again, we can reopen it. But then we'll definitely need a test case.