Matthias Kahlert <imightreadmailtothisadressorimightnotbutinanycasesendmenos...@kahlert.at> wrote: > Am 30.01.2013 17:11, schrieb Roger Fink: >> Matthias Kahlert wrote: > > >>> On other user-profiles on the same pc everything is fine (and it also >>> used to work with older versions of jre), so I rule out the seamonkey >>> and the java installation. The problem must be somewhere in the >>> profile. >>> >>> Any ideas? (renaming blocklist.xml as per another posting didn't help) >> >> fwiw, I have the same problem in Seamonkey 15.1 (but not FF 18.0.1). On some >> sites the override routine works the way it was intended, on others it >> doesn't. My assumption was that the problem was site-related, but the way >> you describe it, maybe not. > > It must be in some way profile related. If I delete the old profile and > create a new one from scratch it works again, even if I copy the old > prefs.js to the new profile. > > But I'm not too happy with this "solution", as I have several affected > users and they would still loose lots of information (saved passwords, > bookmarks, history, etc...)
Try to find which of the other files in the profile is the culprit. You can start by clearing the disk cache (and/or turning it off), then try files like places.sqlite cookies.sqlite panacea.dat etc. When you find it is caused by places.sqlite there is a middle way where you lose all your history but not your bookmarks, which may be more acceptable: when you remove places.sqlite it will import the last backed up bookmarks. When a problem can be worked around by using a new profile, it should always be possible to determine what part of the profile is the cause. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
