1394563 - Firefox.exe -silent -setDefaultBrowser hangs infinitely

Status: RESOLVED WONTFIX

(Firefox :: Shell Integration, defect)

Description

[wdo362]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20170411115307

Steps to reproduce:

When trying to rollout ESR 52 the call in our script "Firefox.exe -silent -setDefaultBrowser" hangs infinitely when called under Windows SYSTEM account.


Actual results:

The call hangs infinitely when called under Windows SYSTEM account. We verified that it does not hang when called under Administrator acccount which is not an option for deployment via GPO. We also verified that it works as expected with previous ESR release 45. For workaround we found that helper.exe with /SetAsDefaultAppGlobal still works as expected.


Expected results:

Call should not hang infinitely as it was with previous versions.

Comment 1

[wdo362]

Forget to mention platform is Windows 7 SP1 x86

Comment 2

[Robert Strong (they/them - no direct email)]

iirc this is due to another command line handler (possibly something to do with telemetry) and not the shell integration code.

chutten, do you know anything about command line handling that was added for telemetry?

Comment 3

[Chris H-C :chutten]

'fraid not. Was there something added for telemetry? (+Cc :gfritzsche, :Dexter for comment)

Comment 4

[Robert Strong (they/them - no direct email)]

Someone brought it up on irc awhile back and I *thought* it was in regards to telemetry but I might very well have misremembered the component

Comment 5

[Alessio Placitelli [:Dexter]]

(In reply to Robert Strong [:rstrong] (use needinfo to contact me) from comment #2)
> iirc this is due to another command line handler (possibly something to do
> with telemetry) and not the shell integration code.
> chutten, do you know anything about command line handling that was added for
> telemetry?

To my knowledge nothing like that was added.

However, something similar was triggered by bug 1358907 landing on m-c: was fixed by bug 1379831. However that stuff landed on 56 and we're talking about ESR52 here, so that might be a completely different problem.

Comment 6

[Robert Strong (they/them - no direct email)]

Thanks, the bug that I thought this might be caused by is bug 1379831 which is unrelated.

The cleaner method for deployments is the one you discovered and we're not going to try to address this when there is a workaround that is actually a better method.