Package Details: proton-vpn-gtk-app 4.7.4-2

Git Clone URL: https://aur.archlinux.org/proton-vpn-gtk-app.git (read-only, click to copy)
Package Base: proton-vpn-gtk-app
Description: ProtonVPN GTK app, Maintained by Community
Upstream URL: https://github.com/ProtonVPN/proton-vpn-gtk-app
Keywords: protonvpn
Licenses: GPL3
Groups: ProtonVPN
Conflicts: protonvpn-gui, python-proton-client
Submitter: ali.molaei
Maintainer: ali.molaei
Last Packager: ali.molaei
Votes: 85
Popularity: 10.46
First Submitted: 2023-11-01 12:41 (UTC)
Last Updated: 2024-11-14 16:19 (UTC)

Pinned Comments

ali.molaei commented on 2024-11-14 16:25 (UTC)

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

stickyhands commented on 2024-02-09 23:53 (UTC) (edited on 2024-02-09 23:53 (UTC) by stickyhands)

@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.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 20 Next › Last »

Musikolo commented on 2024-09-24 00:27 (UTC) (edited on 2024-09-24 00:27 (UTC) by Musikolo)

@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:

I hope it helps.

omano commented on 2024-09-22 22:28 (UTC) (edited on 2024-09-22 22:31 (UTC) by omano)

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.

zeroconf commented on 2024-09-22 21:04 (UTC) (edited on 2024-09-22 21:05 (UTC) by zeroconf)

I removed completely:

yay -Rns proton-vpn-gtk-app

then installed again (whenever asked, answer to clean build all components)

yay -Sy proton-vpn-gtk-app

... and was installed and app starts. But this seems overall Proton apps or GNOME keyring issue, that after reboot cannot open former keyring and wants to create a new one. This repeats after every reboot. Even when to use no password, still cannot use same keyring and wants to create a new one after every reboot...

linuXus commented on 2024-09-20 21:00 (UTC)

@omano so should we just wait?

marie commented on 2024-09-20 18:26 (UTC)

@omano oh i see, thank you very much!

omano commented on 2024-09-20 17:12 (UTC)

@marie, that's not an issue, that is expected.

https://github.com/ProtonVPN/python-proton-vpn-network-manager/commit/028ff978f50cb31cca5b5bac15b5ffd4af5369cf

marie commented on 2024-09-20 16:17 (UTC)

Hello,

I wanted to report an issue I encountered after trying to update some Proton VPN packages. Here are the recent updates:

proton-vpn-gtk-app: 4.4.4-1 → 4.4.5-2 
python-proton-core: 0.2.0-1 → 0.3.3-1 
python-proton-vpn-api-core: 0.32.2-1 → 0.33.11-1 
python-proton-vpn-network-manager: 0.5.2-1 → 0.6.3-2

However, during installation, I encountered conflicts with the following packages:

python-proton-vpn-network-manager-0.6.3-2 and python-proton-vpn-network-manager-wireguard-0.4.1-1 are in conflict. Remove python-proton-vpn-network-manager-wireguard? [y/N]

python-proton-vpn-network-manager-0.6.3-2 and python-proton-vpn-network-manager-openvpn-0.1.0-1 are in conflict. Remove python-proton-vpn-network-manager-openvpn? [y/N]

Until now, I haven't had any issues with these WireGuard and OpenVPN packages, so I'm not sure if it's a good idea to remove them since they seems important? Any ideas on the subject?

Thank you in advance for your help!

zeroconf commented on 2024-09-19 09:03 (UTC)

Problem is, that when upgrading, there will be conflicts between wireguard related packages and upgrading failed. How to solve? Remove all and reinstall all again?

kt167 commented on 2024-09-18 21:40 (UTC)

@ali.molaei, awesome!!! Installing openvpn and networkmanager-openvpn did the trick. Thank you!