Closed
Bug 203733
Opened 21 years ago
Closed 21 years ago
UI needed for breaking profile lock
Categories
(SeaMonkey :: Startup & Profiles, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 151188
People
(Reporter: dp+moz, Assigned: jag+mozilla)
Details
(Whiteboard: DUPEME)
Attachments
(1 file)
26.48 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030330 Phoenix/0.5 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4a) Gecko/20030330 Phoenix/0.5 One of our users was substantially inconvenienced by a lock left in her profile in her home directory, which is on a campus-wide NFS server. This means that as she roams from machine to machine, she will use the same profile in many places. The problem she encountered was with a lock which referenced a host other than the one she was using. Without hunting through her profile directory for the lock, there was no way to start up mozilla with her profile. Mozilla seems to check for invalid locks when on the local host, but when the lock is apparently on another host, for example: lock -> 129.146.89.213:21056, you will have problems. This might seem to be an uncommon scenario, but in an office environment which uses DHCP and dynamic IP addresses, it could be very likely if the power goes out. When hosts come back up, they might be assigned new addresses. The UI ought to do allow the user to break the lock if he/she is sure it is safe to do so. It might tell the user "The lock appears to be for process ID <xxxxx> on host <yyyyyy>. Please verify that it isn't in use. Click "Break Lock" if mozilla should proceed." or some such. Reproducible: Always Steps to Reproduce: 1. Start mozilla or phoenix on system A 2. kill -9 the process. Verify that it has left a 'lock' symlink in your profile 3. Go to system B. Try to start phoenix. 4. The profile manager should appear; try to use the profile. 5. It will tell you that the profile is in use.
This is something that NN4.7x got right, as per the screenshot I'm attaching.
Updated•21 years ago
|
Whiteboard: DUPEME
Comment 2•21 years ago
|
||
*** This bug has been marked as a duplicate of 151188 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•