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

Problem on Debian Buster (Testing) #2860

Closed
livarcocc opened this issue Jul 31, 2017 · 15 comments
Closed

Problem on Debian Buster (Testing) #2860

livarcocc opened this issue Jul 31, 2017 · 15 comments

Comments

@livarcocc
Copy link
Contributor

@livarcocc livarcocc commented Jul 31, 2017

From @matiux on July 30, 2017 21:11

When I run dotnet new console -o hwapp on Debian Buster (Debian Tetsing) I get this:

Getting ready...
Segmentation fault

$dotnet --info

.NET Command Line Tools (2.0.0-preview2-006391)

Product Information:
Version: 2.0.0-preview2-006391
Commit SHA-1 hash: ef5d4b47c3

Runtime Environment:
OS Name: debian
OS Version:
OS Platform: Linux
RID: debian-x64
Base Path: /usr/share/dotnet/sdk/2.0.0-preview2-006391/

Microsoft .NET Core Shared Framework Host

Version : 2.0.0-preview2-25407-01
Build : 40c5652

Copied from original issue: dotnet/cli#7319

@livarcocc
Copy link
Contributor Author

@livarcocc livarcocc commented Jul 31, 2017

From @matiux on July 30, 2017 21:22

Same thing with older version:

$ dotnet --info
.NET Command Line Tools (1.0.4)

Product Information:
Version: 1.0.4
Commit SHA-1 hash: af1e6684fd

Runtime Environment:
OS Name: debian
OS Version:
OS Platform: Linux
RID: debian.8-x64
Base Path: /opt/dotnet/sdk/1.0.4

Loading

@livarcocc
Copy link
Contributor Author

@livarcocc livarcocc commented Jul 31, 2017

@steveharter can you investigate first and if this is a CLI issue, please, re-activate the issue there?

Loading

@Petermarcu
Copy link
Member

@Petermarcu Petermarcu commented Jul 31, 2017

@janvorli , I would expect that from 1.X but in 2.0, we've tried to be more portable. For the 2.0 attempt, we should try to understand where the seg fault is happening.

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Jul 31, 2017

Working on repro...

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Jul 31, 2017

I was unable to repro the crash. Please try my configuration or let me know any differences.

  1. Pull ISO from https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/multi-arch/iso-cd/
  2. Install ISO on Windows Server 2012R2 via Hyper-V
  3. Follow docker commands at https://github.com/dotnet/dotnet-docker/blob/master/2.0/sdk/stretch/Dockerfile
  4. Run various dotnet commands including new console and run (successful)

dotnet --info output: (note that my SDK\CLI version is higher at 6497 vs. 6391)

.NET Command Line Tools (2.0.0-preview2-006497)

Product Information:
 Version:            2.0.0-preview2-006497
 Commit SHA-1 hash:  06a2093335

Runtime Environment:
 OS Name:     debian
 OS Version:
 OS Platform: Linux
 RID:         debian-x64
 Base Path:   /usr/share/dotnet/sdk/2.0.0-preview2-006497/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0-preview2-25407-01
  Build    : 40c565230930ead58a50719c0ec799df77bddee9

Loading

@anmsh
Copy link

@anmsh anmsh commented Aug 10, 2017

I have debian buster and I have the same issue.

I found this comment segfault following debian tutorial dotnet/core-setup#649 which mentions renaming libssl.so.1.0.0 lib to libssl.so.1.0.0.old.

Doing this worked, but the moment I do an apt-get update and upgrade, I see the segmentation fault again since the libssl.so.1.0.0 lib is getting restored.

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Aug 10, 2017

@animeshb did you do a clean install of buster or did you upgrade?

What does your /etc/apt/sources.list contain. I have:

deb http://ftp.us.debian.org/debian/ buster main
deb-src http://ftp.us.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main
deb-src http://security.debian.org/debian-security buster/updates main

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Aug 10, 2017

@animeshb also be sure you have libssl1.0.2 installed (that is in the docker scripts I mention earlier). I have:

/usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
/usr/lib/x86_64-linux-gnu/libssl.so.1.1

Loading

@anmsh
Copy link

@anmsh anmsh commented Aug 10, 2017

Steve,

I started from Jessie last year and then upgraded to Stretch earlier this year and came up to buster two months back.

This is my sources list:

deb http://httpredir.debian.org/debian buster main non-free contrib
# deb-src http://httpredir.debian.org/debian buster main non-free contrib

deb http://security.debian.org/ buster/updates main contrib non-free
# deb-src http://security.debian.org/ buster/updates main contrib non-free

deb http://httpredir.debian.org/debian buster-updates main contrib non-free
# deb-src http://httpredir.debian.org/debian buster-updates main contrib non-free

deb [arch=amd64] https://download.docker.com/linux/debian stretch stable
# deb-src [arch=amd64] https://download.docker.com/linux/debian stretch stable

I already had libssl.so.1.0.2 installed and it is at the latest version:

libssl1.0.2 is already the newest version (1.0.2l-2).

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Aug 10, 2017

@animeshb do you know why it is insisting on pulling the libssl.so.1.0.0 version? Can you apt-get remove ssl1.0.0 that?

Loading

@anmsh
Copy link

@anmsh anmsh commented Aug 10, 2017

I removed ssl1.0.0 and a bunch other stuff I am sure were not being used.

  gstreamer0.10-plugins-bad gstreamer0.10-plugins-base libass5 libcdaudio1 libdirac-encoder0 libgstreamer-plugins-bad0.10-0
  libgstreamer-plugins-base0.10-0 libgstreamer0.10-0 libjasper1 libmimic0 libpng12-0 libschroedinger-1.0-0 libslv2-9 libsoundtouch0
  libssl1.0.0 libvpx1 libwildmidi1

After this, I was able to run dotnet new console and other project types.

I will try other things and see if anything else breaks.

Thank you!

Loading

@anmsh
Copy link

@anmsh anmsh commented Aug 10, 2017

I did a upgrade and dist-upgrade and that did not create any trouble. dotnet new ran fine after this.

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Aug 10, 2017

Glad to know it was a configuration problem! Thanks for reporting this as it may help others.

I'm going to close this since @animeshb issue appears fixed and @matiux has not replied in a while. Please re-open if there are additional segfaults with buster.

Loading

@AlexBander
Copy link

@AlexBander AlexBander commented Sep 9, 2017

I have the same problem.
which configuration problem you mean?

it dont work on default settings

dotnet new Wird vorbereitet... Speicherzugriffsfehler

.NET-Befehlszeilentools (2.0.0)

Product Information:
 Version:            2.0.0
 Commit SHA-1 hash:  cdcd1928c9

Runtime Environment:
 OS Name:     debian
 OS Version:  9
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /usr/share/dotnet/sdk/2.0.0/

Microsoft .NET Core Shared Framework Host

  Version  : 2.0.0
  Build    : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
Distributor ID: Debian
Description:    Debian GNU/Linux 9.1 (stretch)
Release:        9.1
Codename:       stretch
Statusinformationen werden eingelesen.... Fertig
libssl1.0.2 ist schon die neueste Version (1.0.2l-2).

Loading

@steveharter
Copy link
Member

@steveharter steveharter commented Sep 21, 2017

@AlexBander the configuration problem was an older version of OpenSsl that was being used, and which is not compatible.

Loading

@msftgits msftgits transferred this issue from dotnet/core-setup Jan 30, 2020
@msftbot msftbot bot locked as resolved and limited conversation to collaborators Dec 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants