Calendars go offline after program start - says credentials are not ok. But same credentials are accepted with 137. 0.2
Categories
(Calendar :: Provider: CalDAV, defect)
Tracking
(Not tracked)
People
(Reporter: rikardo.tinauer, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:137.0) Gecko/20100101 Firefox/137.0
Steps to reproduce:
After I start Thunderbird and after program does all refreshing all calendars are DISABLED, this is on version 138.0b3 (64-bit). All my calendars are network calendars from the same server.
I run Thunderbird on linux.
Calendars are working fine in version 137.0.2.
After checking the difference in these two versions I found that 138.0b3 does not get past entering credentials (trying to create new calendars). The password I entered keeps getting back the message that credentials are not ok. But same credentials are accepted with 137. 0.2. I tried several times, even copy-paste to ensure to ensure my credentials were correct.
Actual results:
The result is that version 138.0b3 disables all calendars from the same server.
Comment 1•1 year ago
|
||
Do you know that server software is used?
Comment 2•1 year ago
|
||
xref bug 1920710.
Can you try both these builds to see if you get a different result?
#1 https://ftp.mozilla.org/pub/thunderbird/nightly/2025/03/2025-03-18-10-20-18-comm-central/
#2 https://ftp.mozilla.org/pub/thunderbird/nightly/2025/03/2025-03-19-10-22-22-comm-central/
| Reporter | ||
Comment 3•1 year ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #1)
Do you know that server software is used?
Server software is Apple CalendarServer - open source running on linux
| Reporter | ||
Comment 4•1 year ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #2)
xref bug 1920710.
Can you try both these builds to see if you get a different result?
#1 https://ftp.mozilla.org/pub/thunderbird/nightly/2025/03/2025-03-18-10-20-18-comm-central/
#2 https://ftp.mozilla.org/pub/thunderbird/nightly/2025/03/2025-03-19-10-22-22-comm-central/
Tried 138.0a1 (2025-03-19) (64-bit) Thunderbird Daily and Calendar works
| Reporter | ||
Comment 5•1 year ago
|
||
Meanwhile I have upgraded to 138.0b4 (64-bit) but calendar still does not work
Comment 6•1 year ago
|
||
Ok, not from bug 1920710 then as that's in 2025-03-19.
Can you try mozregression to get a regression range: https://mozilla.github.io/mozregression/quickstart.html
| Reporter | ||
Comment 7•1 year ago
|
||
I can but I do not know what the "good" date was, I did not write it down the day it broke
Comment 8•1 year ago
|
||
You just start with 2025-03-20 (as previous was known good) and go from there. There's not that many days.
| Reporter | ||
Comment 9•1 year ago
|
||
Ok, tommorow
| Reporter | ||
Comment 10•1 year ago
|
||
1962189 - not the same behavior as mine, a cannot get past credentials verification
| Reporter | ||
Comment 11•1 year ago
|
||
Magnus cannot do it, mozregression tool crashes "Seg fault". Cannot build it my self as I have some problems with repos for apt.
But I believe I provided pretty much detailed information to fix it
Comment 12•1 year ago
|
||
You could manually test builds as well by downloading from the nightly ftp builds - https://ftp.mozilla.org/pub/thunderbird/nightly/2025/03/
Comment 13•1 year ago
|
||
Can confirm I have this same error with 138 on Manjaro. Downgraded to 137.0.2 (with profile downgrade included), it works there.
Comment 14•1 year ago
|
||
(In reply to Rikardo Tinauer from comment #11)
Magnus cannot do it, mozregression tool crashes "Seg fault". Cannot build it my self as I have some problems with repos for apt.
If mozregression crashes and you don't see the crash listed in https://mzl.la/4j6kL8Z, please report the bug https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=mozregression
| Reporter | ||
Comment 15•1 year ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #14)
(In reply to Rikardo Tinauer from comment #11)
Magnus cannot do it, mozregression tool crashes "Seg fault". Cannot build it my self as I have some problems with repos for apt.
If mozregression crashes and you don't see the crash listed in https://mzl.la/4j6kL8Z, please report the bug https://bugzilla.mozilla.org/enter_bug.cgi?product=Testing&component=mozregression
I get no message when crash happens, the crash happens at starting the mozregressiom-gui program, so the only thing I get is
"Segmentation fault (core dumped)" message in console. Is there any log file so I can check the log and send it to you?
Comment 16•1 year ago
|
||
Would assume this is duplicate of bug 1964295
Description
•