Arch Linux User Repository

PSA: Upstream does not support building natively for ARM64, only cross-compiling. You can use mullvad-vpn-bin instead.

--> ALWAYS DO A CLEAN BUILD <--

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.

Please do not create upstream issues about the AUR package, they do not support it.

Got a bunch of errors with: rm: cannot remove '/var/tmp/pamac-build............

Had to manually remove these, then it worked: sudo rm -rf /var/tmp/pamac-build-evilmonkey/mullvad-vpn

@tirithen: Enabling a service symlinks it from /usr/lib/systemd/system/ to /etc/systemd/system/. DO NOT manually copy it there. I have no idea what is going on on your system, but it's not related to this package.

I'm getting a "Waiting for system service" message in the Mullvad GUI, on one of my Arch machines, even after enabling the service with systemctl.

I have previously used sudo cp /opt/Mullvad\ VPN/resources/mullvad-daemon.service /etc/systemd/system/mullvad-daemon.service to solve the problem but with the latest version 2022.5-2 this service file is no longer present.

Also now my internet becomes fully blocked without the ability to start the system service. Uninstalling and deleting all settings unlocks internet again.

How can I debug this to get the latest version of Mullvad up and running?

@Akari-chan: It was a typo, it's fixed now.

Hello, reporting from the latest update :

https://pastebin.com/HaxVzBf5

Is that one of the cases where you might want to try a clean build?

Anyway, if you need/want more information, let me know.

EDIT : I saw you addressed the problem, and indeed, it installed alright. KDEconnect works again!

package() fails with

==> Starting package()...
install: cannot stat 'dist-assets/linux/{mullvad-daemon}.service': No such file or directory
install: cannot stat 'dist-assets/linux/{mullvad-early-boot-blocking}.service': No such file or directory
==> ERROR: A failure occurred in package().
    Aborting...

Could you please not use multilayered {} brackets for install?

My bash seems to be not smart enough for them.

This fails on compiling talpid-types:

   Compiling talpid-types v0.1.0 (/mnt/slow/paru_clone_dir/mullvad-vpn/src/mullvadvpn-app/talpid-types)
error[E0658]: deriving `Default` on enums is experimental
   --> talpid-types/src/net/mod.rs:303:17
    |
303 | #[derive(Debug, Default, Copy, Clone, Eq, PartialEq, Deserialize, Serialize)]
    |                 ^^^^^^^
    |
    = note: see issue #86985 <https://github.com/rust-lang/rust/issues/86985> for more information
    = note: this error originates in the derive macro `Default` (in Nightly builds, run with -Z macro-backtrace for more info)

   Compiling translations-converter v0.1.0 (/mnt/slow/paru_clone_dir/mullvad-vpn/src/mullvadvpn-app/android/translations-converter)
For more information about this error, try `rustc --explain E0658`.
error: could not compile `talpid-types` due to previous error
warning: build failed, waiting for other jobs to finish...

EDIT: It was my outdated Rust. After a rustup update it's fine.

@wlhlm: The issue is resolved now.

@wlhlm: Well that's odd as Mullvad still uses those commands in their Debian prerm file in the 2022.2 and 2022.3.beta1 releases.

Uninstalling the package throws an error:

:: Processing package changes...
Making sure the Mullvad VPN daemon is stopped & disabled...
Removed "/etc/systemd/system/multi-user.target.wants/mullvad-daemon.service".
Removed "/etc/systemd/system/mullvad-daemon.service".
error: Found argument 'clear-history' which wasn't expected, or isn't valid in this context

USAGE:
    mullvad-setup <SUBCOMMAND>

For more information try --help
Failed to remove leftover WireGuard keys

clear-history has been renamed to remove-wireguard-key has been renamed to remove-device.