I’m having the same problem with protonVPN and followed several suggestions from this thread but none of them fixed it. I did reinstall the package from AUR and followed the instruction from proton after reading this thread. Typing protonvpn on the command line gives following metadata not found… but I don’t understand where to get it from.
[angelica@quiet-pc ~]$ protonvpn
Traceback (most recent call last):
File “/usr/bin/protonvpn”, line 33, in
sys.exit(load_entry_point(‘protonvpn-gui==1.0.1’, ‘console_scripts’, ‘protonvpn’)())
File “/usr/bin/protonvpn”, line 22, in importlib_load_entry_point
for entry_point in distribution(dist_name).entry_points
File “/usr/lib/python3.10/importlib/metadata/init.py”, line 919, in distribution
return Distribution.from_name(distribution_name)
File “/usr/lib/python3.10/importlib/metadata/init.py”, line 518, in from_name
raise PackageNotFoundError(name)
importlib.metadata.PackageNotFoundError: No package metadata was found for protonvpn-gui
Little bit offtopic but while you try to get protonvpn working
you can use windscribe vpn
It doesnt have a GUI like proton vpn but it just works and it is much faster than protonvpn
pamac install windscribe-cli
sudo systemctl enable windscribe
#following commands have to be executed everytime you want to connect
sudo systemctl start windscribe
windscribe connect
Never mind I’ll make do without my VPN until I get a magic updated that fixes it again. I’ve got problems connecting to a new printer to sort out first.
Cannot reproduce, at least not if I do it the proper way as outlined above, and I dont care enough to try any other way when it seems obvious everything works when operated correctly.
Not unrelated: I have the same issue as the main one of this topic: protonvpn-cli, installed through AUR, just stopped working. I now try to get it working and none of the solutions that I was able to try works:
pamac: sudo pacman -S $(pacman -Qoq /usr/lib/python3.9) raises these errors (sorry, it’s in French: translate roughly as “error: impossible to find the target: X”) erreur : impossible de trouver la cible : python-configparser erreur : impossible de trouver la cible : python-proton-client
paru: you propose (among other) to use paru, that I don’t know. If it’s just an AUR helper, then indeed pamac should do the job just fine. I just mention in my post that I did not test that part of your solution.
The problem seems to be on protonvpn-cli or on the AUR script side. Someone managed to solve it in the git thread posted (using yay, which from what I understand is a AUR helper - the default Arch Linux one?), but I can’t reproduce it with pamac.
From comments on the AUR page. I don’t use protonVPN and don’t care to try…
commented on 2022-01-06 01:56
I fixed my issue by following https://github.com/ProtonVPN/linux-cli/issues/57#issuecomment-994694954https://github.com/ProtonVPN/linux-cli/issues/57#issuecomment-994694954
yay -Rs protonvpn
rm -rf ~/.cache/protonvpn
And then reinstalling protonvpn using pamac (Manjaro user here).
~~~
my bad for the confusion pacman/pamac, and I read your post as a “1. check that system is fully up to that 2. double check against repo (3 commands proposed)”. I did run the last command involving pamac (pamac build $(pacman -Qoq /usr/lib/python3.9)) and it now works!
Thank you very much for taking the time to explain this
Slightly off topic, I’m not sure to understand the underlying problem here. I also use protonvpn-cli on another computer that runs Fedora. It is installed through RPM and updated through dnf. Both computers use Python 3.10.1 and ProtonVPN CLI 3.11.0 (and the same packages versions), and on Fedora the update went without a hitch. What is the difference? Is is related to the job done by the AUR script vs the dnf update? Or does dnf rely on pre-compiled binaries? I’m interested by any explanation on this topic.
Well, RPM packages are build in RPM format which Fedora is using. Therefore, correct, the whole build process written in the RPM scripts differ from the Arch packages which Manjaro is using.
Also these RPM packages are maintained by Fedora or some other community and AUR is a user repository where the packages are maintained by the user him/herself, so if something changed in the newer kernel or in any distro update, which affects your installed software, then you either need to wait for this particular user to fix the issue in the software or you may fix it by yourself.
Thanks for trying, but I decided to simply install protonVPN on my cell phone then USB tether to the internet thru that and it’s working so I’m OK for now