Closed emsal0 closed 4 years ago
Update: apparently this works when I have an X server running (I'm using vcXsrv). If I run pip3
again with the DISPLAY
environment variable not set, then it works.
To clarify:
DISPLAY
environment variable is not set, pip3 19.3.1 works just fine.DISPLAY
environment variable is set (in my case it was set to 172.30.144.1:0
), and there is no X server running, presumably because the new version of pip3 relies on DBus messaging (would need to investigate the root cause)To clarify:
- If the
DISPLAY
environment variable is not set, pip3 19.3.1 works just fine.- If the
DISPLAY
environment variable is set (in my case it was set to172.30.144.1:0
), and there is no X server running, presumably because the new version of pip3 relies on DBus messaging (would need to investigate the root cause)
Just encountered this issue in 2021! So frustrating trying everything but pip just wouldn't work. Using unset DISPLAY
fixed everything instantly. Thanks!
This issue still remains now.
unset DISPLAY
could fix
Is there any other solution? What happened?
Also, just encountered this same exact issue. The only difference I can tell is that I was in a virtual env with --system-site-packages enabled.
unset DISPLAY
fixed.
Using: python 3.8.5 pip version 20.0.2
Also running WSL 2 with Ubuntu:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.2 LTS"
I'm using WSL 2 using Ubuntu:
Powershell output for
wsl -l -v
:Ubuntu version:
And here's the aformented problem. I start with a fresh install of
python3-pip
(version 9.0.1) fromapt
, then upgradepip
using itself (upgrading to 19.3.1), then attempt to upgrade/install pip again:At this point this operation hangs forever until I do a Ctrl-C. Here's the prompt from the Keyboard Interrupt, if it helps