-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Launching "wsl" from search, or "ubuntu" from the run dialog doesn't launch with profile customisations #12755
Comments
Same as the WSL launching issue from #12582 But is launching Ubuntu, and not having it profile matched, a problem that will be fixed with the above? |
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! |
@NewtonChutney The temporary solution for me was to create a desktop shortcut for Ubuntu and so it works wt -p "Ubuntu" Icon https://www.iconspedia.com/icon/ubuntu-flat-circle-icon-41194.html |
@maisondasilva thanks mate! But I'd rather reserve the precious real estate for other things.. 🥲 😅 And if people have quite a few WSL profiles.. This isn't that elegant of a workaround.. It's gonna be better if the WSL team changes those executables (eg Ubuntu.exe) to point to WT profiles somehow.. 😂 But everything lies in that "somehow".. It's the devs' magic! |
I don't seem to find a similar issue elsewhere, but do merge this issue with an existing one if there is any..
Whenever I launch WSL by searching from start, or by entering "wsl" or "ubuntu" in the run dialog, windows terminal launches it without the profile customisations. I seem to think this is a supported scenario, as many people would be launching from Win+r as it is very handy..?
Desired Behaviour:
Desired behaviour when launching "Ubuntu on Windows" app or the profile from WT:
What is being seen:
What I get when "wsl" or "ubuntu" is launched from win+run dialog:
Steps to reproduce:
Other Data:
What device you're running (inc. CPU type, memory, disk, etc.):
What build of Windows your device is running
What tools and apps you're using (e.g. VS 2019, VSCode, etc.)
Your Environment
The text was updated successfully, but these errors were encountered: