Open
Bug 712905
Opened 13 years ago
Updated 2 years ago
no-remote conflicts with ProfileManager (running multiple profiles)
Categories
(Toolkit :: Startup and Profile System, defect)
Tracking
()
NEW
People
(Reporter: bugs, Unassigned)
References
Details
(Keywords: regression)
User Agent: Mozilla/5.0 (Ubuntu; X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 Build ID: 20111219070828 Steps to reproduce: Upgraded from 8 to 9. Launching firefox with : firefox -ProfileManager -no-remote opening URL in one of running instances: firefox -P browse -remote "openURL(http://www.mozilla.com)" Actual results: Error: No running window found Apparently -no-remote now disables remote interface completly, however Profile manager can't be started without -no-remote if there is another profile running. Expected results: URL should have been opened in running browser with profile "browse".
Updated•12 years ago
|
Component: General → Startup and Profile System
Keywords: regression
Product: Firefox → Toolkit
QA Contact: general → startup
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•12 years ago
|
||
I think that this is probably "not a bug", but I for one would very much like to see the design corrected. Web developers such as myself often want to run multiple profiles -- one for work, and one for browsing and perhaps another with no plugins for speed testing. As it is, I have succumbed to the ability to open any profile I want with a single click via this command line: google-chrome --user-data-dir=/home/slindsey/.config/chrome-browse/ - or - google-chrome --user-data-dir=/home/slindsey/.config/chrome-work/ There doesn't seem to be an equivalent in Firefox.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•