wrong update channel when using lang packs - showing 138 beta - beta xpi language packs have been uploaded to the release channel.
Categories
(Thunderbird :: Build Config, defect, P1)
Tracking
(Not tracked)
People
(Reporter: sossami3884, Unassigned)
References
Details
(Keywords: regression, regressionwindow-wanted)
Attachments
(3 files)
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:136.0) Gecko/20100101 Firefox/136.0
Steps to reproduce:
Version Thunderbird was 136 normal release ; update occured... I accepted.
Actual results:
New version was 138, in beta version ! ! !
producing a bug in calendar.
Only the last account calendar created was working ; the previous accounts created before were disabled, and no way to recreate them again ; the creation always remained on the last account created.
Expected results:
Version should remain in normal canal.
Even downloading .exe installer from Thunderbird site or in archive releases, delivers the beta version without showing the b letter for Beta.
And calendars should keep on working well, all.
Comment 1•4 months ago
|
||
FWIW reports of this type are extremely rare, as measured in bugzilla https://mzl.la/4jHPPg9 Thunderbird reports of last 3 years. I found none in the toolkit update component.
Comment 2•4 months ago
|
||
Can you provide a screenshot of the about dialog?
Updated•4 months ago
|
Comment 3•4 months ago
|
||
@SAMI: Does your help screen look like this?
- mentions Thunderbird Beta in the title
- mentions the channel to be release
Sorry, I can't provide a screenshot. I'm computer repairer and it's about a machine customer of mine and I don't have it with me.
It's under Windows 10 64 bits family.
Exactly, we start with a "normal" Thunderbird release (nothing special in title bar) 128 or 136, and the dialog "Help / About" window shows nothing special about the channel.
But after clicking "Restart Thunderbird to update", version is 138 beta, and "beta" is indicated in the title bar (and calendars no more run well).
This morning, I did the same thing on another machine (another customer), under Windows 11 Pro ; everything was right, normal channel (and version) before and after update.
So, the question is : how to delete all traces of Thunderbird after removing it, to reinstall a normal version ? (138 if possible)
Is this a problem of installation ? or a problem of profile user ?
Comment 5•4 months ago
|
||
Is this a problem of installation ? or a problem of profile user ?
Not yet known.
So, the question is : how to delete all traces of Thunderbird after removing it, to reinstall a normal version ? (138 if possible)
I think we first need to determine how it happened, so it doesn't happen again for your user.
Comment 6•4 months ago
•
|
||
Before you start removing/updating Thunderbird, we first have to make sure you are really on beta. For me it looks like you are on Release, but the build uses a wrong name to identify itself.
The screenshot I shared shows that the update-channel is "release", even though the title says otherwise. Beta by the way is on 139.x.
It can very well be, that the bug regarding calendar is indeed a bug in Release.
Comment 7•4 months ago
|
||
URL please of where the installer was downloaded from.
Updated•4 months ago
|
I downloaded the installer in the first page of Thunderbird site : https://www.thunderbird.net/fr/
and I tried also the installer from the archive releases : https://archive.mozilla.org/pub/thunderbird/releases/138.0/win64/fr/Thunderbird%20Setup%20138.0.exe
(In reply to John Bieling (:TbSync) from comment #6)
Before you start removing/updating Thunderbird, we first have to make sure you are really on beta. For me it looks like you are on Release, but the build uses a wrong name to identify itself.
I'M NOT on beta, when I remove the 128 or the 136 version. 128 is esr ; 136 is release.
May be you're right... But, today, I tried the same handling on 2 different Windows 10 machines and everything was OK.
Very strange problem........... But for my customer, the real problem is on the calendar.
Comment 9•4 months ago
|
||
Same problem here on my iMac.
BTW I am the author (Mapenzi) of the cited thread in the German Thunderbird Mail DE forum.
When I realised this issue I re-downloaded a new copy of v138.0 from here https://www.thunderbird.net/fr/thunderbird/all/ and installed it over my actual version which had been updated from 137.0.2. But this didn't resolve this issue.
When I create a new test profile with the same TB 138.0 copy the issue no longer appears. So the error must be somewhere in the profile....
Comment 10•4 months ago
|
||
I installed 138.0 from https://www.thunderbird.net/en-US/download/ on Windows 11 and no trouble found.
Comment 11•4 months ago
|
||
Looks like a language pack problem, I have no problem with the installed en-us version.
If I switch to any other language (tested nl, de, fr and en-gb) I get the mismatched about dialog.
I have not noticed any calendar problems, but I don't use them very much.
Comment 12•4 months ago
•
|
||
John pointed out the strings for the about dialog:
https://searchfox.org/comm-central/source/mail/locales/en-US/messenger/aboutDialog.ftl#7
And in en-US we have -brand-full-name defined as one of:
mail/branding/thunderbird/locales/en-US/brand.ftl:-brand-full-name = Mozilla Thunderbird
mail/branding/nightly/locales/en-US/brand.ftl:-brand-full-name = Thunderbird Daily
mail/branding/tb_beta/locales/en-US/brand.ftl:-brand-full-name = Mozilla Thunderbird Beta
We can find translated versions in https://github.com/thunderbird/thunderbird-l10n
I don't see any issues with brand-full-name in that repo.
Comment 13•4 months ago
|
||
I installed the German version from https://download.mozilla.org/?product=thunderbird-138.0-SSL&os=linux64&lang=de and wasn't able to recreate this issue.
Comment 14•4 months ago
|
||
However, if I install the English (US) version, change the Language from English (US) to Deutsch in the settings, I am able to recreate.
Steps to reproduce:
- Install the en-US version of 138.0
- Go to Settings->Language
- Set Alternative to Deutsch
- Restart
- Help->About
Comment 15•4 months ago
•
|
||
Apparently beta xpi language packs have been uploaded to the release channel.
Comment 16•4 months ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #10)
I installed 138.0 from https://www.thunderbird.net/en-US/download/ on Windows 11 and no trouble found.
Did you create a new profile or did you start your v138.0 in an already existent "release" profile (see comment #9)?
Comment 17•4 months ago
|
||
In fact, the problem seems to be caused by language packs.
In my French 138.0 version I deleted the German and the English language packs and recovered the "release channel" !
Updated•4 months ago
|
Reporter | ||
Comment 18•4 months ago
|
||
Well...
OK for beta or no beta version.
But, what about bug calendar ?...
I think I'm going to create a new profile. But I'd want to save accounts mails (there are 10 !...) not to have to recreate them ; but I see that the export/import tool only allow to import accounts AND parameters, but no accounts only. Is there a way to export/import only accounts mails without profile parameters ?...
Comment 19•4 months ago
|
||
You may have seen bug 1964295 for calendar.
Updated•3 months ago
|
Updated•3 months ago
|
Comment 20•3 months ago
|
||
This appears to be limited to 138
Comment 21•3 months ago
|
||
A few more data points regarding the beta/release issue.
- Both versions (for example Beta 137.0b1 and Release 137.0) use the same URL to request available lang packs: https://services.addons.thunderbird.net/api/v3/addons/language-tools/?app=thunderbird&type=language&appversion=137.0
- It is obvious that Beta and Release use the same lang pack files.
- The about dialogs use different images based on the channel, not based on the locale macro
- I downloaded all lang packs for arabic and french from 127 to 138
- arabic had "Beta" in it in versions 131, 134 and 138
- french had "Beta" in it in version 138
So this is purely a lang pack issue.
- Should we at all use tb_beta branding for the localized beta versions (Firefox does not)? Only the shipped-with-the-product locales will be able to properly use "Beta" for Beta (which could lead to confusion)
- Lang packs should not use Beta branding
- How can the french and the arabic lang pack for the same version have different branding? How are they prepared?
Comment 22•3 months ago
|
||
I would like to report a case that occurred with the Japanese version.
Steps to reproduce:
- Install the ja version of Thunderbird 137.0.2 and start it.
- Install
japanese_ja_language_pack-137.0.20250327.75402-tb.xpi
to Thunderbird. - Update Thunderbird to 138.0.
Actual results:
The language pack has been updated to the Beta version(138.0.20250422.130245), and the product name has been changed to "Thunderbird Beta" in the about dialog, etc.
Removing the language pack restored the display to "Thunderbird".
Expected results:
When Thunderbird is updated on a release channel, the language packs for that release channel should be used.
There is no problem in Firefox.
Comment 23•3 months ago
|
||
- On a Japanese website "窓の杜" that introduces Windows software, an image in an article about Thunderbird 138 also shows it as "Thunderbird Beta"
https://web.archive.org/web/20250511121151/https://forest.watch.impress.co.jp/img/wf/docs/2011/007/html/image1.png.html - When I access https://addons.thunderbird.net/ja/thunderbird/language-tools/ from Thunderbird, the language pack for the release channel is downloaded.
- Actually, I don't remember installing any language packs, which is strange.
![]() |
||
Comment 24•3 months ago
|
||
![]() |
||
Comment 25•3 months ago
|
||
Confirmed on german version 138.0 with "English (GB) (en-GB)" language pack.
Reporter | ||
Comment 26•3 months ago
|
||
(In reply to Magnus Melin [:mkmelin] from comment #19)
You may have seen bug 1964295 for calendar.
Yes, I read it. Thank you. I hope it will be corrected in next release version (not a beta one).
For "beta bug", I started with a complete new profile (not the existing one), and there was no more problem upgrading version :-)
Comment 27•3 months ago
•
|
||
We fixed this for all affected locales. You may have to manually search for updates in the add-on manager for the changes to be picked up. After 24h, Thunderbird should automatically do that for you.
We now know what happened, will monitor for similar cases in the future, and work on a permanent solution. This work is being tracked here:
Description
•