The protonVPN app refuses to log in, here’s the journalctl:
The app launches, but trying to log in tells you “an error occurred”, unsure if these errors are related.
Unfortunately its hard to tell from that error alone. It seems to be a VK_ERROR_INITIALIZATION_FAILED in vkEnumeratePhysicalDevices, and the Vulkan docs aren’t helpful here as they don’t explain when this might happen…
Will have a further look.
1 Like
Oh, since you’re seeing some GUI I presume it was just some weird Vulkan thing. Can you launch it from a terminal to see the logs again? Does proton have a verbose logging flag or environment variable you can use?
EDIT: looks like maybe ~/.cache/protonvpn/logs contains logs too? Might be worth checking that.
EDIT 2: looks like the post that I saw showing the log location is old. Seems to be ~/.cache/Proton/VPN/logs/vpn-app.log now.
1 Like
I think your error might be related to this issue, the logs look similar.
3 Likes
This looks like a packaging bug?
EDIT: have you tried using the Proton CLI instead (think it is proton-vpn-cli?)?
EDIT 2: looks like the CLI also won’t work until this is merged and onto whatever branch you’re using: proton-vpn-cli: 0.1.9 -> 1.0.0, python3Packages.proton-vpn-api-core: 4.18.0 -> 4.19.1, proton-vpn: add api-core compatibility check by Bad3r · Pull Request #509227 · NixOS/nixpkgs · GitHub
1 Like
Glad to see it’s not an issue on my end 
Would downgrading the app maybe work in the meantime? Or do I just have to wait? I’m on unstable
You can wait. I’m not sure how to do it but you might be able to apply a patch but that might cause a local build and at some point you’ll probably want to remove the patch.
I’d recommend following the issue on GitHub and, once it’s merged, checking here to see if it’s reached unstable.
2 Likes
Okay, thank you so much for all the help!!! @magicquark too
The author of the PR to fix it has an overlay that can be used.
3 Likes
I’m being silly, you can use an overlay, add this (or something similar) to your configuration:
nixpkgs.overlays = [
(final: prev: {
pythonPackagesExtensions =
prev.pythonPackagesExtensions
++ [
(python-final: python-prev: {
proton-vpn-api-core = python-prev.proton-vpn-api-core.overrideAttrs (oldAttrs: {
version = "4.19.1";
src = prev.fetchFromGitHub {
owner = "ProtonVPN";
repo = "python-proton-vpn-api-core";
rev = "v4.19.1";
hash = "sha256-PD/UQ+BoDO6firhlBJDRNrtiHgnp+4uIb8j+egXqxPA=";
};
});
})
];
proton-vpn-cli = prev.proton-vpn-cli.overrideAttrs (oldAttrs: {
version = "1.0.0";
src = prev.fetchFromGitHub {
owner = "ProtonVPN";
repo = "proton-vpn-cli";
rev = "v1.0.0";
hash = "sha256-TIS1vhiOaX0ADKD1WRiPv+WYj0LwHmUuqyctygpaBho=";
};
postInstall =
(oldAttrs.postInstall or "")
+ ''
export HOME=$(mktemp -d)
export XDG_RUNTIME_DIR=$(mktemp -d)
'';
pythonImportsCheck = ["proton.vpn.cli"];
});
})
];
And this should do the trick (at least it is working on my machine). This is pretty much just overriding the current options with the ones from the PR.
4 Likes
Hello everyone
I am the author of the PR. It’s pretty surreal and awesome to see my work posted here as well as my personal config overlay workaround.
Hopefully, the PR is merged soon™️. If you know who can help getting it merged please ping them.
In the same PR, I addressed the root cause that introduced this issue. This hopefully means, this is the last time you will have to deal with it.
1 Like