Fail to open microsoft edge after updating wsl

[edmondium]

Windows Version

Microsoft Windows [Version 10.0.22631.2792]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 23.10

Other Software

No response

Repro Steps

before running wsl, i update it first by executing wsl --update.

Expected Behavior

microsoft edge runs normally, blender should run normally too.

Actual Behavior

edmondium@LAPTOP-1Q9H40K6:~$ microsoft-edge
[717:717:1212/080052.779472:ERROR:ozone_platform_x11.cc(239)] Missing X server or $DISPLAY
[717:717:1212/080052.779577:ERROR:env.cc(257)] The platform failed to initialize. Exiting.

edmondium@LAPTOP-1Q9H40K6:~$ blender
GHOST: failed to initialize display for back-end(s): ['X11']
GHOST: unable to initialize, exiting!

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• WSL failed to start after update Windows (#4939), similarity score: 0.77
• WSL not working after windows update (#10185), similarity score: 0.77

Closed similar issues:

• Can't launch wsl after the update (#8859), similarity score: 0.79
• WSL not working after update from Microsoft store (#8260), similarity score: 0.78
• Can't open wsl possibly after update "the data is invalid" (#8826), similarity score: 0.77

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[OneBlue]

/logs

[edmondium]

Hello! Could you please provide more logs to help us better diagnose your issue?

To collect WSL logs, download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging

Thank you!

WslLogs-2023-12-13_02-17-34.zip

[OneBlue]

Thank you @edmondium. I'm not seeing any WSL error in the trace you shared. Can you make sure you reproduced the issue while the trace collection was running ?

[MHamzaRajput]

I delete the file .wslconfig in C:\Users{USER_NAME} and WSL back into working state.