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
segfault following debian tutorial #649
Comments
Hi @mm-s - which version of Debian so I can give it a go? |
I've got the same problem on my computers running Debian sid, and I can not get it running on Debian testing (stretch) because it requires OpenSSL 1.0.0 that is no longer packaged. |
@bartonjs let me know that we have an issue to support OpenSSL 1.1, but .NET Core 2.0 doesn't support it yet. Debian 9 comes with OpenSSL 1.1, which we don't support. @leecow @Petermarcu @richlander - our supported versions roadmap says that .NET Core 2.0 supports |
@pinaraf The back-compat package seems to be called |
I removed on my sid the old unmaintained libssl 1.0.0 package, and now I get the error message |
So, basically, for Debian 9+ corefx must be compiled with OPENSSL_NO_SSL3_METHOD defined… |
@eerhardt Yes, it's my understanding that Debian 9 will be supported by 2.0. |
@pinaraf Ah, yeah, I thought that sounded familiar... we fixed it two weeks ago: dotnet/corefx#19070. The latest daily builds should work on Debian 9. |
@bartonjs And I confirm the latest builds work on Debian 9 with OpenSSL 1.0.2. |
closing this because it looks like we've solved the issue. |
fwiw, I still see this on:
Latest debian stretch (now the stable release) |
@brendandburns - did you install |
$ sudo apt-get install libssl1.0.2
[sudo] password for bburns:
Reading package lists... Done
Building dependency tree
Reading state information... Done
libssl1.0.2 is already the newest version (1.0.2l-2).
0 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. It appears to be the right version. Happy to help with further debugging, let me know what you need me to do. |
Ah, I dug around a little more. I had a stray Not sure why that was there, but moving it out of the way (adding Thanks. |
Great to hear you found it @bartonjs should we open an issue to see if we can be more resilient here? |
@Petermarcu If it's badly pervasive, maybe? libcrypto.so.1.0.0 (and libssl.so.1.0.0) is the name recommended by OpenSSL. Debian is deviating from that recommendation and naming it libcrypto.so.1.0.2. Preferring Debian's name above OpenSSL's recommended name on Ubuntu seems weird. Though, I guess that we could assert that libcrypto and libssl need the same SONAME version fragment and we load them locked, or not at all. @janvorli, thoughts? (I'm assuming that there was an aberrant libssl.so.1.0.0, but not also an aberrant libcrypto.so.1.0.0) |
@brendandburns Oh wow, thanks for the solution! I was hitting segfaults with latest preview on Debian 9, and this fixed it. |
Experienced this issue, but pulling down the newest (preview 2 2.0 SDK) seems to fix it nicely |
I had the same problem, and solution for me was |
I have the same problem. it dont work on default settings
|
Just encountered the same issue on debian stretch while following the instruction on |
Same here, segfault on Debian Stretch when using |
@brendandburns The reason I had
I have no rhash installed so no other program than Spotify should need it on my install. I moved the
and it works. Now |
I just wrote |
Thanks @willvitorino, I was able to solve my seg fault error, 3 years later! As strange as it sounds, opting out of telemetry stopped the crashes. |
segfault at step 2 of this tut:
https://www.microsoft.com/net/core/preview#linuxdebian
log:
root@fish# dotnet new console
Welcome to .NET Core!
Learn more about .NET Core @ https://aka.ms/dotnet-docs. Use dotnet --help to see available commands or go to https://aka.ms/dotnet-cli-docs.
Telemetry
The .NET Core tools collect usage data in order to improve your experience. The data is anonymous and does not include command-line arguments. The data is collected by Microsoft and shared with the community.
You can opt out of telemetry by setting a DOTNET_CLI_TELEMETRY_OPTOUT environment variable to 1 using your favorite shell.
You can read more about .NET Core tools telemetry @ https://aka.ms/dotnet-cli-telemetry.
Configuring...
A command is running to initially populate your local package cache, to improve restore speed and enable offline access. This command will take up to a minute to complete and will only happen once.
Decompressing 100% 6845 ms
Expanding 100% 13180 ms
Getting ready...
Segmentation fault
root@fish# dotnet new console -o hwapp
Getting ready...
Segmentation fault
The text was updated successfully, but these errors were encountered: