Important Notice: We're experiencing email notification issues. If you've posted a question in the community forums recently, please check your profile manually for responses while we're working to fix this.

On Monday the 3rd of March, around 5pm UTC (9am PT) users may experience a brief period of downtime while one of our underlying services is under maintenance.

Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Jei jums reikia pagalbos, užduokite naują klausimą.

bug? 69.0.3497.81 -ProfileManager -no-remote

  • 4 replies
  • 1 has this problem
  • 3 views
  • Paskiausią atsakymą parašė xoferif

xoferif
xoferif
more options

Is 69.0.3497.81 profilemanager bugged?

To open ProfileManager from a windows shortcut, the 'target' is "C:\Program Files\Mozilla Firefox\firefox.exe" -P -no-remote

With FF not running: -P opens ProfileManger -P "profilename" opens ProfileManger

With FF running: -P opens a new instance. -no-remote -P opens ProfileManager -no-remote -P "notopenedprofilename" opens ProfileManger -no-remote -P "openedprofilename" says FF is not responding

FF is not not responding. Bug?

Is 69.0.3497.81 profilemanager bugged? To open ProfileManager from a windows shortcut, the 'target' is "C:\Program Files\Mozilla Firefox\firefox.exe" -P -no-remote With FF not running: -P opens ProfileManger -P "profilename" opens ProfileManger With FF running: -P opens a new instance. -no-remote -P opens ProfileManager -no-remote -P "notopenedprofilename" opens ProfileManger -no-remote -P "openedprofilename" says FF is not responding FF is not not responding. Bug?

All Replies (4)

xoferif
xoferif Klausimą uždavęs asmuo
more options

Xoferif said 

Is 69.0.3497.81 profilemanager bugged?

To open ProfileManager from a windows shortcut, the 'target' is 
"C:\Program Files\Mozilla Firefox\firefox.exe" -P -no-remote

With FF not running: 
-P opens ProfileManger
-P "profilename" opens ProfileManger

With FF running: 
-P opens a new instance.
-no-remote -P opens ProfileManager
-no-remote -P "notopenedprofilename" opens ProfileManger
-no-remote -P "openedprofilename" says FF is not responding

FF is not not responding.  Bug?


This forum mangles the posters text... maybe that's whats wrong with the code?

Modified by cor-el

cor-el
cor-el
  • Top 25 Contributor
  • Moderator
more options

In the case that Firefox is running, was Firefox with or without the -no-remote switch ?

xoferif
xoferif Klausimą uždavęs asmuo
more options

Initially FF was run with only -p <profile name>

xoferif
xoferif Klausimą uždavęs asmuo
more options

I closed all the windows, then used only -no-remote to open both profiles. It worked.