Can't open in box; get internal error (server bug)
The latest version of Thunderbird crashes on me, according to the log I saw in my meanderings to find the answer when I shut down my computer. I click to send to Mozilla for a response and I've yet to get anything. I don't bother doing it anymore. In clicking on my emails just awhile ago, it's blank and down at botton I see my inbox, nothing happens and then lower right box opens and tells me that internal error (server bug) and to check server log. Overall this latest version of Thunderbird really sucks and even more so now as I can find NO answer on how to resolve this. I even downloaded and reinstalled and that did nothing. I tried to install a prior release/version and one cannot do that. After the 30+ years of using Mozilla and the lack of support, I just may say adios to Mozilla. SAD
Tutte le risposte (2)
Perhaps you might supply the crash id's instead of a rant about how your expectation have not been met. I can not offer more than a rant in return without facts to work with and that will help neither of us.
https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb#w_viewing-crash-reports
One thing I must point out is the dialog say "allow Mozilla to contact me" it make no suggestion that they will and very rarely is the email address used unless someone working on a bug needs additional information.
Note that without submitting the crash reports, what is critically important to you goes unnoticed in the scheme of things. It is only by getting crash reports and lots of them that resources can be prioritized to fix the ones causing the most trouble first. On your case with no reports, that crash will no get any priority unless other have the same issue and are sending their reports.
If you are interested the current top crash is a shut down hang with 148 crashes reported in the last 7 days. https://crash-stats.mozilla.com/topcrashers/?product=Thunderbird&version=60.5.1&process_type=any
These crashes are almost always caused by anti virus products so are a perennial issue. But without a crash id I can not comment on your crash specifically.
