Este site está com funcionalidades limitadas enquanto realizamos manutenção para melhorar sua experiência de uso. Se nenhum artigo resolver seu problema e você quiser fazer uma pergunta, nossa comunidade de suporte pode te ajudar em @FirefoxSupport no Twitter e /r/firefox no Reddit.

Pesquisar no site de suporte

Evite golpes de suporte. Nunca pedimos que você ligue ou envie uma mensagem de texto para um número de telefone, ou compartilhe informações pessoais. Denuncie atividades suspeitas usando a opção “Denunciar abuso”.

Saiba mais

Esta discussão foi arquivada. Faça uma nova pergunta se precisa de ajuda.

Firefox 68 Mac, can't start w/profile from command line

  • 7 respostas
  • 2 têm este problema
  • 1 exibição
  • Última resposta de user1903660

more options

Long-time Firefox user with several profiles defined via ProfileManager. Have several AppleScript apps that start firefox-bin with "-P profilename" to start Firefox with the named profile (see <https://spf13.com/post/managing-multiple-firefox-profiles-in-os-x/> for a description of how this is set up). They no longer work. Starting the profiles from a shell prompt also does not seem to work, at best it opens a new Firefox window in each currently-open Firefox profile. Have tried -P with profile name (profile name quoted), --profile with path to profile's "Root Directory", --profile with path to profile's "Local Directory", pathnames quoted if necessary; all of the above with --new-instance. No joy. What am I missing?

Long-time Firefox user with several profiles defined via ProfileManager. Have several AppleScript apps that start firefox-bin with "-P profilename" to start Firefox with the named profile (see <https://spf13.com/post/managing-multiple-firefox-profiles-in-os-x/> for a description of how this is set up). They no longer work. Starting the profiles from a shell prompt also does not seem to work, at best it opens a new Firefox window in each currently-open Firefox profile. Have tried -P with profile name (profile name quoted), --profile with path to profile's "Root Directory", --profile with path to profile's "Local Directory", pathnames quoted if necessary; all of the above with --new-instance. No joy. What am I missing?

Solução escolhida

There were a few changes here recently, you might want to try `firefox -P profile -no-remote`

Ler esta resposta 👍 2

Todas as respostas (7)

more options

Additional information: One way profiles do work: about:profiles, and "Launch profile in new browser". So I think my profile definitions are in order, it's getting them going via firefox-bin command-line arguments that is broken.

more options

Does it work if you use firefox -P "profile" instead of firefox-bin ?

more options

It works the same way: I get a new window for each in-use profile.

more options

Running this from the AppleScript again, I am reminded that it put up a dialog, "The command exited with a non-zero status", and that if I echo $? after trying the same command from a shell prompt the status is 1. (I also get the new window open under the in-use profile, as opposed to the profile I wanted to launch).

more options

Solução escolhida

There were a few changes here recently, you might want to try `firefox -P profile -no-remote`

more options

That seems to work well enough to get the AppleScript method going again. Thanks! (Might be nice if it were in the usage message.)

more options

I'm having the same issue. I have two profiles (work and personal) which I usually leave open; the -P flag seems to be ignored and instead any URL I pass in is opened in both profiles. `-no-remote` doesn't work for me... it either brings up an error complaining that the profile is already open, or it just hangs. All I want is some way to open a link in a specific profile (e.g. from an Alfred shortcut).