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.

Thanks for the package!

However, it is uncommon for packages in Archlinux to enable or start services after they are installed. It goes against the "Simplicity" principle:

It does not add automation features such as enabling a service simply because the package was installed.

https://wiki.archlinux.org/title/Arch_Linux#Simplicity

Personally, I would just print instructions to start/enable the services in the post-install step.

I (successfully) installed the package on Manjaro 23.0.0

In case it's useful, I'll report here the warning and errors that appeared in during the building process :

[...]

>Installing JavaScript dependencies...
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: mini-create-react-context@0.4.1
npm WARN Found: react@18.2.0
npm WARN node_modules/react
npm WARN   react@"^18.2.0" from the root project
npm WARN   5 more (react-dom, react-redux, react-router, react-simple-maps, styled-components)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer react@"^0.14.0 || ^15.0.0 || ^16.0.0 || ^17.0.0" from mini-create-react-context@0.4.1
npm WARN node_modules/react-router/node_modules/mini-create-react-context
npm WARN   mini-create-react-context@"^0.4.0" from react-router@5.2.0
npm WARN   node_modules/react-router
npm WARN 
npm WARN Conflicting peer dependency: react@17.0.2
npm WARN node_modules/react
npm WARN   peer react@"^0.14.0 || ^15.0.0 || ^16.0.0 || ^17.0.0" from mini-create-react-context@0.4.1
npm WARN   node_modules/react-router/node_modules/mini-create-react-context
npm WARN     mini-create-react-context@"^0.4.0" from react-router@5.2.0
npm WARN     node_modules/react-router
npm WARN deprecated asar@3.2.0: Please use @electron/asar moving forward.  There is no API change, just a package name change
npm WARN deprecated electron-osx-sign@0.6.0: Please use @electron/osx-sign moving forward. Be aware the API is slightly different
npm WARN deprecated mini-create-react-context@0.4.1: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm WARN deprecated source-map-resolve@0.6.0: See https://github.com/lydell/source-map-resolve#deprecated

[...]

warning: variable does not need to be mutable
   --> talpid-wireguard/src/lib.rs:181:9
    |
181 |     let mut first_peer = config.peers.get_mut(0).expect("missing peer");
    |         ----^^^^^^^^^^
    |         |
    |         help: remove this `mut`
    |
    = note: `#[warn(unused_mut)]` on by default

[...]

==> Checking for packaging issues...
==> WARNING: Package contains reference to $srcdir

@Slug: You're missing the prerequisites for using the AUR. Please to not spam the same thing in multiple AUR package comments.

I had a problem trying to install on manjaro 23.0.0 today :

/var/tmp/pamac-build-jorgecpd/mullvad-vpn/PKGBUILD: line 47: patch: command not found

==> ERROR: A failure occurred in prepare(). Aborting...

EDIT : I found out meanwhile I lacked base-devel, found in official repositories (core) :

https://software.manjaro.org/package/base-devel

@yochananmarqos Sorry for the inconvenience.

Is it normal building mullvad-vpn uses almost 13GiB on disk ? And quite some time. Maybe I should just use mullvad-vpn-bin, if it is equivalent, but it seems a lot !

[SOLUTION] I accidentally chose 2) rustup on the build initiation instead of 1) rust. Doing sudo pacman -R rustup and then re-initiating the install (yay -Sua in my case) brought the prompt back and choosing the first option allowed the build to complete successfully.

User error, nothing more to see here. Will keep the post up for others who may have made the same mistake. [/SOLUTION]

[ORIGINAL ISSUE] Currently the Mullvad-vpn 2023.4-1 is not compiling with the following errors:

Compiling tonic v0.8.1
error[E0432]: unresolved imports `std::os::fd::AsRawFd`, `std::os::fd::RawFd`
  --> talpid-tunnel-config-client/src/lib.rs:24:27
   |
24 |     pub use std::os::fd::{AsRawFd, RawFd};
   |                           ^^^^^^^  ^^^^^ no `RawFd` in `os::fd`
   |                           |
   |                           no `AsRawFd` in `os::fd`

error[E0603]: module `fd` is private
   --> talpid-tunnel-config-client/src/lib.rs:24:22
    |
24  |     pub use std::os::fd::{AsRawFd, RawFd};
    |                      ^^ private module
    |
note: the module `fd` is defined here
   --> /home/anonymous/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/os/mod.rs:150:1
    |
150 | mod fd;
    | ^^^^^^

error[E0599]: no method named `as_raw_fd` found for struct `TcpSocket` in the current scope
   --> talpid-tunnel-config-client/src/lib.rs:181:50
    |
181 |                 try_set_tcp_sock_mtu(&addr, sock.as_raw_fd(), mtu);
    |                                                  ^^^^^^^^^ method not found in `TcpSocket`
    |
   ::: /home/anonymous/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/os/fd/raw.rs:57:8
    |
57  |     fn as_raw_fd(&self) -> RawFd;
    |        --------- the method is available for `TcpSocket` here
    |
    = help: items from traits can only be used if the trait is in scope
help: the following trait is implemented but not in scope; perhaps add a `use` for it:
    |
1   | use std::os::unix::io::AsRawFd;
    |

Some errors have detailed explanations: E0432, E0599, E0603.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `talpid-tunnel-config-client` due to 3 previous errors
warning: build failed, waiting for other jobs to finish...
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mullvad-vpn-exit status 4

Running latest Arch updates on 6.1.35-1-lts kernel.

Hi,

I’m having problems with my internet connection sometimes (often) disconnecting, while using Mullvad VPN. Problem always gets fixed when I reconnect, but it’s really annoying. I have feeling the problem has something to do with DNS, because the errors always say something linked to hostname. For example right now I can connect to all sites but Archlinux which gives me error:

"Hmm. We’re having trouble finding that site. We can’t connect to the server at bbs.archlinux.org."

When I reconnect Mullvad it works like a charm again…

Using Manjaro.

@nullpointer_ex: Please install the prerequisites for using the AUR.

Please add pkg-config to the dependencies.

Thanks you very much, package is a works works now ;)