Microsoft Edge Stable – Crash on First Launch with New Profile (Ubuntu 24.04)

[jornodberg]

Recent versions of Microsoft Edge Stable for Linux fail to start on Ubuntu 24.04 when no existing Edge profile is present. The browser terminates immediately on first launch and produces a trap int3 event. The issue is reproducible across multiple systems and affects at minimum the last 3–4 Stable releases.

Impact
Edge cannot be used on newly provisioned Ubuntu 24.04 systems
Affects enterprise deployments with fresh user profiles or ephemeral home directories
Breaks automated onboarding, VDI environments, and standard imaging workflows
Requires manual downgrade‑and‑upgrade workaround to restore functionality

This constitutes a blocking issue for Linux‑based enterprise environments.

Environment
OS: Ubuntu 24.04 LTS (fully updated)
Installation: Official Microsoft APT repository
Condition: No existing Edge profile (~/.config/microsoft-edge and ~/.cache/microsoft-edge absent)

Steps to Reproduce
Remove any existing Edge profile directories.
Install the latest Microsoft Edge Stable build.
Launch Edge.

Actual Result
Edge crashes immediately with no UI displayed.
dmesg logs show:

traps: msedge[PID] trap int3 ... error:0 in msedge[…]

--no-sandbox does not mitigate the issue.

Expected Result
Edge should initialize a new profile and launch normally.

Workaround
The following sequence restores functionality:

Install an older Stable version (e.g., 144.0.3719.115).
Launch Edge and allow profile initialization and sync.
Upgrade to the latest Stable version.
Edge now launches successfully.

This indicates that current Stable builds fail during initial profile creation, but operate normally when using a profile generated by an older version.

Please investigate the regression in the profile‑initialization path for Linux in recent Stable builds. We can provide additional diagnostic data (logs, traces, reproducible environment) upon request.