starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 08:24:54 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Ubuntu Not Opening #1946

New Issue
Closed
opened 2026-01-30 22:42:37 +00:00 by claunia · 12 comments
claunia commented 2026-01-30 22:42:37 +00:00
Owner
Copy Link

Originally created by @Sameer2307 on GitHub (Jun 23, 2019).

Ubuntu doesn't show up in the terminal. Its installed on my machine but the new terminal is recognizing it.

Originally created by @Sameer2307 on GitHub (Jun 23, 2019). Ubuntu doesn't show up in the terminal. Its installed on my machine but the new terminal is recognizing it.
claunia added the Issue-QuestionArea-SettingsResolution-AnsweredProduct-Terminal labels 2026-01-30 22:42:38 +00:00
claunia commented 2026-01-30 22:42:39 +00:00
Author
Owner
Copy Link

@Sameer2307 commented on GitHub (Jun 23, 2019):

The command wsl -l
gives me following Windows Subsystem for Linux Distributions: Ubuntu-18.04 (Default)

@Sameer2307 commented on GitHub (Jun 23, 2019): The command wsl -l gives me following Windows Subsystem for Linux Distributions: Ubuntu-18.04 (Default)
claunia commented 2026-01-30 22:42:39 +00:00
Author
Owner
Copy Link

@scottwmaxwell commented on GitHub (Jun 23, 2019):

Also Having this problem. Installed ubuntu. wsl -l gives me
Windows Subsystem for Linux Distributions: Ubuntu (Default)

@scottwmaxwell commented on GitHub (Jun 23, 2019): Also Having this problem. Installed ubuntu. wsl -l gives me Windows Subsystem for Linux Distributions: Ubuntu (Default)
claunia commented 2026-01-30 22:42:39 +00:00
Author
Owner
Copy Link

@Sh4d commented on GitHub (Jun 23, 2019):

Same here, window spawns momentarily but immediately quits. Launching wsl from a command prompt tab works fine. Also on ubuntu 18.04

@Sh4d commented on GitHub (Jun 23, 2019): Same here, window spawns momentarily but immediately quits. Launching wsl from a command prompt tab works fine. Also on ubuntu 18.04
claunia commented 2026-01-30 22:42:39 +00:00
Author
Owner
Copy Link

@KalyanVem commented on GitHub (Jun 23, 2019):

Same here, wsl -l lists Ubuntu as default. But the terminal is not showing it.

@KalyanVem commented on GitHub (Jun 23, 2019): Same here, wsl -l lists Ubuntu as default. But the terminal is not showing it.
claunia commented 2026-01-30 22:42:39 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 23, 2019):

If you installed and launched terminal before installing WSL/ubuntu, it doesn't currently autodetect outside of first launch. You can, of course, add a custom profile.

@DHowett-MSFT commented on GitHub (Jun 23, 2019): If you installed and launched terminal before installing WSL/ubuntu, it doesn't currently autodetect outside of first launch. You can, of course, add a custom profile.
claunia commented 2026-01-30 22:42:40 +00:00
Author
Owner
Copy Link

@Sameer2307 commented on GitHub (Jun 23, 2019):

How to add a custom profile

@Sameer2307 commented on GitHub (Jun 23, 2019): How to add a custom profile
claunia commented 2026-01-30 22:42:40 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

I am trying to add a custom profile for my kali WSL, I tried kali.exe as the 'commandline' parameter of the profile, it didn't work. I think it has something to do with the guid or the 'commandline' parameter itself. the profile shows itself in the dropdown but doesn't work as linux terminal.
**edit: **
commandline parameter : wsl.exe -d kali-linux

@Shorotshishir commented on GitHub (Jun 23, 2019): I am trying to add a custom profile for my kali WSL, I tried `kali.exe` as the 'commandline' parameter of the profile, it didn't work. I think it has something to do with the `guid` or the 'commandline' parameter itself. the profile shows itself in the dropdown but doesn't work as linux terminal. **edit: ** commandline parameter : `wsl.exe -d kali-linux`
claunia commented 2026-01-30 22:42:40 +00:00
Author
Owner
Copy Link

@weems commented on GitHub (Jun 23, 2019):

Confirmed that re-installing the application adds WSL Installed Distros to the list.

@weems commented on GitHub (Jun 23, 2019): Confirmed that re-installing the application adds WSL Installed Distros to the list.
claunia commented 2026-01-30 22:42:41 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

if reinstalling doesn't find the installed WSL (for some reason) , open appdata (windows+r, then type appdata, hit enter ) then go to Local>Packages>Microsoft.WindowsTerminal_8wekyb3d8bbwe>RoamingState and delete the package.json file. reopen the Terminal app. This will reset the settings to default and load all available terminals.

@Shorotshishir commented on GitHub (Jun 23, 2019): if reinstalling doesn't find the installed WSL (for some reason) , open `appdata` (windows+r, then type appdata, hit enter ) then go to `Local>Packages>Microsoft.WindowsTerminal_8wekyb3d8bbwe>RoamingState` and delete the package.json file. reopen the Terminal app. This will reset the settings to default and load all available terminals.
claunia commented 2026-01-30 22:42:41 +00:00
Author
Owner
Copy Link

@kn0rki commented on GitHub (Jun 23, 2019):

Doenst work for Powershell core that is not installed on default path :(

if reinstalling doesn't find the installed WSL (for some reason) , open appdata (windows+r, then type appdata, hit enter ) then go to Local>Packages>Microsoft.WindowsTerminal_8wekyb3d8bbwe>RoamingState and delete the package.json file. reopen the Terminal app. This will reset the settings to default and load all available terminals.

@kn0rki commented on GitHub (Jun 23, 2019): Doenst work for Powershell core that is not installed on default path :( > if reinstalling doesn't find the installed WSL (for some reason) , open `appdata` (windows+r, then type appdata, hit enter ) then go to `Local>Packages>Microsoft.WindowsTerminal_8wekyb3d8bbwe>RoamingState` and delete the package.json file. reopen the Terminal app. This will reset the settings to default and load all available terminals.
claunia commented 2026-01-30 22:42:41 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 23, 2019):

@kn0rki for not default location installations, u need to add a custom profile.
just make a duplicate of the default PowerShell profile and use the complete path of the .exe in the 'commandLine': parameter. It should work just fine.
Update: reference #1415

@Shorotshishir commented on GitHub (Jun 23, 2019): @kn0rki for not default location installations, u need to add a custom profile. just make a duplicate of the **default PowerShell profile** and use the **complete path of the .exe** in the **'commandLine'**: parameter. It should work just fine. Update: reference #1415
claunia commented 2026-01-30 22:42:41 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 24, 2019):

This seems solved?

@DHowett-MSFT commented on GitHub (Jun 24, 2019): This seems solved?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Issue-Question Product-Terminal Resolution-Answered
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1946
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?