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
libidn2-0:amd64 (2.2.0-1+ubuntu18.04.1+deb.sury.org+1) - PHP Curl Errors #1247
Comments
it actually breaks more apps. After the same upgrade gnome-terminal.real: relocation error: /usr/lib/x86_64-linux-gnu/libgnutls.so.30: symbol _idn2_punycode_decode version IDN2_0.0.0 not defined in file libidn2.so.0 with link time reference had to revert to previous deb to fix |
Also breaks other utilities like apt Solution discovered via: Workaround Package source: https://packages.ubuntu.com/bionic/libidn2-0
|
It pretty much breaks the OS - don't reboot. If you do reboot you will need to go to another console and manually set up network card (network manager will not start), set up route table and DNS. Once that is done download the latest Ubuntu .deb using wget (curl broke) then install with dpkg (apt was broken too). Possibly helpful link to Ubuntu package: https://packages.ubuntu.com/search?suite=bionic&searchon=names&keywords=libidn2-0 May be easiest to transfer from a booting computer if you don't have lynx or links2! |
ACK issue on 'standard' Ubuntu 18.04 server architecture (i.e. not related only to 'aws' architecture). Who knew this library could throw so many things so much out of whack. Package libidn2-0 downgraded by hand & held, waiting for a solution. |
It also broke http used by apt-get:
|
In my case, i had to download the i386 version as well and install both. Otherwise dpkg couldn't proceed.
|
The same over here! |
Faced with the same error. I use this libidn2-0_2.0.5-1_amd64.deb instead:
|
I hate when the upstream doesn't bump SOVERSION when they drop quote-quote-internal-quote-quote symbols :( - https://gitlab.com/libidn/libidn2/issues/74 I am going to restore the missing symbols in a minute in the next upload. Sorry for all the havoc, the other Debian maintainer who did the 2.2.0-1 upload to Debian should have noticed that. |
Btw for people who already did the reboot (like me) grab a different device that has internet and usb working (i used my phone) grab the deb you need there and just transfer it over using the usb stick. http://mirrors.kernel.org/ubuntu/pool/main/libi/libidn2/libidn2-0_2.0.4-1.1build2_amd64.deb |
It should be fixed as of this moment.
|
wget http://mirrors.kernel.org/ubuntu/pool/main/libi/libidn2/libidn2-0_2.0.4-1.1build2_amd64.deb This work for me on AWS ubuntu 18.04.2. |
If you actually read the linked bug report, you would know it has been already fixed, and neither downgrading nor pinning is needed. If you pin the package version, you won’t get any security updates. |
@oerdnj downgrading may be needed for users who got the dead update and are stuck though. but I agree about the pinning. |
@oerdnj It is not so simple. Those whose computers were affected by this "disaster", no program works, including network. Therefore, the only solution is to download the package to another computer, save it to a USB Flash, connect it to the affected computer, enter the TTY (because the terminal does not work), degrade package and restart. After restart everything is normalized. And it can be updated to fix the problem |
Any update on this? I use ubuntu on my work and everything is crazy! |
|
after doing the steps listed above I was able to get my server back in working order, I just wished I saw this before I decided to reinstall the OS on my laptop (luckily I had a secondary drive I could move my files to so it wasn't a total disaster). |
Just download the .deb of the new version (it might be needed to do that on another computer and bring it to the target using a usb stick or other ways) and install it using the file explorer (gui) or dpkg or similar tools (cli), you NO NOT NEED to hold updates. This was only needed the short time until the update released, you also don't need to downgrade anymore as you can just pull in the update. |
Thank you but I can't find the link to the new version? The server is still functioning so I can use wget to get it. |
Issue & Steps to Reproduce
I completed an apt-upgrade and one of the candidates was libidn2-0:amd64.
When I upgraded to libidn2-0:amd64 (2.2.0-1+ubuntu18.04.1+deb.sury.org+1) the php curl module stoped working.
The fix I found after some Googling [https://superuser.com/questions/1466648/kali-linux-failed-after-upgrade] was to downgrade libidn2 manually using a deb.
PHP worked as expected with the curl module active. I tried to then perform an apt-upgrade however it installed the new version and broke curl again.
Distribution
The text was updated successfully, but these errors were encountered: