-
Notifications
You must be signed in to change notification settings - Fork 854
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
WSL Ubuntu 20.04 - gpg: can't connect to the agent: IPC connect call failed #5125
Comments
Which Windows build? Ubuntu 20.04 right now is incompatible with WSL1. |
OS Build 18363.815 I do not think WSL 2 is available to me right now. I am no longer getting preview updates, so I have to wait until the official release. |
Can you please run: $ sudo apt install strace -y $ strace -o strace.log curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - Then post it to a gist? |
Are you on WSL 1 @maximilia? |
@sirredbeard yes, I am |
My trace, if it provides any insight @maximilia's does not: https://gist.github.com/dawsonc623/06c9300dca0d5504602d6ea3ffe21004 |
I got the same error when a tried to run curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash - |
It fails in WSL1 build 19041 and It works in WSL1 build 19613 so I'd say same as #4898. |
How to fix this issue until Microsoft releases the fix via Windows Update. Solution by @rafaeldtinoco: sudo add-apt-repository ppa:rafaeldtinoco/lp1871129
sudo apt update
sudo apt install libc6=2.31-0ubuntu8+lp1871129~1 -y
sudo apt-mark hold libc6 |
@onomatopellan in case if build-essential is installed it should be:
to avoid g++ removal. But otherwise it works fine, thanks to you and @rafaeldtinoco. |
That worked, thank you very much. |
Hey everyone, enabling WSL 2 works for me. What I did:
|
Will result in:
Make sure you add the
|
I tried this workaround and it did work but I gotta say it seems like a pretty ugly hack. What are the repercussions of holding back |
thanks to @rafaeldtinoco and @Kagami for the workaround! |
For me, WSL2 is a no can do. My dev environment heavily relies on both virtual box and VMware workstation. I know vbox 6 is compatible, but VMware has yet to release their patch... |
@bkraul VMWare released a tech preview that works with WSL2. If there are no important bugs this will be next stable release. |
Guys, so what do I do if I have 18363 (WSL 1)build only and I need to use gpg? If I use Ubuntu 18.04 instead of 20.04 will it help? |
Pretty much seems to be the only solution for you if going with 20.04. The hack does work, tho. Not sure how intricate your particular WSL instance is, but I would figure if it is not that intricate and you need to use gpg, the hack is worth implementing. Or yeah, you could try 18.04. I believe 18.04 does not have that issue. At least I do not experience on my 18.04 instance. |
@onomatopellan Thanks, I did check that out. But can't move to it until GA because of critical development environments running on VMware at the moment. I will keep an eye out for both Windows May 20 update and VMWare GA release. |
Temporary Solution: Downgrade libc6 Edit: /var/lib/dpkg/info/libc6:amd64.postinst and remove the sleep 1 that is in nearly the last line. |
From this command sudo add-apt-repository ppa:rafaeldtinoco/lp1871129
sudo apt update
sudo apt install libc6=2.31-0ubuntu8+lp1871129~1 libc6-dev=2.31-0ubuntu8+lp1871129~1 libc-dev-bin=2.31-0ubuntu8+lp1871129~1 -y --allow-downgrades
sudo apt-mark hold libc6 What's happen when Windows release update for this issue and How to rollback when Windows solved this ? |
|
1909 build has WSL 2 ? |
It's a broken libc6 and it's used everywhere. Edit: Ok now there is no doubt both issues are related: gpg uses nanosleep from glibc which right now is broken in Ubuntu 20.04 WSL1. |
Had the same issue with the kubernetes repo key; I chucked the key in /etc/apt/trusted.gpg.d, it worked and I moved on. |
Windows 10 2004 came out 2 days ago. With this, WSL2 is now widely available. I upgraded my ubuntu WSL instance to WSL2, and everything works as expected. |
Just for the record, since that's the first google finds when searching for the issue: You don't need to fiddle with your clib or even downgrade to gpg1, the only thing needed to make it work is an environment-Variable, which is best to set by appending these Lines to your shell-Initialisation (~/.bashrc on a default-wsl-ubuntu install):
See EDIT: forgot to say why I still write this, since wsl 2 also fixes the Issue: You can't use wsl 2 on arm64 devices at the moment, ther seems to be a showstopper for the new release for this architecture. |
Worked nice! Thinks. |
This works for me |
Thanks this works for me. |
Best sollution. Simple. |
Still having the same issue after try every "solution here" |
@janba12: #5125 (comment) worked for me. You might try this: sudo apt remove gpg
sudo apt autoremove --purge -y
sudo apt install gnupg1 |
@janba12 What's the output of |
I run into the same issue in trying to install v14 of Nodejs following the steps outlined in this article. It seems that the nodesource_setup.sh script that is downoaded reverses the workaround steps
and fails with the same error. Here is version info for me
|
@KevinBurton Your Ubuntu distro is still WSL1. You need to convert it to WSL2 with |
Don't mess up your system by installing / disabling extra programs, just follow the inctructions carefully on micosoft's website. It takes only 5 minutes to apply. |
The issue i had happened because i was instaling "ubuntu" from Microsoft Store. i just uninstall that one and get Ubuntu 20.04 LTS , that fixed all the issues. thanks for your answers |
Thank you! That was much simpler than some of the solutions above, and it worked for me when installing Yarn |
this is really good for me! ths!!!! windows 10 2004 , wsl1 Ubuntu 20.04 |
Ubuntu 20.04 |
I was trying to run as follows: And was getting error: Ran the commands provided > sudo apt remove gpg
|
Works perfectly (and so true btw, just read the docs 😅) while neither other solution worked for me. Thank you so much! 🤘 So here are the commands that saved my day:
(last command is for checking that Ubuntu is using WSL2) |
On Windows 10 before the Windows preview. Shortly if you want to use wsl command with |
do sudo apt remove gpg then sudo apt install gnupg1 it worked. |
This helped me immensely. I hadn't struggled for long. Once I saw the issue, I googled and luckily found this. It worked for me as now I've been able to install rails. |
Time to get rid of any workarounds. The fix for WSL1 in Windows 10 v2004 is finally here. KB4571756 (OS Build 19041.508) Now sleep in Ubuntu 20.04 WSL1 is working just fine. |
Workaround discussions (to the extent anyone wants to continue them) can happen over in discussions. |
I have a fresh installation of Windows 10, and I am trying to get a development environment with WSL set up. I enabled WSL and installed Ubuntu from the Microsoft Store. Everything went smoothly in that process. Then, I tried to go through the steps to install Yarn here.
When I try to run the first line (
curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
), I get the error in the title:I have looked up this error, and there were a few suggestions related to
gpg-agent
that I tried, such as manually starting the agent and creating/deleting certain configuration files related togpg
. Everything I tried resulted in the same error above. I am at a loss for what to try next. Has anyone else seen and fixed this issue?The text was updated successfully, but these errors were encountered: