Correct Dependencies for ArchLinux please

[schmitmd]

We are happy to answer your questions about the code or discuss technical ideas.

Please complete the following checklist (by adding [x]):

• [x] I have searched open and closed issues for duplicates
• [x] This isn't a feature request
• [x] This is not a report about my app not working as expected

---

It is not a safe assumption that a user has gnome-keyring or kwallet and uses NetworkManager as their main networking solution. A lot of Arch users set things up very minimally and do not want programs that they themselves don't have an explicit need for. If such programs are necessary for a tool they do have a need for, it is reasonable to expect that they will be installed as dependencies.

My experience in recent days is below. I hope it explains how I got here and why I think this relatively simple change is important:

1. If you use Netctl rather than NetworkManager, ProtonVPN does not work and the error output does not make it immediately clear that the problem is simply "you must use NetworkManager and no other networking solution for this to function correctly." (The now-deprecated aur/protonvpn-cli-ng package does not have this limitation, but does require root)
2. If you do not have nm-applet installed and running, both CLI and GUI do essentially the same. Minimal intelligible error output to explain why you're not getting a connection and instead just seeing a hung attempt.
3. If you've gotten past 1) and 2), but have not installed and started a system keyring (gnome-keyring or kwallet), you will get prompted for a password by nm-applet every time you try to connect. Entering your openvpn/ikev2 password works fine for this, but makes the whole thing pretty tedious. Installing, configuring, and starting a keyring gets you fully up and running in both GUI and CLI.

The above three steps took me a while to diagnose and fix. While all of the information I truly needed is specified in this post, almost all of it could have been avoided by simply adding a dependency entry for the package or putting in a clear error asking if these 3 things are in the necessary state.

Basically, can you please edit the PKGBUILD file(s) to include gnome-keyring or kwallet and nm-applet as required dependencies?

I realize I'm creating this issue semi-outside of the normal process flow and I apologize for that, but I really think this is a simple fix that would save a lot of people a lot of time. Relevant bug reports that helped me get here (in addition to the link above): #28 , #12, linux-cli#6.

[schmitmd]

Perhaps depend on org.freedesktop.secrets to cover "either-or" case for keyrings? Probably need to verify that KeepassXC works correctly as well for this; it is (the only, at the moment, afaict) another pkg that provides this.

At the least, any/all of these could be added to "optional deps"

[f2e6]

Thank you sooo much. nowhere in any documentation did it say this, and it never gave any useful output, it just hang. It requires gnome-keyring/kwallet and nm-applet to be installed and running.

[dron1885]

KeepassXC works correctly as well for this

Can verify, personally use KeppasXC Secret Service integration for over a year, and PVPN works like a charm with it.

[dron1885]

KeepassXC works correctly as well for this

Can verify, personally use KeppasXC Secret Service integration for over a year, and PVPN works like a charm with it.

~~It seems that about two months ago protonvpn GUI and cli stopped logging in with KeepassXC SS, only KDE and gnome are working.~~ It seems that it broke only on my main PC, on laptop it's still fine.

[Hielyr]

Basically, can you please edit the PKGBUILD file(s) to include gnome-keyring or kwallet and nm-applet as required dependencies?

Thank you very much for putting in the work to discover this.

I had the issue where without these I would attempt to connect the CLI or GUI would freeze for a bit, and then tell me "unknown reason occured."

I already had kwallet, but not nm-applet (repo name extra/network-manager-applet for anyone wondering).

Immediately after installing it and running nm-applet, the same thing would happen with the hang and the unhelpful message. After a reboot however, I was able to launch nm-applet and attempt a connection and it began working.