Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

--no-remote (and --new-instance) prevents duplicate instances of same profile, not just different ones

  • אין תגובות
  • 2 have this problem
  • 16 views
more options

It's understood that --no-remote (and --new-instance, though with slightly different abilities) will allow the -P {profile name} to function when a previous profile is already up and running.

That works as expected, thus this works (tested under Linux Mint/zsh)

---> firefox --no-remote -P Dwight {............} and ---> firefox --no-remote -P Schmidlapp {............} (with both running).

HOWEVER,

When profile Dwight is running, and I try to execute another run at the same time of a Dwight profile, I'll get the same old error message (attached) on the second run.

It's understood that --no-remote (and --new-instance, though with slightly different abilities) will allow the -P {profile name} to function when a previous profile is already up and running. That works as expected, thus this works (tested under Linux Mint/zsh) ---> firefox --no-remote -P Dwight {............} and ---> firefox --no-remote -P Schmidlapp {............} (with both running). '''''HOWEVER,''''' When profile Dwight is running, and I try to execute '''''another''''' run at the same time of a Dwight profile, I'll get the same old error message (attached) on the second run.
צילומי מסך מצורפים