User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:126.96.36.199) Gecko/20060728 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:184.108.40.206) Gecko/20060728 Firefox/220.127.116.11 Firefox creates .parentlock in the profile directory of the user when started. However that file remains until deleted by the user and prevents the user from starting Firefox on another client. The error message follows. Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. Reproducible: Always Steps to Reproduce: 1. Create a user in Workgroup Manager (OS X Server 10.4.7 PPC). 2. Create a home directory on that server shared through AFP. 3. Login as that user on a client machine (OS X 10.4.7 Intel). 4. Start Firefox. 5. Close Firefox. 6. Log out. 7. Log into another client. 8. Try to start Firefox. Actual Results: I get the error I typed above. I get the same error but with a slightly different wording when both clients are running Firefox 2.0 Beta 2. However, it works fine when both are running Firefox 3.0a1 (20060905). Expected Results: I assume that it's supposed to delete .parentlock when it closes.
If you could find out when it was fixed in Firefox 3 then we might be able to pinpoint which patch it was that fixed it. (Although at this point the chances of getting that patch into Firefox 2 are pretty slim.) Older builds are available on http://archive.mozilla.org/pub/firefox/nightly.
Version: unspecified → 2.0 Branch
Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:18.104.22.168) Gecko/20060909 Firefox/22.214.171.124 and 126.96.36.199. All the profiles have .parentlock in them, whether Fx is running or not. Some people have, indeed, problems with the file in different OSes, but I never did.
On AFS, this file makes Fx refuse to start. Maybe bug 318801 should depend on this one.
Oh, sorry. Didn't read well. Probably the two bugs are the same.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 318801
You need to log in before you can comment on or make changes to this bug.