Closed
Bug 225157
Opened 21 years ago
Closed 21 years ago
Option to remove stale lockfile in .mozilla profile directory
Categories
(SeaMonkey :: Startup & Profiles, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 151188
People
(Reporter: etnoy, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624
If, for example I (for any apparent reason) need to terminate the mozilla app
without letting it to shutdown gracefully, it will leave a stale lockfile in
~\.mozilla\<profilename>\<garbage>\lock. When Mozilla later on starts, it asks
for a profile to start with, but as the lockfile being stale, it won't start the
browser.
It should be possible to have a button associated to a profile entry, saying
"Remobe lock", after the program has checked the process ID in the lockfile.
That would save me (and others) from going to a shell, entering the mozilla
directory and remove a lockfile. For newbie users that would be a nightmare, and
I sure think that they'll be running with about 10 or 20 profiles at once,
because they can't get the older ones to run.
Reproducible: Always
Steps to Reproduce:
1.Start Mozilla
2.Kill -9 Mozilla
3.Start Mozilla
Actual Results:
It asked for "Select Profile"
Expected Results:
Given me a button, saying "Remove the @£$€@¥ lockfile"
Comment 1•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
•