David E. Ross wrote:
On 12/18/2017 1:17 PM, Henrik37 wrote:
Oops - after a complete reboot, SM 2.49.1 does appear to have solved the
problem.
Does anyone have any idea or explanation about what has been going on?
Oops again - SM 2.49.1 DIDN'T fix my problem after all. More ideas sought.
Have you tried starting SeaMonkey in Safe Mode?
I receive the same error messages in SeaMonkey Safe Mode.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
