All this button does is open a new window within the currently running browser / profile combo. We should hide this button until the feature works. Tested on Windows w/Nightly 55.
Summary: About:profiles 'launch profile in new browser" doesn't work → About:profiles "launch profile in new browser" doesn't work
This is basically dead code until such time as someone decides to revive it, given bug 1239848, to which all issues with the existing implementation have so far been duped.
Component: General → Startup and Profile System
Product: Firefox → Toolkit
Um, please DON'T hide it. The button does actually work so long as you are clicking them from a no-remote started instance.
Actually it works exactly how it should. It opens the selected profile in a new instance. We should not remove about:profiles and if there are issues, we can simply fix them.
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → INVALID
(In reply to Andrea Marchesini [:baku] from comment #3) > Actually it works exactly how it should. It opens the selected profile in a > new instance. > We should not remove about:profiles and if there are issues, we can simply > fix them. Not on Windows, it just opens a new window int he same instance, using the currently open profile.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Jim, as mentioned in comment #2, if you add -no-remote to your Firefox shortcut, the Launch profile in new browser button works as expected. This is not all that surprising, you cannot manually open another profile (with the -p "profilename") option without -no-remote either because Firefox is already running. Perhaps there should be a check with a pop up message.
Can the code be revised to always use -no-remote (express or implied) on new instances? For example, I start Firefox normally in my default profile. I then use a desktop shortcut to start Firefox -P "profile2" -no-remote. In about:profiles in the "profile2" instance, I can launch "profile3" with no conflict (-no-remote doesn't appear on the command line but is somehow inherited?). Then in about:profiles in the "profile3" instance, I can launch "profile4" with no conflict (-no-remote doesn't appear on the command line). Since all four profiles operate independently at that point, I think it should be possible to achieve this effect from the original instance. Somehow. ;-)
From a Sumo perspective, I think it’s safe to say about:profiles comes in handy and we need this feature/button to work in any version without mentioning any tricks or bugs. Adding -no-remote would be required to make this work in FF release allright, but appears to break recognition of the default browser (or rather: profile) for links clicked in Thunderbird emails even when FF is already open and running the default profile. See https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles/discuss/7232.
You need to log in before you can comment on or make changes to this bug.