NFN Smith wrote:
A Williams wrote:
Firefox (the newest level) is unaffected. I think I am going to try
exporting my SM profile into FF until this gets resolved.
Have you tried launching Seamonkey in safe mode?
Typically, this kind of problem is related to something in your user
profile that's amiss. Extensions are a frequent culprit, and a similar
troubleshooting approach is to disable all your extensions, and then
reenable one by one, until you find which one is causing problems.
However, sometimes it can happen that there's something else not quite
right, and it's generally some setting in your prefs.js file. If that's
the case, your better bet would be to start over with a new user profile
in Seamonkey.
If you export your data to Firefox, you might find that you have similar
problems there. If you do, then it's a pretty solid indication that
your problem is related to the profile, not to Seamonkey.
Smith
I renamed the original profile xxxxxxxx.screwed
I renamed the backup profile xxxxxxxx.backup
I created a new xxxxxxxx.default
(xxxxxxx is the usual random string)
Then I copied "screwed" to "default" with the idea of replacing files
from "backup" one by one until things worked. a "diff" on "prefs.js"
had already shown nothing significant.
Copying was done by going to "screwed" and then:
tar cf - . | (cd ../xxxxxxx.default ; tar xf - )
as my normal id, not as root
It worked first time and I do not have a clue why - in particular
because rebooting had not helped at all.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
