-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Cannot create new project #54148
Comments
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
do you have the core? Is is possible that you are missing some dependencies? |
There were no errors when I installed dotnet. Even if I miss some
dependencies, how to check this?
|
You're using the snap install of .NET. Probably the package install will work fine for you: https://docs.microsoft.com/en-us/dotnet/core/install/linux-ubuntu.
This command starts 2 applications, it's not clear which one gives you the segfault.
Can you also share the output of?
|
Sure
|
Can you install
Start the debugger:
Now run the app:
The app will segfault.
|
both return "segmentation fault (core dumped)"
|
[Triage] Closing Snap issues to reflect current priorities. |
Describe the bug
Cannot create new project
To Reproduce
when I try to create new app (dotnet new console -o myApp), from tutorial, this error appears
Exceptions (if any)
segmentation fault (core dumped)
Further technical details
Пакет SDK для .NET (отражающий любой global.json):
Version: 5.0.301
Commit: ef17233f86
Среда выполнения:
OS Name: ubuntu
OS Version: 21.04
OS Platform: Linux
RID: ubuntu.21.04-x64
Base Path: /snap/dotnet-sdk/129/sdk/5.0.301/
Host (useful for support):
Version: 5.0.7
Commit: 556582d
.NET SDKs installed:
5.0.301 [/snap/dotnet-sdk/129/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.7 [/snap/dotnet-sdk/129/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.7 [/snap/dotnet-sdk/129/shared/Microsoft.NETCore.App]
VS Code 1.57.0
The text was updated successfully, but these errors were encountered: