Launch WSL2 through APP icon don't work, and would terminate all running Terminal sessions

[DanielYang59]

Windows Version

Microsoft Windows [Version 10.0.22631.3155]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-microsoft-standard-WSL2

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Trying to launch WSL2 (Ubuntu 22.04 LTS) by clicking the "Ubuntu 22.04 LTS" icon would not work, an empty pops up and disappears after a few seconds, as seen in the following gif:

Worsestill, if there is any Terminal session already running, it seems to terminate them as well, seen:

Meanwhile, WSL2 could be accessed just fine by starting a Terminal session, and type wsl.

Expected Behavior

Clicking the WSL2 APP icon should start WSL2 session just fine, and should not affect other running Terminal sessions.

Actual Behavior

Cannot start WSL2 by clicking the icon, and would terminate other Terminal sessions.

Diagnostic Logs

It's hard to provide log because I'm not very familiar with log location of Terminal nor WSL2. Please let me know how could I collect such logs and I would be more than happy to provide them.

Meanwhile the Terminal session for WSL2 just disappears so I didn't get much useful feedback, but I enclosed the settings.json for Terminal hoping it would help pin the issue.

settings.json

[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!

Closed similar issues:

• WSL2 hangs on launch (#5756), similarity score: 0.78
• WSL2 terminal won't start (#5912), similarity score: 0.75
• Can't open Windows app from WSL 2 anymore (#4567), similarity score: 0.75
• Unable to launch WSL2 (#4598), similarity score: 0.75
• Unable to launch Windows applications from WSL (#3809), similarity score: 0.74

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

[DanielYang59]

Closing as this does not seem a WSL2 issue, everything works fine after rolling Terminal back to version 1.18.10301.0 as suggested in microsoft/terminal#16730 (comment).