Calendar locks (read-only) upon Thunderbird restart

[neXussT]

Thunderbird 52.8.0 64bit ExchangeCalendar: 4.0.0-beta6 Ubuntu 16.04 with Unity WM

Issue: Hi. I've been using ExchangeCalendar for a couple months now. It works great, however whenever I restart Thunderbird, the calendar goes into read-only mode. In the Calendar window, it shows a lock icon beside the calendar name. When I double click on it to see the properties, the read-only checkbox is checked. If I uncheck and save nothing happens - it remains read-only.

Workaround: Unsubscribe from calendar. Disable ExchangeCalendar. Restart Thunderbird. Enable ExchangeCalendar. Restart Thunderbird. Create the calendar again with the normal process.

I have a basic understanding of JavaScript, so I may be able to help fix the issue. However, I have no idea where to look, or how any of this works. I would appreciate it if someone could track down where the defect could be, then I could look into it.

[DutchFlander]

Hi,

In my case the whole TB was hanging sometimes because of exchange calendar. The solution in these cases are to go to your profile folder and delete this dir: c:\Users\<username>\AppData\Roaming\Thunderbird\Profiles\<your profile>\exchange-data After restarting TB the data will be synced again and you don't have to unsubsribe and subscribe again.

Hope, it helps! in your case as well!

[MartijnRas]

I have the same problem, at first I used the unsubscribe -> subscribe workaround. Later I found out the following procedure to be easier:

Open the Exchange (EWS) properties Set or unset the domain name field Click the 'Check server and mailbox' button Click the 'Save and reset' button

[fprawits]

I am on TB 52.9.1 (64bit) that ships with Ubuntu 18.04 and I am having a similar, maybe even the same problem (I was already thinking about opening my own issue thread).

Whenever I add my company's hosted exchange calender it works fine until I restart Thunderbird. At the restart, I get prompted 3 times by the 'Microsoft Exchange EWS: Password request." and the calendar is set to read-only. Additionally I noticed a list of queued jobs that is kind of stuck (and is slowly growing) whenever I do enter my password into the request prompts.

Until now I always had to unsubscribe and add the calendar to get it working again. MartijnRas' trick with checking the server and mailbox button again at least speeds up the process of getting the calendar to work again, but it is still very tedious to do, so hopefully one of the devs can give us some direction on this.

I am using the latest 'release' of exchange-calendar: v4.0.0-beta5 The TB profile is a new one, since I am on a fresh install of ubuntu 18.04, the only other extensions I am using are:

• Lightning 5.4
• ExQuilla for Microsoft Exchange 60.0 (for getting my exchange mail into TB)
• EDS Calendar Integration 0.5 (one-way sync down to the gnome-calendar)

[fprawits]

So I don't want to be celebrating pre-maturely, but I might have found a fix for the calendar issue. I changed from the domain\username scheme to username@domain. You can change your settings regarding this via the "Exchange (EWS) properties" menu entry available when right clicking on your calendar in TB's calendar list. The username@domain part has to be entered in the username field, after that the domain field can be left empty and you have to recheck the mail settings via the button below and probably enter your password again.

I will keep observing this behaviour, if I am not replying here any more, that probably means that everything is working fine now ;).

[halbekanne]

I experience exactly the same problem as @fprawits and sadly the different naming scheme did not fix the issue for me. Today (I think it happens after a reboot or something) it asked me again 3-4 times for the password.

Additionally I noticed a list of queued jobs that is kind of stuck (and is slowly growing) whenever I do enter my password into the request prompts.

Which is also exactly what happens for me. It can't synchronize the calendars and they're marked as read only.

Info: Kubuntu 18.04, Thunderbird 52.9.1, exchange-calendar v4.0.0-beta5

[fprawits]

Did you leave the domain field empty when you changed to the username@domain naming scheme? I think I remember leaving it empty, however I am currently not at my machine to check my settings. My issues were solved once I changed my naming scheme and everything is working fine then. if this is still not the case for you, MartinRas' trick should work at least as a workaround for now.

[advancingu]

Does this issue continue to exist for anyone here?

If so, please provide output from the Thunderbird development console from the time where the calendar stopped being writeable. This helps fixing the issue

[Spurlos]

I have got affected by this issue lately (as of this week). For me the issue was that EWS settings jumped from Office365 to Exchange. Setting it back restored the write capability.

[neXussT]

I gave up. I need this for work, so I switched to using DavMail which handles exchange, and passes calendar events to a Thunderbird native format.

[vvombat]

FYI: I had the same issues. I had '%' as character in my password. Seems like it didn't like that at all. New passwort without %'s and everything is working as intended as far as I can tell.