How to stop Thunderbird crashing immediately upon loading.
We use Thunderbird in the office, with installs on half a dozen workstations, each set to run automatic updates. This morning, on one workstation loads, and immediately crashes. A dozen or so crash reports will have been submitted this morning from that machine. Safe Mode did not make any difference.
On my (working) copy the version is 60.5.0 (32-bit). I assume that the version is the same on the broken machine.
Any thoughts on how to break the re-boot cycle would be appreciated.
Crash ID: bp-9b23d053-8612-4696-95c0-e8afb0190206
P.S. In the time it took to type this another workstation has started doing the same.
All Replies (5)
I've just run a fourth workstation and Thunderbird successfully installed an update to 60.5.0. Has this update broken the two other copies?
It looks to be a permission issue. If I run TB as administrator it does appear to work on these machines. The problem being I don't want all users to have full admin rights on their machines as this is opens up other security issues.
Ok, so the crashing is still happening. It appears to relate to the 'local folders' which are actually on a network drive. This is done because we actually share the local folders, something we've done successfully for about 15 years. Now however on these two workstations certain actions on the local folders cause the crash. TB will then continually restart & crash until told to stop. Re-starting as administrator will break the cycle as the local folders are not available, allowing the user to set their inbox as the active folder and they can then restart as a normal user and the shared local folders will again be available to them.
So I'm still looking for a long term solution to this which wasn't a problem until v60.5
Based on what you have said. A couple of questions but nothing helpful probably.
Are the permissions for the network share set using a UNC or a drive letter? Changes in the release notes mention changes from drive letter to UNC paths, this might be related? Just a guess.
It is a mapped network drive, so yes linked to the drive letter. This might be part of it, but I've not changed the settings on the other workstations and they continue to work as they have always done.
Indeed for one user I've not changed their network permissions and it has not been affected (so far at least).