Package Details: mullvad-vpn 2024.8-1

Git Clone URL: https://aur.archlinux.org/mullvad-vpn.git (read-only, click to copy)
Package Base: mullvad-vpn
Description: The Mullvad VPN client app for desktop
Upstream URL: https://www.mullvad.net
Licenses: GPL-3.0-or-later
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 139
Popularity: 3.58
First Submitted: 2018-10-24 17:33 (UTC)
Last Updated: 2024-12-13 02:39 (UTC)

Pinned Comments

yochananmarqos commented on 2022-11-11 19:31 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)

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

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2024-06-06 22:09 (UTC) by yochananmarqos)

--> 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.

Latest Comments

1 2 3 4 5 6 .. 45 Next › Last »

Mr.Spock commented on 2024-12-04 19:39 (UTC)

New version 2024.8 is available. I got notified in the Mullvad VPN app about it.

yochananmarqos commented on 2024-11-26 16:56 (UTC)

@dreieck: mullvad-vpn-cli provides and conflicts with mullvad-vpn. Other packages should depend on mullvad-vpn so either can be chosen.

dreieck commented on 2024-11-25 23:53 (UTC)

Please add provides=("mullvad-vpn-cli=${pkgver}") sinc

  • it actually provides the CLI, too,
  • There is a package that depends on the CLI (mullvad-vpn-cli).

Regards!

khairizalkhalid commented on 2024-10-27 14:34 (UTC) (edited on 2024-10-28 02:24 (UTC) by khairizalkhalid)

Latest (d40056a) Mullvad Maybenot commit in maybenot.h does not have MaybenotAction_InjectPadding instead they use MaybenotAction_SendPadding_Body.

Upon scraping through maybenot commits from the one commented

_mn_commit=7254d70ea92e59778a99611999e4ed88a4aa821b  ## commit does not exist

found that we can use b06094e from the parent of parent 7254d above

_mn_commit=b06094e81701782d28cd2312f58e0654109d04ce

then switch comment on the other line

 "git+https://github.com/mullvad/maybenot.git#commit=${_mn_commit}"
  # "git+https://github.com/mullvad/maybenot.git"

I manage to build this successfully although I am not sure we should use this commit or what.

Edit: Or maybe need to raise issue for mullvad's wireguard-go because daita.go is calling on a different function?

Edit 2: Author fixed the pkgbuild with static maybenot commit.

christinryver commented on 2024-10-27 02:01 (UTC)

Same issue for me @TSTSTS

TSTSTS commented on 2024-10-26 01:03 (UTC)

I had the .npmrc file, and renamed it, as I did not know what else to do. Whether it exists or is renamed, I get the following error. Is there something I need to do separately with Rust or Go? I tried deleting the folder under .cache/paru/clone and rebooting. Thx!

error: failed to run custom build command for `wireguard-go-rs v0.0.0 (/home/user/.cache/paru/clone/mullvad-vpn/src/mullvadvpn-app/wireguard-go-rs)`

Caused by:
  process didn't exit successfully: `/home/user/.cache/paru/clone/mullvad-vpn/src/mullvadvpn-app/target/release/build/wireguard-go-rs-d40f5bfc91516353/build-script-build` (exit status: 1)
 wireguard-go/device/daita.go:287:21: could not determine kind of name for C.MaybenotAction_InjectPadding
Caused by:
      Failed to execute command: cd "./libwg" && CGO_ENABLED="1" GOARCH="amd64" GOOS="linux" "go" "build" "-v" "-o" "/home/user/.cache/paru/clone/mullvad-vpn/src/mullvadvpn-app/target/release/build/wireguard-go-rs-ad78211061f55ed7/out/libwg.a" "-buildmode" "c-archive" "--tags" "daita

SoftExpert commented on 2024-10-24 05:31 (UTC)

Latest package fails to build if there is an .npmrc file in the home directory.

Perhaps there is a need to build using a virtual environment set explicitely ? For example nodeenv ...

Computing checksum with sha256sum
Checksums matched!
Your user’s .npmrc file (${HOME}/.npmrc)
has a `globalconfig` and/or a `prefix` setting, which are incompatible with nvm.
Run `nvm use --delete-prefix v20.18.0` to unset it.
==> ERROR: A failure occurred in prepare().
    Aborting...

1 2 3 4 5 6 .. 45 Next › Last »