2004921 - [intermittent] Sometimes the client does not open after a successful authentication

Status: RESOLVED DUPLICATE of bug 2006637

(Firefox Enterprise :: Client, defect)

Description

[Alexandru Trif, Desktop Test Engineering [:atrif]]

Attachment: no_client.mov

Found in

• Firefox Enterprise 147.0a1 - Build ID: 20251205074101

Affected versions

• Firefox Enterprise 147.0a1 - 20251205074101

Tested platforms

• Affected platforms: macOS 26, Windows 11, Ubuntu 24
• Unaffected platforms: none

Preconditions

• install Firefox Enterprise from here

Steps to reproduce

1. Open the Authentication screen and log in.
2. Sign out and repeat step 1

Expected result

• The client is displayed after each successful authentication.

Actual result

• Sometimes the client is not open.

Regression range

• The issue is very intermittent. A regression range is not so possbile without proper steps.

Additional info

• Attached a screen recording.
• Windows 11 screen recording from sbadau: link

Comment 1

[:gerard-majax]

Can you confirm it happens with builds from https://github.com/mozilla/enterprise-firefox/actions/runs/19955143103 but not those from https://github.com/mozilla/enterprise-firefox/actions/runs/19954422050 ?

Comment 2

[Simona Badau, Desktop QA]

(In reply to :gerard-majax from comment #1)

Can you confirm it happens with builds from https://github.com/mozilla/enterprise-firefox/actions/runs/19955143103 but not those from https://github.com/mozilla/enterprise-firefox/actions/runs/19954422050 ?

I can reproduce this issue with builds from both repositories - tested using msi installers on Windows 11. Not sure if it’s worth mentioning, but for me, roughly every third attempt to launch Firefox Enterprise fails.

Comment 3

[:gerard-majax]

Thanks, it's weird because it is a path tested with our tests 😭

Comment 4

[:gerard-majax]

Can you reproduce running from command line with MOZ_LOG=console:5 env ? If so sharing the output may help

Comment 5

[Simona Badau, Desktop QA]

Attachment: mozlogs.zip

(In reply to :gerard-majax from comment #4)

Can you reproduce running from command line with MOZ_LOG=console:5 env ? If so sharing the output may help

Yes, I attached the logs that were generated.

Comment 6

[:gerard-majax]

Not sure how you collected, but it's truncated so it's missing the part we need :(

Comment 7

[:gerard-majax]

When you are at it also set RUST_LOG=felt=trace just in case

Comment 8

[Simona Badau, Desktop QA]

Attachment: mozlogs.zip with RUST_LOG=felt=trace set

(In reply to :gerard-majax from comment #7)

When you are at it also set RUST_LOG=felt=trace just in case

Set it, please see the generated logs.

Comment 9

[:gerard-majax]

Simona, do you think you could give a try to a build from https://github.com/mozilla/enterprise-firefox/actions/runs/20330519215 (once they are completed, in a few minutes) for this bug and bug 2006637 ?

Comment 10

[Simona Badau, Desktop QA]

(In reply to :gerard-majax from comment #9)

Simona, do you think you could give a try to a build from https://github.com/mozilla/enterprise-firefox/actions/runs/20330519215 (once they are completed, in a few minutes) for this bug and bug 2006637 ?

I'm still able to reproduce this issue - I captured a screen recording here.

As for bug 2006637, I can also reproduce it when opening Firefox Enterprise first from PowerShell and then selecting Sign out from the toolbar button. As in the scenario described in this bug, on the third attempt to open Firefox Enterprise it fails (different logs, but the same steps).

Comment 11

[:gerard-majax]

So it's consistent with what I saw, and I dont think you were experiencing a crash at startup

Comment 12

[:gerard-majax]

Simona, do you still repro this one with the builds I shared on bug 2006637 ?

Comment 13

[Simona Badau, Desktop QA]

(In reply to :gerard-majax from comment #12)

Simona, do you still repro this one with the builds I shared on bug 2006637 ?

No, with the builds from Comments 21 and 22 in Bug 2006637, I can no longer reproduce this issue.

Comment 14

[:gerard-majax]

ok sop we can safely assert it's a dupe now and that we have a fix