Justin Wood (Callek) wrote:
Sounds like an adobe issue, can you try launching adobe reader outside of seamonkey after the install.... (even better if done with SeaMonkey closed) and accept the licence with the separately launched version, exit reader, then try visiting that website again.
It may not be easy : first I would have to convince Adobe that I had not signed the acceptance in the first place (which I now have), and that would probably mean uninstalling Adobe Reader again. Isn't the real question why Plugin-container sits there consuming all available CPU ? Philip Taylor _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
