Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicated Ubuntu WSL profiles on fresh install #15560

Closed
mwisnicki opened this issue Jun 15, 2023 · 4 comments
Closed

Duplicated Ubuntu WSL profiles on fresh install #15560

mwisnicki opened this issue Jun 15, 2023 · 4 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@mwisnicki
Copy link

mwisnicki commented Jun 15, 2023

Windows Terminal version

1.17.11461.0

Windows build number

10.0.19045.3086

Other Software

No response

Steps to reproduce

  1. Install wsl ubuntu
  2. Install terminal

Expected Behavior

Single Ubuntu profile for WSL

Actual Behavior

Two Ubuntu profiles for wsl Ubuntu distro:

  • wsl.exe -d Ubuntu and penguin icon
  • ubuntu.exe and ubuntu icon.
@mwisnicki mwisnicki added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 15, 2023
@lhecker
Copy link
Member

lhecker commented Jun 19, 2023

Could you comment the outputs of wsl --version and wsl --list --verbose? Additionally, a screenshot of HKCU\Software\Microsoft\Windows\CurrentVersion\Lxss in regedit would be helpful - something like this:
image

Edit: However, I feel like this problem is probably that the Ubuntu fragment somehow clashes with what we're doing by reading the registry... But I figured it can't hurt to have all the information.

@zadjii-msft
Copy link
Member

Oh this is surely the fact that Canonical ships a separate profile for Ubuntu, rather than a fragment that updates the existing one we generate. This has caused no end of confusion for everyone involved.

see #12961 et al

@carlos-zamora
Copy link
Member

Hi @mwisnicki. Thanks for filing. This is the same root cause as #12961. We need a holistic solution for all of them. Marking as a /dup of #12961

@microsoft-github-policy-service
Copy link
Contributor

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@microsoft-github-policy-service microsoft-github-policy-service bot added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants