On Tue, Jan 02, 2007 at 08:23:08PM +0100, Ingo Juergensmann <[EMAIL PROTECTED]> wrote: > On Tue, Jan 02, 2007 at 11:16:51AM +0100, Mike Hommey wrote: > > > > > Unfortunately I can't reproduce this at all on my PowerBook G4, and it > > > > doesn't look like anyone has stepped up to offer a "me too". Have you > > > > tried moving your .mozilla directory out of the way? > > > No, not my .mozilla directory. I'm somewhat uncertain about what directory > > > is actually used by iceweasel: .mozilla or .firefox. > > You can know that by checking the paths in ~/.mozilla/firefox/profiles.ini > > Ok, I've checked the following: > > - renaming ~/.mozilla/firefox: problem still exists > > - renaming ~/.mozilla: problem still exists > > - renaming ~/.firefox: iceweasel complains about still running instance > > - renaming ~/.firefox *and* ~/.mozilla: iceweasel starts, asking what to > import and opens browser window. It works. > > So, it seems to me that something has changed in the code between 2.0 and > 2.0.0.1 that messes something up with the paths. > In my ~/.mozilla/firefox/profiles.ini the Path is pointing to ~/.firefox > instead of ~/.mozilla/firefox/. Maybe it's reproducible now?
If you have ~/.mozilla/firefox/profiles.ini pointing to ~/.firefox, that means you are using your profile since version 1.0 at least, or even earlier. I can't remember exactly when they moved it. That also means it won't be reproducible until we know what in your ancient profile is causing the problem. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
