Closed Bug 228064 Opened 21 years ago Closed 21 years ago

Account locked after a system crash

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 151188

People

(Reporter: matthieu.moy, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030701
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.4) Gecko/20030701

When mozilla is started, a lock file is created in ~/.mozilla/user/xxx/lock to
avoid multiple sessions.

The problem is that after a system crash, this file is still there, and when
starting mozilla, the user is prompted for another account.

The workaround is to remove the lock file manually, but for a newbie, this is a
*really* complex task :

* Guess that you have to delete this precise file
* Find it in .mozilla, which is a hidden directory

Before displaying this profile selection box, I think it would be really better
to have a small dialog box :

"This mozilla profile seems to be already in use. Most probably you have another
Mozilla application running, and you should use it or close it.

However, follwing a system crash, it may happen that the profile remains locked
forever. If so, say 'yes' to the following question :

Do you want to force unlocking the profile XXX ?

[ Yes ] [ No ]
".

Then, clicking "Yes" would delete the lock file and start Mozilla normally, and
clicking "No" would continue with the current behavior.

Reproducible: Always

Steps to Reproduce:
1. Launch a Mozilla session
2. Simulate a system crash
3. Launch another Mozilla session

Actual Results:  
The user account is lock forever if you are not a unix guru !

Expected Results:  
Offer the user to unlock the account.
This looks like bug 151188, but feel free to reopen if you have a specific
reason to disagree.

*** This bug has been marked as a duplicate of 151188 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.