Unable to push on Linux with newer versions of libcurl

[verkvieto]

Prerequisites

• Have you tried to reproduce the problem in Safe Mode? Yes.
• Have you followed all applicable steps in the debugging guide? Yes.
• Have you checked the FAQs on the message board for common solutions? Yes.
• Have you checked that your issue isn't already filed? Yes.

Description

Unable to push commits on Linux with newer versions of libcurl.

Steps to Reproduce

1. Open a GitHub repository.
2. Make a commit.
3. Try to push.

Expected behavior:

The commit pushes successfully.

Actual behavior:

The push fails.

Reproduces how often:

100% of the time.

Versions

atom --version
Atom    : 1.18.0-beta0
Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0

apm --version
apm  1.18.1
npm  3.10.10
node 6.9.5 x64
python 3.6.1
git 2.13.0

OS: Arch Linux

Additional Information

Pop-up error message:

Unable to push
git-remote-https: /usr/lib/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by git-remote-https)

---

Edit by @rsese to mention workaround

From #848 (comment) below:

A workaround you can use is to set LOCAL_GIT_DIRECTORY to your system installation of Git - this worked for me on Ubuntu 18.04:

export LOCAL_GIT_DIRECTORY=/usr

[smashwilson]

Looks like we're still dynamically loading libcurl from git binaries within dugite. @shiftkey, any thoughts on this?

[shiftkey]

@smashwilson not initially. I was chatting with @dscho about this last night, he's given me some thoughts but it seems like A Really Hard Task to put a purely portable Git together for Linux due to the explicit and implicit dependencies.

I've opened desktop/dugite-native#42 to track investigating the libcurl issue. I'm kinda swamped for the next week with conference stuff, but I'll dump some more thoughts in there when I can.

[NormanEdance]

Any progress/quickfix, guys?

[davidkwast]

me too, started today on Ubuntu 18.04 with Atom 1.31.1

[git-elliot]

I've installed some of the libraries but still getting this error

/snap/atom/200/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib/x86_64-linux-gnu/libgnutls.so.30)
/snap/atom/200/usr/share/atom/resources/app.asar.unpacked/node_modules/dugite/git/libexec/git-core/git-remote-https: /snap/core/current/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.26' not found (required by /usr/lib/x86_64-linux-gnu/libp11-kit.so.0)

I think dependencies are hard coded and requires the older version to be able to run.

[dscho]

@parasthekoder indeed, the GLIBC versioning hits you.

One way to work around this is to add (ugly) defines for the versioned symbols. I did this in a different project, a long time ago: https://github.com/imagej/imagej-launcher/blob/master/src/main/include/glibc-compat.h (and I wrote a script to update that header based on a built executable: https://github.com/imagej/imagej-launcher/blob/master/force-glibc-compat.sh

A less hacky way might be to use ELF statifier, as I mentioned elsewhere, but this comes with the big caveat that I have not tried it, and therefore I cannot vouch that it works.

The ball is in your park now, @parasthekoder

[amirhfarzaneh]

So I think all of ubuntu 18.04 user with the latest update cannot use Atom for GitHub right now.

[daviwil]

Lemme see if I can squeeze this into the next Atom hotfix. It'll be dependent on whether this doesn't break things on earlier Ubuntu releases.

[schampseix]

should be work with installing : sudo apt install libcurl3/bionic , its working on my side under ubuntu 18.04