After upgrading to Thunderbird 60.5.1 the language of the Lightning calendar appears in English. I have reviewed the language supplements and they all appear disabled due to incompatibility with the version.
Same problem. "fr Language Pack Calendar" is IN the distribution. So i searched with MCC "cal" "fr" ligntning" and other words but didn't find it. I finally found it in the files of Thunderbird "/usr/lib64/thunderbird/distribution/extensions/langpack-cal-fr@lightning.mozilla.org.xpi". I installed the extension in Thunderbird from this file and there was no more incompatibility. When incompatible, the update date of this extension was Feb,14 2019, after fresh install, its update date is Feb,21 2019. But Calendar remains still in English and, i verified, it really french (for me) in the xpi files ;-)
CC: (none) => magnux77
Assigning to the registered maintainer, but CC'ing all packagers collectively, in case the maintainer is unavailable.
Assignee: bugsquad => doktor5000CC: (none) => marja11, pkg-bugs
I could reproduce here in MGA6. I have found a workaroud : remove Lightning extension, then add it back. Now it is in french. Looks like our packaging triggers some bug in Thunderbird... I have no idea where, but I see an error on each Thunderbird update in the post script trying to be run as root.
CC: (none) => lists.jjorge, nicolas.salguero
It's also a regression. Lightning is 6.2.5.1 before suppress and install, after it is 6.2.5.
Performing the action indicated by José Jorge, the problem is solved, we must eliminate and reinstall the thunderbird calendar to correct the problem. Contributed the solution and waiting for it to be fixed permanently, the calendar now if it is seen in Spanish.
Update to Thunderbird 60.6.0 solved it, update to 60.6.1 broke it again
CC: (none) => chmos
Update to Thunderbird 60.7.2 and broke it again. Regards!!
From the last update 68.1 solved it. Can anyone else confirm that?
(In reply to Jose Manuel López Díaz from comment #8) > From the last update 68.1 solved it. Can anyone else confirm that? I confirm it solved for me in portuguese.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
*** Bug 25068 has been marked as a duplicate of this bug. ***
CC: (none) => nk0885