Closed Bug 634114 Opened 15 years ago Closed 14 years ago

Don't start with -no-remote by default

Categories

(Testing Graveyard :: ProfileManager, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Unassigned)

Details

Profile Manager currently always starts an app with the -no-remote parameter. However, this causes some problems. E.g.: If no Firefox is running and one is launched via Profile Manager (which passes -no-remote), then url launching from e.g., Thunderbird will be broken (you'll see the "Firefox is already running" error). To solve this, move the -no-remote parameter to an option and exclude it by default.
I have a fix for this, but it can potentially create other confusion, since if you already have Firefox running on one profile, and wish to launch another, you have to remember to tick the '-no-remote' option, otherwise you'll get an error when launching Firefox. It would be nice to automatically add -no-remote if any other instance if Firefox is running. But we can't easily detect this without adding a new xpcom component. However, we could iterate through the profiles, and if any are locked, assume that another instance is running and add -no-remote automatically. This would only fail if someone had an orphaned profile lock on their machine.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
This isnt't really a dupe of bug 441422, since that's a statement of issues with Firefox functionality, and this bug is related to how the standalone Profile Manager (see: https://developer.mozilla.org/en/Profile_Manager) deals with that. I've implemented the fix I described in Comment #1; will see if any beta users run into problems with this.
Resolution: DUPLICATE → FIXED
I'd file another bug for this, but I don't see how to set the Component to ProfileManager. Pursuant to the fix in Bug 625044, I think the profile manger could use an option that would unlock all profiles, thus making it easier to resolve the orphaned profile lock failcase mentioned in the bug. And, while I'm here, if there is a precompiled Windows version, could someone email me a link? I'd be glad to help with testing.
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.