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. Please ask a new question if you need help.

Why does TB do mailto differently depending on state of FF that started it?

  • 1 reply
  • 1 has this problem
  • 3 views
  • Last reply by pb

pb
pb
more options

win 7 64 bit, TB 38.5.1

This is a followup to

https://support.mozilla.org/en-US/questions/1108691

and

https://support.mozilla.org/en-US/questions/1108660

When I do an "email link" or click a "malto" in FF, if TB is already running, sometimes I get a mail compose window as I want, and sometimes I get the TB profile manager, which of course does not allow me to select the currently runnin TB profile, which is the one that I of course want.

The only difference between the two scenarios is whether FF was started with the "-no-remote" option.

I have established that TB is being started with the identical command line in both cases, so I am at a loss to understand why it behaves differently depending on how the FF that invokes it was started.

How does TB decide whether it wants to invoke the profile manager when it is already running?

For example, is there some registry value or ENV variable that FF or the OS might have set that it would look at other than the command line to start it?

The exact same TB executable is being invoked also.

Thanks.

win 7 64 bit, TB 38.5.1 This is a followup to https://support.mozilla.org/en-US/questions/1108691 and https://support.mozilla.org/en-US/questions/1108660 When I do an "email link" or click a "malto" in FF, if TB is already running, sometimes I get a mail compose window as I want, and sometimes I get the TB profile manager, which of course does not allow me to select the currently runnin TB profile, which is the one that I of course want. The only difference between the two scenarios is whether FF was started with the "-no-remote" option. I have established that TB is being started with the identical command line in both cases, so I am at a loss to understand why it behaves differently depending on how the FF that invokes it was started. How does TB decide whether it wants to invoke the profile manager when it is already running? For example, is there some registry value or ENV variable that FF or the OS might have set that it would look at other than the command line to start it? The exact same TB executable is being invoked also. Thanks.

Chosen solution

The problem is that FF sets the env variable MOZ_NO_REMOTE.

See https://support.mozilla.org/en-US/questions/1108691 solution for details.

Read this answer in context 👍 0

All Replies (1)

pb
pb Question owner
more options

Chosen Solution

The problem is that FF sets the env variable MOZ_NO_REMOTE.

See https://support.mozilla.org/en-US/questions/1108691 solution for details.