Open Bug 1592743 Opened 5 years ago Updated 2 years ago

ESR68.2.0 on one Win10 laptop and user won't launch

Categories

(Toolkit :: Startup and Profile System, defect, P3)

Product:
Toolkit
Component:
Startup and Profile System
Type:
defect

Tracking

()

Status:
UNCONFIRMED

People

(Reporter: jmp242, Unassigned)

References

(Blocks 1 open bug)

Details

Mike Kaply asked me to open a bug with the issue from the mailing list - so duplicated thread info here:

I have a somewhat odd issue with a Lenovo X1 Carbon 6th gen running Windows 10 1809 LTSC and just deployed 68.2.0ESR over 60.8.0ESR. This laptop is a "kiosk" for us, which means it autologins to a useraccount, vaclab. This is a domain account. This laptop was just out for repair and had the m.2SSD and motherboard replaced. We just re-imaged it with our image just prior to the 68.2.0 deployment, so it hadn't been used or had Firefox launched before the upgrade.

As the vaclab account, Firefox won't run. It will launch 2 firefox.exe processes for about 30 seconds and they will either then trigger Mozilla crash reporter, or just exit silently.

As admin users on the laptop, we can launch Firefox just fine. Because of the specific "kiosk" configuration, we are not allowed by GPO to log in as other regular users. However, on other Win10 instances that are Kiosks or regular users we do not see the issue. Just on this one X1, and with this one user.

The Crash Details for the user show a crash in an ESET plugin - we use ESET Endpoint Security v7.1.something - however, it's a system level config, and doesn't crash for the admin users - we tried 2 different user accounts. We also tried "pausing" ESET live protection, no change. We looked at ESET live logs and ESET showed nothing.

To debug, we tried deleting C:\Users\vaclab\appdata\xxxx.mozilla (local, local low, and roaming). No change. I tried using Windows profile manager as and admin to remove the vaclab profile and re-create. No change. I tried as vaclab running firefox -profilemanager - weird XUL crash. Tested running same command as the admin users, worked fine, though showed 2 profiles?

I'm at either re-imaging the laptop AGAIN, or throwing it out for a different X1 carbon - but does anyone have ANY ideas about this failing just for the particular user?

As a test, we uninstalled ESR 68.2.0 and reinstalled ESR 60.8.0, and that worked perfectly for the vaclab account. We re-ran the upgrade (silent install for ESR 68.2.0) and it again broke. I don't think this is related to ESET, but something different in ESR 68.2.0.

One other wrinkle is we turn UAC off via GPO and use traditional Windows permissions and Dell Privilege Manager for targetted elevations in limited cases, but that agent is running on the computers.

James Pulver
CLASSE Computer Group
Cornell University

Blocks: 1564546

Mike, I think you said on Slack you had a little more information that what's here, can you add it? Do you have any idea on where this should be triaged to? Is it policy or something else?

Flags: needinfo?(mozilla)

We think this is DLL injection or launcher process.

Should be triaged the same as bug 1564546

Flags: needinfo?(mozilla)
Priority: -- → P3

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: General → Startup and Profile System
Product: Firefox → Toolkit
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.