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

Terminal crashs after an error message 'There is no distribution with the supplied name' #1692

Closed
techloghub opened this issue Jun 28, 2019 · 4 comments
Labels
Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Product-WSL Issue that should probably go to Microsoft/WSL Resolution-Answered Related to questions that have been answered

Comments

@techloghub
Copy link

techloghub commented Jun 28, 2019

Environment

pc: thinkpad x1c
cpu: Intel i7-7500U
gpu: Intel HD Graphics 620
memory: 8GB
os: windows10 1832.175

Steps to reproduce

I installed windows terminal(preview) in Microsoft Store, then I clicked the icon to start it. Surprisingly, it crashed.

Actual behavior

It was so fast that I didn't see any word in it earlier, I think it is just like #1364 , I found the following info in system error log:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2019-06-28T01:24:33.401096400Z" /> 
  <EventRecordID>2813</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>DESKTOP-I4MNSMJ</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>WindowsTerminal.exe</Data> 
  <Data>1.0.1906.20005</Data> 
  <Data>5d0c1459</Data> 
  <Data>TerminalApp.dll</Data> 
  <Data>1.0.1906.20005</Data> 
  <Data>5d0c140d</Data> 
  <Data>c0000005</Data> 
  <Data>000000000003a539</Data> 
  <Data>598</Data> 
  <Data>01d52d503b8fa64f</Data> 
  <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe</Data> 
  <Data>C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe\TerminalApp.dll</Data> 
  <Data>2068bb0f-9ffe-446c-b6a7-c0f52dcb737d</Data> 
  <Data>Microsoft.WindowsTerminal_0.2.1715.0_x64__8wekyb3d8bbwe</Data> 
  <Data>App</Data> 
  </EventData>
  </Event>

After many attempts, I used the 'print screen' button to see the error message in windows terminal window:
QQ截图20190628092434

It means: "There is no distribution with the supplied name"

I thought maybe it because that the profile of wsl was wrong, so I tried to look for the profile.json in whole my disks, but I could not find it anywhere.

Some useful imformation is that everytime, when I start my windows terminal, CPU load goes up immediately, and at same time GPU load goes 100%
My wsl is ubuntu 18.04 LTS, I think the error is because of the space in it name, but I don't know how to deal with it.

Thanks

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 28, 2019
@techloghub techloghub changed the title Terminal crashs after an error message 'There is no distribution with the supplied name' then to be white Terminal crashs after an error message 'There is no distribution with the supplied name' Jun 28, 2019
@techloghub
Copy link
Author

techloghub commented Jun 28, 2019

Just as I guessed, I tried to uninstall my wsl and reinstall my windows terminal, and now it seems to be alright.
But I also want to know how to deal with it without uninstall the ubuntu 18.04 LTS, thanks!
Maybe some others has the same crash problem as me.

@Shorotshishir
Copy link

Shorotshishir commented Jun 28, 2019

the error itself is self-explanatory. There wasn't a distribution with the supplied name.
It means in your profile.json where you configured the path of the WSL i.e. the commandLine parameter, the name wasn't correct, probably a typo. "wsl.exe -d <name-was-incorrect>"

You can reproduce the error just by changing the name and trying to open the terminal WSL

@techloghub
Copy link
Author

the error itself is self-explanatory. There wasn't a distribution with the supplied name.
It means in your profile.json where you configured the path of the WSL i.e. the commandLine parameter, the name wasn't correct, probably a typo. "wsl.exe -d <name-was-incorrect>"

You can reproduce the error just by changing the name and trying to open the terminal WSL

But I can't find profiles.json anywhere when the error happens, after I reinstalled it and all is right now, I find the profiles.json in directory: AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\RoamingState
I don't know why, is it aways here but I didn't realize it? I don't think so.

@miniksa
Copy link
Member

miniksa commented Jun 28, 2019

The profiles.json should always be at that location for right now.

We might move it to make it easier to find #1567 or make a UI for it #1564.

But for now, that's where it is.

It looks like this question is answered, so I'm resolving this issue.

@miniksa miniksa closed this as completed Jun 28, 2019
@miniksa miniksa added Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Product-WSL Issue that should probably go to Microsoft/WSL Resolution-Answered Related to questions that have been answered and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jun 28, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Interaction Interacting with the vintage console window (as opposed to driving via API or hooks) Issue-Question For questions or discussion Product-Terminal The new Windows Terminal. Product-WSL Issue that should probably go to Microsoft/WSL Resolution-Answered Related to questions that have been answered
Projects
None yet
Development

No branches or pull requests

3 participants