Firefox on Windows ignores .parentlock and on Linux parent.lock is ignored.

NEW
Unassigned

Status

()

P5
enhancement
10 years ago
8 years ago

People

(Reporter: nilsjansen, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.5) Gecko/2008121622 Ubuntu/8.10 (intrepid) Firefox/3.0.5

On Ubuntu 8.10 Firefox 3.05 starts with a Profile which is currently in use by Windows and vice versa. They should not use different Lockfiles (.parentlock and parent.lock) so one Profile can be used from both OS without risk of dataloss.

Reproducible: Always

Steps to Reproduce:
1. Run firefox on windows and save the profile folder on a samba-share.
2. Run firefox on eg ubuntu and use this profile on the samba-share.
Actual Results:  
2 firefox are running on one profile, which should not happen simultaneously.

Expected Results:  
Windows, Linux and MacOS should all use one lockfile-name.

Updated

10 years ago
Component: General → Startup and Profile System
OS: Windows XP → All
Product: Firefox → Toolkit
QA Contact: general → startup
Hardware: x86 → All

Comment 1

10 years ago
Using the same profile data on Windows and Linux is very edge-case. I'm not inclined to make the locking code more complicated for this case, because it's not just the lock file that differs, it's the method of locking.

What backing filesystem are you sharing with? NFS? Do Windows locking primitives work on NFS mounts?
Severity: normal → enhancement
Priority: -- → P5

Comment 2

10 years ago
For what it's worth, I can reproduce this locally by loading up WinXP in a VirtualBox on Kubuntu and creating an emulated network share of a profile dir from the host.
Status: UNCONFIRMED → NEW
Ever confirmed: true
You need to log in before you can comment on or make changes to this bug.