-
Notifications
You must be signed in to change notification settings - Fork 391
Unable to push on Linux with newer versions of libcurl #848
Comments
Looks like we're still dynamically loading libcurl from git binaries within dugite. @shiftkey, any thoughts on this? |
@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. |
Any progress/quickfix, guys? |
me too, started today on Ubuntu 18.04 with Atom 1.31.1 |
I've installed some of the libraries but still getting this error
I think dependencies are hard coded and requires the older version to be able to run. |
@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 |
So I think all of ubuntu 18.04 user with the latest update cannot use Atom for GitHub right now. |
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. |
should be work with installing : sudo apt install libcurl3/bionic , its working on my side under ubuntu 18.04 |
I got an output that says What does this mean? |
looks like an apt process (update, upgrade or installation) is already in progress |
Thanks ! It worked perfectly for me. |
Yes , that work but you have to remove curl. |
How to remove curl? |
It is automatically. Curl need libcurl4 :( |
|
I think a workaround you can use is to set export LOCAL_GIT_DIRECTORY=/usr I first tried using
|
I tried that but it will remove my virtualbox-5.2 I think this is Atom's fault because Ubuntu 18.04 has the biggest Linux userbase. And going back to a older version of a library is not a proper fix. Atom should have this lib embed with it will not supprt the updated versions from now on. |
@davidkwast the core of the issue is upstream, and it's down to supporting versions of Ubuntu across the I'd love some help figuring this out. |
Any known workaround so we can I use Atom for GitHub on Ubuntu 18.04 without uninstalling |
Also getting the same error in Kali Linux 2018.3. I hope that Atom developers fix this issue in the next update! It's quite annoying as I have to use another Git GUI (SmartGit), even for small projects. |
@ricpelo @gautamkvashisht did you try @rsese's workaround? |
@rsese's workaround worked for me. Atom can push and fetch. |
Bundling a dynamically-linked binary which is built against a distro-specific set of libraries seems bananas. One option would be to compile against RHEL6 so you have a sensible baseline target. A better option would be to add |
Yeah, it works! Thank you very much! |
This comment has been minimized.
This comment has been minimized.
@kunjeshn How does installing a third-party package help with fixing an issue with Atom's default bundled software? We don't want another workaround, we want a fix. |
@kunjeshn this does not work for me, @rsese work around neither, however i can be executing solution wrongly.
|
Yes. But it didn't work. Still getting the same error. |
Also, I would prefer a fix than a workaround because a lot of users are facing this issue. |
I believe that desktop/dugite-native#129 has addressed the issue deep in the Git tooling, and version |
Just a note that we now use dugite@1.79.0 as of #1757. |
Thanks for getting this fixed @shiftkey! |
I can confirm that the updated |
@daviwil can you help me here, how do i apply this to my current installation? |
The only thing you can do right now is |
The workaround no longer works in Ubuntu 18.10 as perhaps to avoid a conflict with libcurl3 libcurl3 has been replaced with libcurl3-gnutls and libcurl-openssl1.0-dev (which depends on libcurl3) has been replaced with libcurl4-openssl-dev (depends libcurl4); /usr/lib/x86_64-linux-gnu/libcurl.so.4 is now owned by package libcurl4. Error: atom --version:
apm --version
apm list | grep github lsb_release -a:
dpkg -l | grep libcurl:
apt-file find /usr/lib/x86_64-linux-gnu/libcurl.so.4
Package needs to search for libcurl-gnutls.so.4 or upgrade to libcurl4
apt-cache show libcurl4-openssl-dev | grep Depends
|
@Spitfire1900 till fix is upload to atom i ll recommend to use it as before and when going to push to cloud use console to do it |
Looks like this is associated with desktop/dugite-native#109 |
The real fix to this issue is the update to |
I have confirmed that install of debian package output of atom/atom's commit 24d1bcc31's (current 1.32-releases tip) 🌮 |
1.32.1 and 1.33.0-beta1 have been released ⚡ Going to go ahead and close this but if you're still having issues, please let us know. |
Atom 1.32.2
|
@Amantel - the Snap installation is unofficial but If you can reproduce the error with a supported installation method, please open a new issue with the template filled out and we'll take a look. |
I'm on Kubuntu 18.04 and can't update from Atom 1.33 because of the libcurl3 vs libcurl4 dependencies. Not sure this issue was fixed by: atom/atom#18201 |
@ecotechie as a Kubuntu 18.10 user I can confirm that atom/atom#18201 resolved my issues per above comments from myself. |
@Spitfire1900 Yup I can push just fine... My bad. I meant to post this on the issue of not being able to update to newer versions of Atom since it has libcurl3 as a requirement and will therefor remove libcurl4 and any program using it. |
Per diff atom/atom@812dcc4, libcurl3 or libcurl4 will both satisfy the libcurl dependency of Atom 1.33's *.deb package. |
That seems about right, but I can't update to any versions after 1.33. It asks to remove libcurl4 and install libcurl3. Created a ticket in the Atom repo atom/atom#18758 |
Prerequisites
Description
Unable to push commits on Linux with newer versions of
libcurl
.Steps to Reproduce
Expected behavior:
The commit pushes successfully.
Actual behavior:
The push fails.
Reproduces how often:
100% of the time.
Versions
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
The text was updated successfully, but these errors were encountered: