Description of problem: After updating to thunderbird 52.0, none of the emails in my email folder containing multipart text/calender entries, nor mails containing .ics attachments are recognized as calendar invitations. That means - none of the buttons handling event invitaions (accept, decline etc.) are available. - The email body of calendar emails is not shown at all. Version-Release number of selected component (if applicable): Tested with both: thunderbird-52.0-1.fc25.x86_64.rpm thunderbird-52.0-2.fc25.x86_64.rpm How reproducible: Just update to 52.0 Corinna
Thanks for the report. Please try to run Thunderbird in safe mode, ie. thunderbird --safe-mode to temporarily disable any addons which could do that. Could you find anything what might be related to it (like something new shows there when selecting message with invitation) on TB Error console (Ctrl-Shift-J is the shortcut).
Hi Jan, I tried it, but running TB in safe mode disabled *all* extensions, even Lightning. So in safe mode the recognition of email invitations is switched off anyway, isn't it? I attached the output on the TB error console. All of these messages are generated at TB startup. There's no new entry in the console when selecting a mail including a calendar event, unfortunately. But from TB's point of view all these mails are just mails, and the text/calendar entry is ignored. Corinna
Created attachment 1272242 [details] TB error console output
Yes, you're right, safe-mode will disable the lightning extension too. You may check the list of installed extension in Tools/Addons/Extensions and disable the other ones if there are any. Hm, looks like you're using German language, right? If not, what locale are you using? Could you please run Thunderbird in English by using 'LC_ALL=en_US.utf8 thunderbird' from terminal and retest the problem.
I disabled all other extensions: - LookOut - Mailbox Alert - Provider for Google Calendar to no avail. With these extensions still disabled I also started TB with LC_ALL=en_US.utf8, but the problem persists. My default language setting for thunderbird is LC_ALL=de_DE.utf8. However, now that you mention it, I noticed something else with this setting: Only the non-Lightning parts of the GUI are in german. All lightning GUI text and dialog content is in English. Even the Calendar tab is now "Calendar" instead of "Kalender". Btw., when starting TB from the command line, it prints this to the console window: [calBackendLoader] Using Thunderbird's builtin libical backend It also prints: Error: Couldn't find (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna Error: Couldn't find Customized Time Zone I'm using the "Europe/Berlin" timezoone in the Calendar settings. Corinna
Ok, so I found a way to restore TB to recognize mail again: If I move ~/.thunderbird into a safe place and start with TB from scratch, TB 52.0 works as desired: Calendar mails are recognized, the Lightning texts are in German. However, that's not how I'd like to proceed. I have multiple calendars and 10 or so mailboxes. Is there some way to try removing just the Lightning settings and set up only the Calendar from scratch? I really don't want to have to configure everything anew. Help? Please? Thanks, Corinna
What is the lightning version you have installed? Check the list of addons to get that. Working is the Lightning 5.4. Sometimes the problem is with old Lightning version kept during the update of Thunderbird or the extension is not correctly updated. To reinstall lightning extension from system location you need to uninstall it first (go to Tools/Addons, find Lightning, click Remove) and then go to Edit/Preferences/Advanced/General/Config Editor, look for: extensions.installedDistroAddon.{e2fda1a4-762b-4020-b5ad-a41df1933103} and delete it (right click on it, then reset). After TB restart the lightning extension should be reinstalled from system location.
Hi Jan, Lightning is 5.4, of course. I tried to remove and reinstall the extension but to no avail. What I also tried was to start with the scratch prefs.js created by the process outlined in comment 6, and then to copy over the mail settings from my original prefs.js. So I replaced all mail* settings of the new prefs.js with all mail* settings of my original prefs.js. The surprising result was that calendar mails were again not recognized with this new, handcrafted prefs.js. It seems that the 5.4 Lightning extension has trouble with some of the mail.* entries, but unfortunately the settings are pretty convoluted. From what I grasped while trying to disentangle them there are also old entries in there which are inactive for a long time. It's hard to distinguish them, though. Since I really need my calendar I now ended up recreating all my TB and Lightning settings from scratch. And even though I'm now using the same settings and extensions as before, the new .thunderbird settings dir works, while the original one does not. Your choice how to proceed. There's apparently a bug in the way Lightning evaluates the thunderbird mail prefs. I still have my original .thunderbird profile dir and especailly the original prefs.js for inspection, but I wouldn't want to attach it to a public case, obviously. Thanks, Corinna
Looking at the sources which are responsible for showing the invitation UI, there's no sign of checking the user prefs. If you really feel you'd like to experiment more, feel free to create a diff between old and new prefs.js and see if anything interesting shows up.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.