Arch Linux User Repository

I've added https://aur.archlinux.org/packages/python-proton-vpn-local-agent-bin as optional dependency, I worked on https://aur.archlinux.org/packages/python-proton-vpn-local-agent a bit to build it from source, but I have a weird issue with it so I'm not depending this package on that by default for now.

For those who know a bit about rust packaging, the issue with building from source for me is: - If I copy the build so file using cp command it works fine - If I package it (using install in PKGBUILD) and put the file there by installing the package using pacman, It doesn't work! although the files have the same checksum.

I have no idea why is that and am open to any help on https://aur.archlinux.org/packages/python-proton-vpn-local-agent package

@shoryuken thank you, that worked!

@ali.molaei I'm not sure of technicalities of dependencies, but if you cannot force network-manager-applet as a dependency I think you should at least pin some comment explaining that getting it might fix issues. As it stands I accidentally found the solution at other package page https://aur.archlinux.org/packages/protonvpn-cli#comment-951908, and only since it's the newest one.

@urbenlegend I think its an upstream issue, reported here waiting to see what they say: https://github.com/ProtonVPN/proton-vpn-gtk-app/issues/73

I am getting an error every time I switch to Wireguard or attempt to enable P2P:

Oct 17 09:18:12 arch-desktop protonvpn-app[28065]: 2024-10-17T16:18:12.368674 | proton.vpn.app.gtk.utils.exception_handler:190 | CRITICAL | APP:CRASH | Unexpected error.
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]: Traceback (most recent call last):
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:   File "/usr/lib/python3.12/concurrent/futures/_base.py", line 449, in result
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:     return self.__get_result()
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:            ^^^^^^^^^^^^^^^^^^^
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:   File "/usr/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:     raise self._exception
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:   File "/usr/lib/python3.12/site-packages/proton/vpn/app/gtk/controller.py", line 368, in save_and_update
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:     await self._api.fetch_certificate()
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]:           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Oct 17 09:18:12 arch-desktop protonvpn-app[28065]: AttributeError: 'ProtonVPNAPI' object has no attribute 'fetch_certificate'

When I try to do the port forwarding one-liner described here: https://protonvpn.com/support/port-forwarding-manual-setup/

it fails with the following error:

Thu Oct 17 09:20:04 AM PDT 2024
initnatpmp() returned 0 (SUCCESS)
using gateway : 10.2.0.1
sendpublicaddressrequest returned 2 (SUCCESS)
readnatpmpresponseorretry returned -7 (FAILED)
readnatpmpresponseorretry() failed : the gateway does not support nat-pmp
  errno=111 'Connection refused'
ERROR with natpmpc command

Manually importing Wireguard cert from the Proton VPN site works though, so there's something wrong with the app in this case.

you need update pkgver!

After updating to the latest releases of ProtonVPN-related packages, the following are no longer needed:

• python-proton-keyring-linux-secretservice
• python-proton-vpn-killswitch-network-manager
• python-proton-vpn-killswitch-network-manager-wireguard
• python-proton-vpn-logger

The following new library is needed:

• python-proton-vpn-local-agent

@XxTriviumxX As it says if you hover over the killswitch toggle, you can't change it whilst connected. Disconnect and go back in to the settings and you can turn it on.

the killswitch function doesnt work anymore... the toggle is grayed out and i still see the pvpn-killswitch-ipv6 connection. I tried disconnecting from proton vpn and i was still connected to my normal connection..

edit: Foxma's post did the trick

@Musikolo Yep I did that back when it was required. I also removed everything and did a Clean Build of proton-vpn-gtk-app so it wouldn't reinstall these unused packages now anyway. I can live with Wireguard (as an experimental feature from what I can see in Proton VPN settings) not working for now, I'll investigate later maybe something unrelated is messing with it.

@Omano, please sure you delete the python-proton-vpn-network-manager-openvpn and python-proton-vpn-network-manager-wireguard packages which are no longer required:

• https://aur.archlinux.org/cgit/aur.git/commit/?h=proton-vpn-gtk-app&id=1be5c69014279a09233a390de1967bfee6cb795f

I hope it helps.

I removed everything just for the sake of it, and reinstalled and Clean Build everything. My old keyring works, I just have to input the password. I had to delete local configuration folders ~/.config/Proton and ~/.config/protonvpn though because it would fail to connect (I quit Proton VPN, deleted the two folders, restarted and connected Proton VPN). Seems all good here, besides the issues with the local configuration I had to delete to be able to connect.

//EDIT: on mly side it seems to be WireGuard connection that fails, but with legacy OpenVPN UDP it works without issue.