Am 31.01.2013 10:43, schrieb Rob: > Matthias Kahlert > <imightreadmailtothisadressorimightnotbutinanycasesendmenos...@kahlert.at> > wrote: >> Am 30.01.2013 17:11, schrieb Roger Fink: >>> Matthias Kahlert wrote:
>> 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. > Yes, but that is a very tedious task, so I hoped someone might know the solution. After some more testing (the new profile that worked yesterday has again ceased to do so today) it seems that pluginreg.dat might be the culprit, which doesn't even sound far-fetched with hindsight... -- Matthias _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
