Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

Can't open new tabs in Firefox from the command line on a Mac

  • 2 odgovora
  • 1 ima to težavo
  • 115 ogledov
  • Zadnji odgovor od cor-el

If I run

   /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org

when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command.

Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

If I run /Applications/Firefox.app/Contents/MacOS/firefox -new-tab https://www.mozilla.org when Firefox is already running, I get the error "A copy of Firefox is already open. Only one copy of Firefox can be open at a time." It is true that Firefox is already running, but what I am shooting for is getting a new tab in the already running instance, as the -new-tab flag indicates. I get this problem even if the already running instance was started with exactly the same command. Some of the flags at https://developer.mozilla.org/en-US/docs/Mozilla/Command_Line_Options explicitly say they open new tabs or windows within an existing instance of Firefox, such as -private-window, but I get the same behavior with those flags. What am I doing wrong?

Vsi odgovori (2)

It appears that as of five years ago this was a known bug with no intended fix: https://bugzilla.mozilla.org/show_bug.cgi?id=393645