Open
Bug 367290
Opened 18 years ago
Updated 3 years ago
an idea for what to do when a profile is locked
Categories
(Toolkit :: Startup and Profile System, enhancement)
Tracking
()
UNCONFIRMED
People
(Reporter: j_gatarz, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Every so often, if my browser crashes, or computer crashes, when I start firefox back up it comes up without my bookmarks. This is because the profile has been locked, and firefox creates a new profile. I suggest that instead of simply creating a new profile, firefox instead imports the locked profile into the new profile, allowing the user to continue on as normal with all their settings and bookmarks.
Reproducible: Always
Steps to Reproduce:
1.
2.
3.
I think I already pressed commit, but I walked away and came back to my computer and this screen was here, so I'm committing just in case I forgot to and thought I did. Sorry if this is a duplicate.
Comment 2•18 years ago
|
||
Do you really see multiple profiles in the profile manager? Normally you should see this message: "Firefox is already running, but not responding.. etc.".
See: http://kb.mozillazine.org/Firefox_crashes
also: http://kb.mozillazine.org/Lost_bookmarks
Comment 3•17 years ago
|
||
I think I saw something similar with TRUNK. My seamonkey-1.1.6 died, but I haven't realized the process was still running. I was just about to test current suite build from TRUNK and the seamonkey shelscript spit out a message that no running windows were found and raised up the profile manager. It refused me to select the only, default profile. After a while I figured out a seamonkey process was still running, and after killing it and maybe removing a stale lock file I could continue using seamonkey. It would have been helpful if I were warned that maybe this was due to a lockfile and maybe a running, "hidden" process. I guess you could even run "ps -ef | grep $username" from seamonkey sheel wrapper and take proper action.
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•