Package Details: mullvad-vpn 2020.6-1

Git Clone URL: (read-only, click to copy)
Package Base: mullvad-vpn
Description: The Mullvad VPN client app for desktop
Upstream URL:
Licenses: GPL3
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 36
Popularity: 2.40
First Submitted: 2018-10-24 17:33
Last Updated: 2020-10-20 15:38

Pinned Comments

yochananmarqos commented on 2019-12-07 17:44


This package will verify the signature of the git tag / commit. Developer keys are available here and instructions are here. See the PKGBUILD to determine which developer key you need.

Latest Comments

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

wilberfan commented on 2020-10-01 21:53

Any idea why this would be over 980MB when installed??

null_matter commented on 2020-07-17 14:21

I've been getting this error for a few months now when trying to update via yay, I've been forced to use the older version:

error: failed to get fern as a dependency of package mullvad-daemon v2020.5.0 (/home/umber/.cache/yay/mullvad-vpn/src/mullvadvpn-app/mullvad-daemon)

Caused by: failed to fetch

I tried installing rustup instead of rust, which started giving a different error, so I tried "rustup install stable", which went back to the first error.

I just decided to uninstall the package and use mullvad-vpn-bin instead but this is the first time I've had an aur issue I couldn't resolve.

nakor commented on 2020-07-15 15:46

FIXED The "S" option in makepkg -CSi was triggering the error. With makepkg -Ci it works.

When I try to update from 2020.4 to 2020.5 I get the following error, when running makepkg -CSi:

==> Making package: mullvad-vpn 2020.5-1 (Wed 15 Jul 2020 05:15:27 PM CEST) ==> Retrieving sources... -> Found ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped ... Passed ==> Verifying source file signatures with gpg... git repo ... SIGNATURE NOT FOUND git repo ... SIGNATURE NOT FOUND ==> ERROR: One or more PGP signatures could not be verified!

When I clone and verify it with git tag -v 2020.5 I get: object 0198a8b98683a768bb8306d7b8ead7f9a0ca114c type commit tag 2020.5 tagger Linus Färnstrand <> 1593072334 +0200

2020.5 gpg: Signature made Thu 25 Jun 2020 10:05:35 AM CEST gpg: using RSA key A6A4778440D27368967A7A3578CEAA8CB72E4467 gpg: Good signature from "Linus Färnstrand (code signing key) <>" [ultimate]

I also tried to import and trust every of Mullvads Developer keys. The error persists. Am I missing something obvious?

yochananmarqos commented on 2020-07-07 01:52

@digitalec: Oops. Apparently I pasted something in the wrong place while multiple PKGBUILDs were open. Fixed.

digitalec commented on 2020-07-07 01:33

Latest commit on 7/4 fails makepkg & pamac with:

error: pathspec 'tools/go-bindata' did not match any file(s) known to git

Rolling back the changes under prepare() to dist-assets/binaries resolved this.

andykluger commented on 2020-06-27 16:09

Thanks for maintaining this!

Please bump the pkgrel when pushing changes without changing the pkgver, so our tools will recognize an update.

yochananmarqos commented on 2020-06-26 22:02

@dahikino: Don't use bauh, use makepkg. If you're going to use an AUR helper, I suggest yay.

dahikino commented on 2020-06-26 21:15

from installing with bauh, i have a issue ==> Starting prepare()... Submodule 'dist-assets/binaries' ( registered for path 'dist-assets/binaries' Cloning into '/tmp/bauh/arch/build_1593205444/mullvad-vpn/src/mullvadvpn-app/dist-assets/binaries'... Submodule path 'dist-assets/binaries': checked out 'f9c55513f372de96223fad3ab6bd2aa78d517387' ==> Starting build()... Building Mullvad VPN 2020.5... build cache is required, but could not be located: GOCACHE is not defined and neither $XDG_CACHE_HOME nor $HOME are defined ==> ERROR: A failure occurred in build().

Strange, i have been able to install it with pamac but not with bauh !

yochananmarqos commented on 2020-06-25 22:22

I've disabled the check function for now, not sure what's causing the issue.

rfvgyhn commented on 2020-06-25 21:47

I have rust 1.44.1 and am also seeing the same error as @wazlecracker.