1793063 - Wrong date when creating whole day event

Status: RESOLVED DUPLICATE of bug 1802316

(Calendar :: Calendar Frontend, defect)

Description

[L.I.A.R.]

Attachment: BugAllDayEvent.png

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:105.0) Gecko/20100101 Firefox/105.0

Steps to reproduce:

Component: Calendar (Why isn't it present in the drop down list? It's been years that it has been integrated in ThB).

I right-clicked on the square right below a date (week view / green dot in screenshot), here Jan 17 2023, to create a whole day event.

Actual results:

The event creation dialog that appears shows "10/04/2022" (cf red markings in screenshot) as the date for the event!!!!!

Expected results:

The date in the dialog MUST be the date I selected when I right-clicked under a date in the calendar

Comment 1

[Thomas D. (:thomas8)]

Liar (reporter), this works for me on 102.3.1 (64-bit), Win10, as well as 107.0a1 (2022-09-30) (64-bit).

Please always include the exact version of TB in your bug reports.
I am not sure how you'd get into the UI state of the screenshot because that doesn't even have all-day checked.
What I'm seeing is that the time slot where one clicks is not considered for the new event - that's odd.

Does this work for you with ≡ > Help > Troubleshoot Mode…?

Comment 2

[L.I.A.R.]

Hi,
I'm currently using "102.3.3 (64-bit)", in which behavior is still totally wrong : created event is on the wrong day and has hours, even if I created it as a whole day event...

Comment 3

[Wayne Mery (:wsmwk)]

but Does this work for you with ≡ > Help > Troubleshoot Mode…?

Comment 4

[L.I.A.R.]

Hi,

Thanks for your feedback and sorry for the delay in answering.

I encountered again this problem in ThB 102.6.1 (64-bit).

Following your advice, I tested in "Troubleshoot Mode". It works.
Then I restarted ThB in normal mode and deactivated the 3 add-ons I use. I works. So it's not a configuration problem.
Then I re-added one by one each add-on and it works after each and/or all of them are re-activated. So it's not an add-on problem either.

The only difference between /before all the tests/ (my bug report) and /after all the tests/ (now) is that I restarted ThB (otherwise, I just let it open and put my machine to sleep).

As a consequence, I think it is a (very strange) artefact that comes from the fact that I might have upgraded my packages while leaving ThB running, thus having a version in memory that was not the same as the one on the HDD.

I would love to find why this happens though.

Also, I had similar problems with FF, but no FF is warning me that the HDD version has diverged from the one in memory and forces me to restart it. Maybe the same thing should be done with ThB?

Comment 5

[L.I.A.R.]

Hi again,

The problem occurred to me again yesterday at night, but this time, I did not upgrade anything while ThB was running.

So the problem seems to rather be related to putting the machine to sleep (by closing the lid) and/or the lost/reopening of another connection that is a consequence of the sleep.

Comment 6

[Martin Schröder [:mschroeder]]

Have you tried Thunderbird 115 and do you still experience this issue ?