Package Details: mullvad-vpn 2022.1-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: GPL3
Submitter: gin078
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 93
Popularity: 7.17
First Submitted: 2018-10-24 17:33 (UTC)
Last Updated: 2022-03-28 20:59 (UTC)

Pinned Comments

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2020-11-17 03:00 (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.

Latest Comments

n8jadams commented on 2022-05-10 17:43 (UTC) (edited on 2022-05-10 19:43 (UTC) by n8jadams)

I'm getting this message when building

Removing old Rust build artifacts
error: failed to load manifest for workspace member `/home/nate/.cache/yay/mullvad-vpn/src/mullvadvpn-app/android/translations-converter`

Caused by:
  failed to parse manifest at `/home/nate/.cache/yay/mullvad-vpn/src/mullvadvpn-app/android/translations-converter/Cargo.toml`

Caused by:
  feature `edition2021` is required

  this Cargo does not support nightly features, but if you
  switch to nightly channel you can add
  `cargo-features = ["edition2021"]` to enable this feature
==> ERROR: A failure occurred in prepare().
    Aborting...

EDIT: Running rustup update stable or rustup default nightly && rustup update fixed it.

Aventinus commented on 2022-04-17 18:16 (UTC) (edited on 2022-04-17 18:19 (UTC) by Aventinus)

Package still fails to build for me. I get the following error:

npm ERR! code 1
npm ERR! path /home/aventinus/Downloads/mullvad-vpn/src/mullvadvpn-app/gui
npm ERR! command failed
npm ERR! command sh -c cross-env ELECTRON_BUILDER_ALLOW_UNRESOLVED_DEPENDENCIES=true electron-builder install-app-deps

manja2 commented on 2022-04-04 23:36 (UTC) (edited on 2022-04-04 23:41 (UTC) by manja2)

Thanks, I did that. But there's a new error. I tried uninstalling and re-installing, but got the same error.

   Compiling mullvad-rpc v0.1.0 (/var/tmp/pamac-build-user/mullvad-vpn/src/mullvadvpn-app/mullvad-rpc)
error[E0658]: use of unstable library feature 'array_methods'
   --> mullvad-rpc/src/lib.rs:530:51
    |
530 |             [StatusCode::CREATED, StatusCode::OK].as_slice(),
    |                                                   ^^^^^^^^
    |
    = note: see issue #76118 <https://github.com/rust-lang/rust/issues/76118> for more information

For more information about this error, try `rustc --explain E0658`.
error: could not compile `mullvad-rpc` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...

Tried installing mullvad-vpn-bin and that did work.

yochananmarqos commented on 2022-03-28 21:02 (UTC)

@manja2: I've re-implemented a fix for that, but you'll have to manually remove the gopath directory first:

sudo rm -rf /var/tmp/pamac-build-user/mullvad-
vpn/src/gopath/

manja2 commented on 2022-03-28 20:28 (UTC)

Can't update. Fails during build.

Building mullvad-vpn...
==> Making package: mullvad-vpn 2022.1-1 (Mon 28 Mar 2022 01:25:58 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Updating mullvadvpn-app git repo...
Fetching origin
  -> Updating mullvadvpn-app-binaries git repo...
Fetching origin
  -> Found mullvad-vpn.sh
==> Validating source files with sha256sums...
    mullvadvpn-app ... Skipped
    mullvadvpn-app-binaries ... Skipped
    mullvad-vpn.sh ... Passed
==> Verifying source file signatures with gpg...
    mullvadvpn-app git repo ... Passed
==> Removing existing $srcdir/ directory...
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/gotext.go': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/services/names.go': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/services/errors.go': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/docs/netquirk.md': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/docs/attacksurface.md': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/docs/buildrun.md': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/docs/adminregistry.md': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/docs/enterprise.md': Permission denied
rm: cannot remove '/var/tmp/pamac-build-user/mullvad-vpn/src/gopath/pkg/mod/golang.zx2c4.com/wireguard/windows@v0.3.14/COPYING': Permission denied
rm

Aithcy commented on 2022-03-15 15:17 (UTC) (edited on 2022-03-15 18:27 (UTC) by Aithcy)

During updating to 2022.1-1 the missing developer key belongs to Oskar. Hopefully this will save others doing the same trial and error exercise as me!

BTW is there a simple way to identify which one is missing? The only clue I had was 4B986EF5222BA1B810230C602F391DE6B00D619C

Edit: Sorry just seen it listed in PKGBUILD!

iyanmv commented on 2022-03-02 09:11 (UTC)

Why does makepkg -Cc fail to do a proper clean up? I only see this issue with this package (so far). Is it a makepkg bug or something that can be fixed in the PKGBUILD? Do we need files in src folder to have read-only permissions?

sylvain commented on 2022-03-02 08:26 (UTC) (edited on 2022-03-02 08:27 (UTC) by sylvain)

Clean build error:

error: target not found: libxcrypt-compat
 -> error fetching mullvad-vpn: fatal: destination path 'mullvad-vpn' already exists and is not an empty directory. 
     context: exit status 128

What worked for me was to delete the ~/.cache/yay/mullvad-vpn directory.

turbochamp commented on 2022-03-01 19:06 (UTC) (edited on 2022-03-01 19:09 (UTC) by turbochamp)

Clean build results in:

error: target not found: libxcrypt-compat
error: target not found: python-docutils
error: target not found: python-imagesize
error: target not found: python-snowballstemmer
error: target not found: python-sphinx-alabaster-theme
error: target not found: python-sphinxcontrib-applehelp
error: target not found: python-sphinxcontrib-devhelp
error: target not found: python-sphinxcontrib-htmlhelp
error: target not found: python-sphinxcontrib-jsmath
error: target not found: python-sphinxcontrib-qthelp
error: target not found: python-sphinxcontrib-serializinghtml
error: target not found: python-sphinx
 -> error fetching mullvad-vpn: fatal: destination path 'mullvad-vpn' already exists and is not an empty directory.
     context: exit status 128

yochananmarqos commented on 2022-02-22 17:16 (UTC)

@nylocx: glibc 2.35 no longer provides libcrypt.so.1, see FS#73799.

nylocx commented on 2022-02-22 13:01 (UTC)

The libxcrypt-compat build dependency can be dropped, at least for me it build with the default one provided by glibc.

nixAchurl commented on 2022-02-19 10:35 (UTC)

Build failed for me until I installed libxcrypt-compat as a dependency. From comments there, it seems there was a related issue with mullvad-vpn-beta.

arch-noob commented on 2022-01-27 22:46 (UTC) (edited on 2022-01-27 22:53 (UTC) by arch-noob)

Build is failing for me as well:

➜ mullvad-vpn git:(master) makepkg -si ==> Making package: mullvad-vpn 2021.6-2 (Thu 27 Jan 2022 05:43:42 PM) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin -> Updating mullvadvpn-app-binaries git repo... Fetching origin -> Found mullvad-vpn.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.sh ... Passed ==> Verifying source file signatures with gpg... mullvadvpn-app git repo ... Passed mullvadvpn-app-binaries git repo ... Passed ==> Extracting sources... -> Creating working copy of mullvadvpn-app git repo... fatal: bad object refs/remotes/origin/add-custom-resolver-docs error: /home/jack/aur-packages/mullvad-vpn/mullvadvpn-app did not send all necessary objects

==> ERROR: Failure while updating working copy of mullvadvpn-app git repo Aborting...

Uninstalled mullvad and removed log/cache/config just in case. Still not working

lunainvictum commented on 2022-01-19 00:06 (UTC)

Build fails:

Löse Unterschiede auf: 100% (1110/1110), fertig. -> mullvad-vpn.sh gefunden ==> Überprüfe source Dateien mit sha256sums... mullvadvpn-app ... Übersprungen mullvadvpn-app-binaries ... Übersprungen mullvad-vpn.sh ... Erfolg ==> Überprüfe Signaturen der Quell-Dateien mit gpg... mullvadvpn-app git repo ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 78CEAA8CB72E4467) mullvadvpn-app-binaries git repo ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel AEE9DECFD582E984) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! -> Fehler beim Herunterladen der Quellen: mullvad-vpn context: exit status 1

==> Erstelle Paket: mullvad-vpn 2021.6-2 (Mi 19 Jan 2022 01:04:35 CET) ==> Prüfe Laufzeit-Abhängigkeiten... ==> Prüfe Buildtime-Abhängigkeiten... ==> Empfange Quellen... -> Aktualisiere das mullvadvpn-app git Repo... Fordere an von origin -> Aktualisiere das mullvadvpn-app-binaries git Repo... Fordere an von origin -> mullvad-vpn.sh gefunden ==> Überprüfe source Dateien mit sha256sums... mullvadvpn-app ... Übersprungen mullvadvpn-app-binaries ... Übersprungen mullvad-vpn.sh ... Erfolg ==> Überprüfe Signaturen der Quell-Dateien mit gpg... mullvadvpn-app git repo ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 78CEAA8CB72E4467) mullvadvpn-app-binaries git repo ... FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel AEE9DECFD582E984) ==> FEHLER: Eine oder mehrere PGP-Signaturen konnten nicht überprüft werden! -> Fehler beim Ausführen: mullvad-vpn

even with clean build.

codicodi commented on 2021-12-22 09:38 (UTC)

The latest devtools update enables lto by default, so the build will fail for anyone building this package in a clean chroot. It would be really nice to disable lto in PKGBUILD.

Nocifer commented on 2021-12-18 12:09 (UTC)

@patlefort Thanks, I've had this same error for ages and disabling LTO fixed it at last. If you haven't already found a solution for selectively disabling it, you can do so on a per package basis by adding

options=(!lto)

to the PKGBUILD (provided you've globally enabled LTO via the OPTIONS array in makepkg.conf and not via a direct -flto flag). And in fact, if this incompatibility with LTO is standard with either Rust packages in general or with Mullvad in particular, maybe this option should be added to this package by default.

patlefort commented on 2021-11-29 02:15 (UTC)

I've narrowed my problem down to using -flto in my CFLAGS. I need to figure how to remove that flag for rust packages.

patlefort commented on 2021-11-19 03:34 (UTC)

Does not compile for me. Rust is updated with rustup update and it is a clean build.

error: linking with `cc` failed: exit status: 1
  |
  = note: "cc" "-m64" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.0.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.1.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.10.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.11.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.12.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.13.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.14.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.15.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.2.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.3.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.4.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.5.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.6.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.7.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.8.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.address_cache.51711df5-cgu.9.rcgu.o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26.2fq5o4btvmubi6xd.rcgu.o" "-Wl,--as-needed" "-L" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps" "-L" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/build/ring-42924d0655ff829f/out" "-L" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-Wl,-Bstatic" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libmullvad_rpc-c74f1b9fa03dc75d.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/liburlencoding-a44463868dfc2f0f.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libserde_json-9e59b6a906f1a4e3.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libryu-b899efa89cc786a4.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhyper_rustls-cce92a6a34156b82.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libct_logs-78f4dce390c06994.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/librustls_native_certs-df39df7774c28a6b.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libopenssl_probe-81cd929d0a1c3527.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtokio_rustls-e63bcbc609087b53.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/librustls-273e8e1c33763b44.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libsct-d0fa21b972a7923f.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libwebpki-72327b3e27c12ca2.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libring-7b70d7622a4cb43d.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libspin-fac74ef25175841b.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libuntrusted-0ac7da5706940b47.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures-91a0e7bff7f735d7.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_executor-73b89b1b9f3fd23d.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libmullvad_types-f5bb78daa70dcb22.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtalpid_types-0a36fd5ab8e3be12.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libbase64-4266b2e95d03dd55.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libx25519_dalek-1e114547858ffe30.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libcurve25519_dalek-eba765ad40370ae7.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libsubtle-c1fbb6064934da17.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libzeroize-9495f6ab1729beb3.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libdigest-d80b69b85aa1cbd5.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libgeneric_array-eeae485ca6bf88da.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtypenum-b6205d60026ddc2b.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libbyteorder-5407dfff1ed112c7.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/librand-1e81c16fa871dedd.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/librand_chacha-a7ae50d759745eb7.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libppv_lite86-825a815032e0c8d2.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/librand_core-98d45e2fb7aa0f4f.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libgetrandom-f8d58760188412ec.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libipnetwork-b9cb111d0c09dac5.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libregex-d3a344a59d7492eb.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libaho_corasick-9559e5bbb7bb6600.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libregex_syntax-bcd7d9cb8454f7ea.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhyper-a0ee89b28dc45d85.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libwant-c18aa0756bbfbafd.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtry_lock-35e5f4d6db6b58b9.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libsocket2-0e3547a12843a84b.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhttparse-7d795383eced879d.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libh2-3a27eee8fafbf1cb.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libindexmap-88985ac2249c6894.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhashbrown-0ae7faae6b8615f0.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtokio_util-f7125b300f7baa06.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtower_service-fadf3bfb461f4a56.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtracing-63f86e9ae88ccca6.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtracing_core-e7d41d4232a5910a.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/liblazy_static-003b530bbc96ec5d.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhttp_body-e07dc48d16b60d34.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_util-bfce8e327c2246ed.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_io-6ab1a4d96627be1c.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libslab-e35933f1df302b72.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_channel-909aa7654ee6f7f1.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_sink-6cc1ebe2043ceb7c.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_task-e4d9564292e1670e.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libpin_utils-d6325796c86937cc.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfutures_core-14ffe8b02b3194ca.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtokio-0cff10b560097861.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libsignal_hook_registry-cf09dcc8968b0a8e.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libnum_cpus-4ed1561a179381bd.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libmemchr-c0ddb5cc827038eb.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libonce_cell-221c2bdbb5ffc604.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libmio-e27a869af90df7af.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/liblog-b26fa174d7e564ca.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libcfg_if-0184e6893eb35a4a.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libpin_project_lite-b492a65436309b13.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhttpdate-3a477da8c5219b38.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libhttp-90466bb445a2ba71.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libitoa-97fb712595b73540.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libbytes-24d99bcbb0102ab9.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libfnv-203b6cf913745c5e.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libchrono-85810f96bd9ac7bb.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libserde-639c911b278eb83c.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libnum_integer-2eb3a178fc334bb6.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libnum_traits-9341d78b41fbd8c9.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libtime-b6c11bde3b494175.rlib" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/liblibc-bd862b436c20cfce.rlib" "-Wl,--start-group" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-65a28bf1738424c0.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libpanic_unwind-ba99c63b775f734c.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libminiz_oxide-2c795be2d1f43514.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libadler-4225fa5bc39268de.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libobject-a6e9f64eae6e45dd.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libmemchr-b1c963add6e8b853.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libaddr2line-541ca82647a7fb7c.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libgimli-b93187d0f71da706.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd_detect-12352e7b2d1a318e.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_demangle-3787a903f1bee791.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libhashbrown-fdd9bd7e7b7760b0.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_alloc-4274f5e0121314fe.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libunwind-496757222b2a1fa7.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcfg_if-e68feee69f5a82d8.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-5d6d15fab36665ef.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-10916d3506f78066.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_core-f6aebf5fbe06d09a.rlib" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-4e1b16fc9c111ada.rlib" "-Wl,--end-group" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-02203e01b7df4fdd.rlib" "-Wl,-Bdynamic" "-lgcc_s" "-lutil" "-lrt" "-lpthread" "-lm" "-ldl" "-lc" "-Wl,--eh-frame-hdr" "-Wl,-znoexecstack" "-L" "/home/elrick/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib" "-o" "/tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/address_cache-e77ac2561d884a26" "-Wl,--gc-sections" "-pie" "-Wl,-zrelro" "-Wl,-znow" "-nodefaultlibs"
  = note: /usr/bin/ld: /tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libring-7b70d7622a4cb43d.rlib(ring-7b70d7622a4cb43d.ring.132e4b18-cgu.1.rcgu.o): in function `ring::aead::chacha20_poly1305::chacha20_poly1305_seal':
          ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x24): undefined reference to `GFp_ia32cap_P'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0xbc): undefined reference to `GFp_poly1305_init'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0xe1): undefined reference to `GFp_poly1305_update'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x129): undefined reference to `GFp_poly1305_update'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x178): undefined reference to `GFp_poly1305_update'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x1be): undefined reference to `GFp_poly1305_update'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x1e5): undefined reference to `GFp_poly1305_update'
          /usr/bin/ld: ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_seal17h8e4935ec1909323dE+0x217): undefined reference to `GFp_poly1305_finish'
          /usr/bin/ld: /tmp/elrick-temp/makepkg/build/mullvad-vpn/src/mullvadvpn-app/target/release/deps/libring-7b70d7622a4cb43d.rlib(ring-7b70d7622a4cb43d.ring.132e4b18-cgu.1.rcgu.o): in function `ring::aead::chacha20_poly1305::chacha20_poly1305_open':
          ring.132e4b18-cgu.1:(.text._ZN4ring4aead17chacha20_poly130522chacha20_poly1305_open17h9d17f43eaffc93c4E+0x24): undefined reference to `GFp_ia32cap_P'
...

And more.

vaba commented on 2021-11-03 14:44 (UTC)

@TSTSTS I'd recommend uninstalling and re-installing mullvad-vpn (easiest solution). This is because the PKGBUILD file may not get updated through your package manager as the package version is the same for both commented and uncommented PGP key versions of the PKGBUILD. So you can either edit the PKGBUILD file yourself if you know where to find it, and then run an update; or delete it and run an update; or just uninstall and reinstall the package.

kamazeuci commented on 2021-11-01 20:22 (UTC)

thanks @lughnoone! that was it.

lughnoone commented on 2021-11-01 19:58 (UTC) (edited on 2021-11-01 20:00 (UTC) by lughnoone)

For EndeavourOS build issue, have a look at: https://github.com/mullvad/mullvadvpn-app/issues/2987

TL;DR: run 'rustup update' then rebuild.

kamazeuci commented on 2021-10-31 20:01 (UTC) (edited on 2021-10-31 20:02 (UTC) by kamazeuci)

Following error while trying to install in Endeavour OS:

   Compiling mullvad-rpc v0.1.0 (~/.cache/yay/mullvad-vpn/src/    mullvadvpn-app/mullvad-rpc)
error[E0658]: half-open range patterns are unstable
   --> talpid-core/src/tunnel/wireguard/wireguard_go.rs:344:9
    |
344 |         0.. => Ok(()),
    |         ^^^
    |
    = note: see issue #67264 <https://github.com/rust-lang/rust/issues/67264> for more information

error[E0658]: exclusive range pattern syntax is experimental
   --> talpid-core/src/tunnel/wireguard/wireguard_go.rs:344:9
    |
344 |         0.. => Ok(()),
    |         ^^^
    |
    = note: see issue #37854 <https://github.com/rust-lang/rust/issues/37854> for more information

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0658`.
error: could not compile `talpid-core`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mullvad-vpn

yochananmarqos commented on 2021-10-25 22:55 (UTC)

@TSTSTS: No. See the pinned comment?

TSTSTS commented on 2021-10-25 22:54 (UTC)

Does it take some time to replicate from source to wherever the packages come from? I am getting the error still.

yochananmarqos commented on 2021-10-25 22:24 (UTC)

@tsweet64: Detected by what? AUR helpers are indeed helpful, but not supported.

Apparently no one has been able to update from 2021.4-1 to 2021.5-1 due to the issue I just fixed, so bumping the pkgrel accomplishes nothing. Just build it.

tsweet64 commented on 2021-10-25 22:02 (UTC)

Had the same issue, thanks. You may want to consider bumping the pkgrel number so that the updated PKGBUILD is detected.

yochananmarqos commented on 2021-10-25 21:46 (UTC)

@TSTSTS: Oops, forgot to uncomment the PGP key. Try it again now.

TSTSTS commented on 2021-10-25 20:04 (UTC)

I am having some issues. When running Paru, I get

==> Making package: mullvad-vpn 2021.5-1 (Mon 25 Oct 2021 02:56:03 PM CDT) ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin -> Updating mullvadvpn-app-binaries git repo... Fetching origin -> Found mullvad-vpn.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.sh ... Passed ==> Verifying source file signatures with gpg... mullvadvpn-app git repo ... Passed mullvadvpn-app-binaries git repo ... FAILED (invalid public key 8339C7D2942EB854E3F27CE5AEE9DECFD582E984) ==> ERROR: One or more PGP signatures could not be verified! error: failed to download sources for 'mullvad-vpn-2021.5-1': error: packages failed to build: mullvad-vpn-2021.5-1

I tried following the steps here https://mullvad.net/en/help/verifying-signatures/ and got

~ gpg2 --verify MullvadVPN-*.deb.asc gpg: assuming signed data in 'MullvadVPN-2021.5_amd64.deb' gpg: Signature made Mon 25 Oct 2021 05:03:16 AM CDT gpg: using RSA key CA83A46153BC58D69518ED49A26581F219C8314C gpg: BAD signature from "Mullvad (code signing) admin@mullvad.net" [ultimate] ➜ ~

Is this something I am doing wrong?

thx

Vedro commented on 2021-10-21 21:20 (UTC)

OS: Manjaro (fresh install, updated) Installer: Yay

getting following error:

Copying binaries
Updating relay list...
    Finished release [optimized] target(s) in 0.09s
     Running `target/release/relay_list`
Error: Failed to fetch relay list
Caused by: Hyper error
Caused by: error trying to connect: tls handshake eof
Caused by: tls handshake eof
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mullvad-vpn

yochananmarqos commented on 2021-10-13 22:47 (UTC)

@brunomiguel: GitHub has been having issues today.

brunomiguel commented on 2021-10-13 20:18 (UTC)

For some reason, I can build it. From the error, I assume it isn't connecting to Github, but I can connect to it

[20:54:38] Starting 'builder-linux'...
  • electron-builder  version=22.10.5 os=5.10.72-1-lts
  • packaging       platform=linux arch=x64 electron=11.2.3 appOutDir=/home/brunomiguel/userrepository/pkgbuild/mullvad-vpn/src/mullvadvpn-app/dist/linux-unpacked
  • Unpacking electron zip  zipPath=undefined
  ⨯ Get "https://github.com/electron/electron/releases/download/v11.2.3/electron-v11.2.3-linux-x64.zip": dial tcp: lookup github.com on [::1]:53: read udp [::1]:57619->[::1]:53: read: connection refused
github.com/develar/app-builder/pkg/download.(*Downloader).follow.func1
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:206
github.com/develar/app-builder/pkg/download.(*Downloader).follow
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:234
github.com/develar/app-builder/pkg/download.(*Downloader).DownloadNoRetry
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:128
github.com/develar/app-builder/pkg/download.(*Downloader).Download
    /Volumes/data/Documents/app-builder/pkg/download/downloader.go:112
github.com/develar/app-builder/pkg/electron.(*ElectronDownloader).doDownload
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:192
github.com/develar/app-builder/pkg/electron.(*ElectronDownloader).Download
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:177
github.com/develar/app-builder/pkg/electron.downloadElectron.func1.1
    /Volumes/data/Documents/app-builder/pkg/electron/electronDownloader.go:73
github.com/develar/app-builder/pkg/util.MapAsyncConcurrency.func2
    /Volumes/data/Documents/app-builder/pkg/util/async.go:68
runtime.goexit
    /usr/local/Cellar/go/1.15.5/libexec/src/runtime/asm_amd64.s:1374  
[20:54:39] 'builder-linux' errored after 576 ms
[20:54:39] Error: /home/brunomiguel/userrepository/pkgbuild/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/home/brunomiguel/userrepository/pkgbuild/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:476:26)
    at ChildProcess.emit (node:events:369:20)
    at ChildProcess.emit (node:domain:532:15)
    at maybeClose (node:internal/child_process:1067:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
    at Process.callbackTrampoline (node:internal/async_hooks:132:14)
[20:54:39] 'pack-linux' errored after 23 s

iyanmv commented on 2021-08-31 07:39 (UTC)

I think there is an issue with the systemd service file. Checking journalctl I saw this line: app-mullvad\x2dvpn@autostart.service: Failed at step EXEC spawning /opt/Mullvad: No such file or directory

iyanmv commented on 2021-08-17 11:03 (UTC)

Hi, thanks for maintaining this package! Just a question: is auto start working for all of you? Option within the program doesn't seem to work for me, and also if I put add it manually on the Plasma autostart settings is ignored. I would like the tray to be loaded automatically after I log in.

Thanks for the help!

tsangares commented on 2021-07-25 05:42 (UTC)

Hi i get:

:: (1/1) Parsing SRCINFO: mullvad-vpn

:: PGP keys need importing:
 -> EA0A77BF9E115615FC3BD8BC7653B940E494FE87, required by: mullvad-vpn
==> Import? [Y/n] y
:: Importing keys with gpg...
gpg: keyserver receive failed: No name
problem importing keys

Failing to build. (yes doing cleanbuild)

jwan commented on 2021-07-13 14:11 (UTC)

One of the links in the pinned comment says I need to install gnupg2. However, Pacman says that package does not exist!

a.liedtke commented on 2021-05-13 17:55 (UTC)

makepkg -i

ends for me with: runtime/cgo

runtime/cgo

cc1: error: unknown pass checking specified in '-fenable'

Any hints on that?

XenGi commented on 2021-05-08 23:00 (UTC) (edited on 2021-05-08 23:01 (UTC) by XenGi)

Package build fine but the daemon doesn't start. Dmesg shows:

cgroup: Disabled controller 'net_cls'

journal says:

May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::version][INFO] Starting mullvad-daemon - 2021.3 2021-04-27
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon][INFO] Logging to /var/log/mullvad-vpn
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::rpc_uniqueness_check][DEBUG] Failed to locate/connect to another daemon instance, assuming there isn't one
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon][INFO] Management interface listening on /var/run/mullvad-vpn
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_rpc::address_cache][DEBUG] Loading API addresses from "/var/cache/mullvad-vpn/api-ip-address.txt"
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_rpc::address_cache][DEBUG] Using API address: 193.138.218.71:444
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::relays][DEBUG] Reading relays from /var/cache/mullvad-vpn/relays.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::relays][DEBUG] Reading relays from /opt/Mullvad VPN/resources/relays.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::relays][INFO] Initialized with 769 cached relays from 2021-05-09 00:57:48.000
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::settings][INFO] Loading settings from /etc/mullvad-vpn/settings.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::version_check][DEBUG] Loading version check cache from /var/cache/mullvad-vpn/version-info.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::version_check][WARN] Error: Unable to load cached version info
May 09 00:58:09 nyu mullvad-daemon[41289]: Caused by: Failed to open app version cache file for reading
May 09 00:58:09 nyu mullvad-daemon[41289]: Caused by: No such file or directory (os error 2)
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::account_history][INFO] Opening account history file in /etc/mullvad-vpn/account-history.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon][INFO] Loaded cached target state "Unsecured" from /var/cache/mullvad-vpn/target-start-state.json
May 09 00:58:09 nyu mullvad-daemon[41289]: [talpid_core::firewall][INFO] Resetting firewall policy
May 09 00:58:09 nyu mullvad-daemon[41289]: [talpid_core::firewall::imp][DEBUG] Removing table and chain from netfilter
May 09 00:58:09 nyu mullvad-daemon[41289]: [talpid_core::tunnel_state_machine][DEBUG] Exiting tunnel state machine loop
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon][ERROR] Error: Unable to initialize daemon
May 09 00:58:09 nyu mullvad-daemon[41289]: Caused by: Unable to initialize split tunneling
May 09 00:58:09 nyu mullvad-daemon[41289]: Caused by: Unable to initialize net_cls cgroup instance
May 09 00:58:09 nyu mullvad-daemon[41289]: Caused by: EINVAL: Invalid argument
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon][DEBUG] Process exiting with code 1
May 09 00:58:09 nyu mullvad-daemon[41289]: [mullvad_daemon::management_interface][INFO] Management interface shut down

Same behaviour with the bin package.

wwklnd commented on 2021-04-30 01:08 (UTC) (edited on 2021-04-30 01:08 (UTC) by wwklnd)

So, I can't seem to update this application and it fails with this error:

error[E0658]: `if` is not allowed in a `const`
  --> mullvad-types/src/wireguard.rs:10:49
   |
10 |   pub const DEFAULT_ROTATION_INTERVAL: Duration = if cfg!(target_os = "android") {
   |  _________________________________________________^
11 | |     Duration::from_secs(4 * 24 * 60 * 60)
12 | | } else {
13 | |     Duration::from_secs(7 * 24 * 60 * 60)
14 | | };
   | |_^
   |
   = note: see issue #49146 <https://github.com/rust-lang/rust/issues/49146> for more information

   Compiling talpid-platform-metadata v0.1.0 (/var/tmp/pamac-build-william/mullvad-vpn/src/mullvadvpn-app/talpid-platform-metadata)
   Compiling htmlize v0.5.0
error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `mullvad-types`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...

Any idea what the issue might be?

arkhetypos commented on 2021-04-28 22:07 (UTC) (edited on 2021-04-28 22:08 (UTC) by arkhetypos)

@yochananmarqos: replaced rustup with rust and it worked. Thanks!

yochananmarqos commented on 2021-04-28 21:51 (UTC)

@arkhetypos: Make sure you're using the repo rust package to build. Also see the pinned comment.

arkhetypos commented on 2021-04-28 21:19 (UTC) (edited on 2021-04-28 21:19 (UTC) by arkhetypos)

Is this just me? Sry if so

error[E0277]: can't compare `Vec<std::net::IpAddr>` with `[std::net::IpAddr]`
  --> talpid-core/src/dns/linux/systemd_resolved.rs:87:40
   |
87 |                     if current_servers != *dns_state.set_servers {
   |                                        ^^ no implementation for `Vec<std::net::IpAddr> == [std::net::IpAddr]`
   |
   = help: the trait `PartialEq<[std::net::IpAddr]>` is not implemented for `Vec<std::net::IpAddr>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
error: could not compile `talpid-core`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
error making: mullvad-vpn

yochananmarqos commented on 2021-04-21 15:43 (UTC)

@Anteduck: That's why it's best to build in a clean chroot so user / system variables don't interfere. However, that flag is part of Rust package guidelines, so I added it.

Anteduck commented on 2021-04-21 11:14 (UTC)

The PKGBUILD doesn't work if you have a different target directory specified in .cargo/config. Here's a patch that explicitly specifies the target directory:

--- PKGBUILD.old    2021-04-21 20:10:03.284860579 +0900
+++ PKGBUILD    2021-04-21 20:04:14.458205960 +0900
@@ -39,7 +39,7 @@
    sed -i "s/'deb', 'rpm'/'deb'/g" gui/tasks/distribution.js

    echo "Removing old Rust build artifacts"
-   cargo clean
+   cargo clean --target-dir target

    export GOPATH="$srcdir/gopath"
    go clean -modcache
@@ -76,13 +76,13 @@

    echo "Building Rust code in release mode using $RUSTC_VERSION..."

-   cargo build --release --locked
+   cargo build --release --locked --target-dir target

    mkdir -p dist-assets/shell-completions
    for sh in bash zsh fish; do
        echo "Generating shell completion script for $sh..."
-       cargo run --bin mullvad --release --locked -- shell-completions "$sh" \
-           dist-assets/shell-completions/
+       cargo run --bin mullvad --release --locked --target-dir target -- \
+           shell-completions "$sh" dist-assets/shell-completions/
    done

    echo "Copying binaries"
@@ -99,10 +99,10 @@
    done

    echo "Updating relay list..."
-   cargo run --bin relay_list --release > dist-assets/relays.json
+   cargo run --bin relay_list --release --target-dir target > dist-assets/relays.json

    echo "Updating API address cache..."
-   cargo run --bin address_cache --release > dist-assets/api-ip-address.txt
+   cargo run --bin address_cache --release --target-dir target > dist-assets/api-ip-address.txt

    # Build Electron GUI app
    pushd gui
@@ -115,7 +115,7 @@

 #check() {
 #  cd "$srcdir/mullvadvpn-app"
-#  cargo test --release --locked
+#  cargo test --release --locked --target-dir target
 #
 #  cd gui
 #  npm test

yochananmarqos commented on 2021-04-19 01:50 (UTC)

@Hubro: I updated the requirements to match Mullvad.

FYI, Node.js 10 is EOL at the end of the month.

andykluger commented on 2021-04-19 01:11 (UTC)

@hubro

So try a newer nodejs like erbium or whatever

Hubro commented on 2021-04-18 23:48 (UTC)

@andykluger

Yep, still happens after clearing ~/.npm. I've tried installing this package with paru, still same error. I haven't tried installing it completely manually yet.

Which nodejs-providing package do you have installed?

$ pacman -Q | grep -i node
node-gyp 7.1.2-1
nodejs-lts-dubnium 10.24.0-1
perl-tree-dag-node 1.31-2

I noticed node-gyp is installed as a system package, so I tried to delete it. Turns out it's a required dependency of npm:

$ pacman -R node-gyp
checking dependencies...
error: failed to prepare transaction (could not satisfy dependencies)
:: removing node-gyp breaks dependency 'node-gyp' required by npm

AlexWayfer commented on 2021-04-18 08:57 (UTC)

I tried 3 times, with clean build:

~/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui ~/.cache/yay/mullvad-vpn/src/mullvadvpn-app
Installing JavaScript dependencies...
npm ERR! code 1
npm ERR! path /home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install
npm ERR! socket hang up
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@0.15.0
npm ERR! node-pre-gyp info using node@15.14.0 | linux | x64
npm ERR! node-pre-gyp WARN Using needle for node-pre-gyp https download 
npm ERR! node-pre-gyp info check checked for "/home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/bin/grpc_tools.node" (not found)
npm ERR! node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp ERR! install error 
npm ERR! node-pre-gyp ERR! stack Error: socket hang up
npm ERR! node-pre-gyp ERR! stack     at connResetException (node:internal/errors:642:14)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.socketCloseListener (node:_http_client:445:25)
npm ERR! node-pre-gyp ERR! stack     at TLSSocket.emit (node:events:381:22)
npm ERR! node-pre-gyp ERR! stack     at node:net:666:12
npm ERR! node-pre-gyp ERR! stack     at TCP.done (node:_tls_wrap:577:7)
npm ERR! node-pre-gyp ERR! System Linux 5.11.14-arch1-1
npm ERR! node-pre-gyp ERR! command "/usr/bin/node" "/home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp" "install"
npm ERR! node-pre-gyp ERR! cwd /home/alex/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! node-pre-gyp ERR! node -v v15.14.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.15.0
npm ERR! node-pre-gyp ERR! not ok

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/alex/.cache/yay/mullvad-vpn/src/npm-cache/_logs/2021-04-18T08_56_15_597Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: mullvad-vpn

Goatroth commented on 2021-04-16 04:02 (UTC) (edited on 2021-04-16 04:08 (UTC) by Goatroth)

I get this error when trying to build in a VM, doesn't matter which VM hypervisor I use:

[23:00:54] 'builder-linux' errored after 12 s
[23:00:54] Error: /home/goatroth/git/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/app-builder-bin/linux/x64/app-builder exited with code ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
    at ChildProcess.<anonymous> (/home/goatroth/git/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/builder-util/src/util.ts:243:14)
    at Object.onceWrapper (node:events:476:26)
    at ChildProcess.emit (node:events:369:20)
    at ChildProcess.emit (node:domain:532:15)
    at maybeClose (node:internal/child_process:1067:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
    at Process.callbackTrampoline (node:internal/async_hooks:132:14)
[23:00:54] 'pack-linux' errored after 33 s
==> ERROR: A failure occurred in build().
    Aborting...

andykluger commented on 2021-04-15 19:18 (UTC)

@Hubro

Have you tried clearing your ~/.npm junk?

Which nodejs-providing package do you have installed?

Do you have the same problem when installing the normal way, without yay?

yochananmarqos commented on 2021-04-14 15:16 (UTC)

@beckab: Ah, good point. I'll just drop them.

pkap commented on 2021-04-14 15:05 (UTC)

@yochananmarqos It seems neither networkmanager nor resolvconf are necessary as dependencies. The Mullvad app checks how DNS is set on your system and acts accordingly. If resolvconf/networkmanager/systemd-resolved are not used it manually writes /etc/resolv.conf.

See here: https://github.com/mullvad/mullvadvpn-app#environment-variables-controlling-the-execution

Thank you for your work packaging this!

madhogs commented on 2021-04-05 09:26 (UTC)

@yochananmarqos I use systemd-resolved for DNS, which does suggest in the wiki page to use a resolveconf provider for compatibility reasons. It does work without it for me though.

yochananmarqos commented on 2021-04-04 23:13 (UTC)

@madhogs: Hmm, that's interesting. According to the merged commit I linked below, it specifically looks for org.freedesktop.NetworkManager which is part of networkmanager.

What do you have installed for DNS management if not resolveconf?

quantized commented on 2021-04-04 23:10 (UTC) (edited on 2021-04-04 23:11 (UTC) by quantized)

@yochananmarqos:

Right, I have the version 2021.2-1 at the moment. I use Wireguard, and since the time I switched to iwd, I got rid of networkmanager completely, with all its dependencies.

@madhogs: I don't have libnm, so apparently, it's not needed for mullvad-vpn.

madhogs commented on 2021-04-04 22:49 (UTC)

@yochananmarqos Just want to add I also use iwd and 2021.2-1 is able to create a wireguard interface just fine without networkmanager. I do have libnm installed however, perhaps that is all that is needed? (It also seems to work fine for me without resolvconf, but maybe I don't understand the issue below)

yochananmarqos commented on 2021-04-04 22:03 (UTC) (edited on 2021-04-04 22:09 (UTC) by yochananmarqos)

@quantized: I added networkmanger with 2021.2-2, you must still have 2021.2-1 installed. However, you just helped me realize all that's required is resolvconf for DNS management. 2021.2-3 is updated to reflect that.

EDIT: Do you use OpenVPN or Wireguard? It turns out networkmanager is required for created a Wireguard interface (wg-mullvad).

quantized commented on 2021-04-04 21:32 (UTC) (edited on 2021-04-04 21:32 (UTC) by quantized)

Hi,

Is networkmanager a new dependency? I currently have the same 2021.2 version, but it's not dependent on networkmanager. Curious, because I use iwd instead of networkmanager, and mullvad-vpn worked just fine with it...

yochananmarqos commented on 2021-04-03 16:33 (UTC)

@AverytheFurry: Done.

@Cant.Install: Read the pinned comment.

@Hubro: Can't reproduce it.

Hubro commented on 2021-04-03 04:09 (UTC)

I am baffled, I have no clue why my install is failing. I have been unable to update this package for months now. I get this error every time:

Installing JavaScript dependencies...
npm WARN EBADENGINE Unsupported engine { package: 'mullvad-vpn@2021.2.0',
npm WARN EBADENGINE   required: { node: '>=12', npm: '>=6.12' },
npm WARN EBADENGINE   current: { node: 'v10.24.0', npm: '7.8.0' } }
npm ERR! code 6
npm ERR! path /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! command failed
npm ERR! command sh -c node-pre-gyp install
npm ERR! node-pre-gyp info it worked if it ends with ok
npm ERR! node-pre-gyp info using node-pre-gyp@0.15.0
npm ERR! node-pre-gyp info using node@10.24.0 | linux | x64
npm ERR! node-pre-gyp WARN Using needle for node-pre-gyp https download 
npm ERR! node-pre-gyp info check checked for "/home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/bin/grpc_tools.node" (not found)
npm ERR! node-pre-gyp http GET https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp http 301 https://node-precompiled-binaries.grpc.io/grpc-tools/v1.9.1/linux-x64.tar.gz
npm ERR! node-pre-gyp ERR! Completion callback never invoked! 
npm ERR! node-pre-gyp ERR! System Linux 5.11.11-arch1-1
npm ERR! node-pre-gyp ERR! command "/usr/bin/node" "/home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp" "install"
npm ERR! node-pre-gyp ERR! cwd /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
npm ERR! node-pre-gyp ERR! node -v v10.24.0
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.15.0
npm ERR! node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
npm ERR! node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
npm ERR! node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tomas/.cache/yay/mullvad-vpn/src/npm-cache/_logs/2021-04-03T04_06_32_624Z-debug.log

I am deleting the source directory before installation:

rm -rf .cache/yay/mullvad-vpn

And I'm choosing to "cleanBuild" the package in yay when installing. I don't see anybody else in the comments with the same problem. Any ideas?

Cant.Install commented on 2021-04-02 23:42 (UTC)

Help? This thing can't install even if I use do 'git clone' and 'makepkg -si' thing. I'm a total beginner with this OS, I really hope I don't offend anyone because I don't know what to do or what's going on, but it's been over a month since I've popped this in a virtual machine and barely anything works.

:: Resolving dependencies... :: There are 4 providers available for mullvad-vpn: :: Repository AUR: 1) mullvad-vpn 2) mullvad-vpn-beta 3) mullvad-vpn-beta-bin 4) mullvad-vpn-bin Enter a number (default=1): 1 :: Calculating conflicts... :: Calculating inner conflicts...

Aur (1) mullvad-vpn-2021.2-1

:: Proceed to review? [Y/n]: y

:: Downloading PKGBUILDs... PKGBUILDs up to date nothing new to review :: keys need to be imported: 8339C7D2942EB854E3F27CE5AEE9DECFD582E984 wanted by: mullvad-vpn-2021.2-1 EA0A77BF9E115615FC3BD8BC7653B940E494FE87 wanted by: mullvad-vpn-2021.2-1 :: import? [Y/n]: y gpg: keyserver receive failed: Server indicated a failure fetching devel info... ==> Making package: mullvad-vpn 2021.2-1 (Fri 02 Apr 2021 07:38:03 PM EDT) ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin -> Updating mullvadvpn-app-binaries git repo... Fetching origin -> Found mullvad-vpn.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.sh ... Passed ==> Verifying source file signatures with gpg... mullvadvpn-app git repo ... FAILED (unknown public key 78CEAA8CB72E4467) mullvadvpn-app-binaries git repo ... FAILED (unknown public key AEE9DECFD582E984) ==> ERROR: One or more PGP signatures could not be verified! :: Packages failed to build: mullvad-vpn-2021.2-1

AverytheFurry commented on 2021-04-02 23:16 (UTC)

the issue was uninstalling gnome uninstalled networkmanager, probably should be a dependency.

AverytheFurry commented on 2021-04-02 23:09 (UTC)

After uninstalling gnome, I am getting "failed to set system DNS" - maybe there's a dependency not listed?

yochananmarqos commented on 2021-03-18 16:20 (UTC)

@rbarrett: I may need to add networkmanager as a dependency. See if using it resolves your issues.

rabarrett commented on 2021-03-18 16:10 (UTC) (edited on 2021-03-18 17:21 (UTC) by rabarrett)

I've been having ongoing--yet intermittent--problems with mullvad-vpn working. I suspect they're similar to what others are describing here, but I'm hoping my additional input will help pinpoint what seems to be affecting so many people.

When I try to use the app to establish a vpn connection, it responds "Blocked Connection" (and my awesome wm icon shows a green lock with a red circle in the middle). This happens even if I use wireguard only, instead of automatic or openvpn (under the app's advanced settings).

Also note that I have already tried the suggestions others have posted here: -I always do a clean build -I've tried the beta--no difference -I've enabled and started systemd-resolved, installed systemd-resolveconf and linked /etc/resolv.conf to /run/systemd/resolv/stub-resolv.conf -none of these seem to help (though when I first set up systemd-resolved, after a reboot it worked for a while)

However, it happens only intermittently. Sometimes after having problems (and just running without the vpn for a while), I'll reboot and it will work. It will keep working for day or even a week or so (with some reboots) and then later it stops working again.

I believe each time it has stopped working, it is after I run a pacman update (and AUR update with yay) and the kernel has been updated. The update has to run hooks for my wireless kernel: the broadcom-wl-dkms module, which has long-standing issues that were eventually solved with the new hook system. So the first idea to consider is that the problem is related to

1) broadcom-wl-dkms and hooks

Another possibility that might help isolate the issue is that I'm not using network manager. I'm using

2) netctl

Note: Just today I tried using NetworkManager instead. It appears to work; but given the intermittent nature of the problem, I'm not sure yet.

Is there any journal info or other data I could collect to help troubleshoot it?

yochananmarqos commented on 2021-03-12 12:24 (UTC)

@madhogs: No, unfortunately not. Only files installed during package installation can be tracked.

madhogs commented on 2021-03-12 10:42 (UTC)

Is there a way of making this package track the folder /etc/mullvad-vpn/ ? For some reason pacman does not track this folder and thinks it does not belong to any package, even though mullvad-vpn creates this itself.

Autodidaddy commented on 2021-03-03 15:49 (UTC)

Changed back from beta to this doing a clean build. I was having the ""failed to set system DNS" error when trying to connect using openvpn. Both beta and 2021.2 are perfectly usable but only using wireguard.

patlefort commented on 2021-02-25 17:42 (UTC) (edited on 2021-02-25 17:43 (UTC) by patlefort)

Does not build for me:

Copying binaries
Updating relay list...
    Finished release [optimized] target(s) in 0.10s
     Running `target/release/relay_list`
Request timed out
==> ERROR: A failure occurred in build().
    Aborting...

dahikino commented on 2021-02-23 22:27 (UTC)

i can't make it work with the problem of DNS not found and i try to compile it , one time on two i have have this :


  Compiling mullvad-rpc v0.1.0 (/home/david/repos/mullvad-vpn/src/mullvadvpn-app/mullvad-rpc) error[E0277]: 

the trait bound `std::net::SocketAddr: std::cmp::Ord` is not satisfied    --> mullvad-rpc/src/address_cache.rs:170:23
    |
170 |             addresses.sort();
    |                       ^^^^ the trait `std::cmp::Ord` is not implemented for `std::net::SocketAddr`

error[E0277]: the trait bound `std::net::SocketAddr: std::cmp::Ord` is not satisfied
   --> mullvad-rpc/src/address_cache.rs:173:28
    |
173 |             current_sorted.sort();
    |                            ^^^^ the trait `std::cmp::Ord` is not implemented for `std::net::SocketAddr`

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0277`.
error: could not compile `mullvad-rpc`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERREUR : Une erreur s’est produite dans build().
    Abandon…

whaler commented on 2021-02-15 23:23 (UTC) (edited on 2021-02-15 23:39 (UTC) by whaler)

@eaburto Thanks, I know. I just installed mullvad-vpn-cli 2020.7 and it is working - even after restarts! :)

systemd says:

$ systemctl -all | grep mullvad

sys-devices-virtual-net-wg\x2dmullvad.device loaded active plugged /sys/devices/virtual/net/wg-mullvad
sys-subsystem-net-devices-wg\x2dmullvad.device loaded active plugged /sys/subsystem/net/devices/wg-mullvad
mullvad-daemon.service loaded active running Mullvad VPN daemon

So, again, I wonder why mullvad-vpn 2021.1-1, the GUI version, refuses to find a/the DNS address.

I am beginning to think there is something wrong in Arch, or my setup. I am using KDE, FWIW.

Hubro commented on 2021-02-15 08:56 (UTC)

@yochananmarqos I do a clean install every time

yochananmarqos commented on 2021-02-14 23:50 (UTC)

@Hubro: Do a clean install like the pinned comment says.

@FIN4LSHAR3: It's not related to system package versions, it's an internal node module. See the error again:

/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp

Hubro commented on 2021-02-14 23:39 (UTC)

@FIN4LSHAR3 I tried upgrading to the most recent version globally:

sudo npm install -g @mapbox/node-pre-gyp

But that didn't make any difference. I assume the build process installs dependencies locally, so it doesn't matter what I install globally.

FIN4LSHAR3 commented on 2021-02-14 14:06 (UTC)

@Hubro Have you tried upgrading node-pre-gyp? You're running version 0.15.0 while the current version is 1.0.0

https://github.com/mapbox/node-pre-gyp

FIN4LSHAR3 commented on 2021-02-14 13:51 (UTC)

My mullvad client (v. 2021.1) went on a reconnecting loop this morning (wireguard). Took me some time to figure out that apparently the client failed to generate a new wireguard key, after generating one manually in the gui it's working fine again. Maybe this helps someone.

With regards to openvpn: I'm still having problems getting openvpn to run properly. I noticed that for some reason mullvad uses the wg-mullvad (wireguard) adapter to connect via openvpn, is that normal? Also I either get some error "failed to set system DNS" or it connects but I can only reach DNS servers (eg. ping 8.8.8.8 works, but ping www.google.com doesn't) Using firefox I can only connect to websites by setting up the mullvad socks proxy ("10.8.0.1:1080"), otherwise I can't connect.
I manly use wireguard so it's not really urgent, but maybe someone here can make sense of this mess.

Hubro commented on 2021-02-14 13:25 (UTC)

Failing to install for me :(

> grpc-tools@1.9.1 install /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
> node-pre-gyp install

node-pre-gyp WARN Using needle for node-pre-gyp https download 
node-pre-gyp ERR! Completion callback never invoked! 
node-pre-gyp ERR! System Linux 5.10.14-arch1-1
node-pre-gyp ERR! command "/usr/bin/node" "/home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools/node_modules/.bin/node-pre-gyp" "install"
node-pre-gyp ERR! cwd /home/tomas/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/grpc-tools
node-pre-gyp ERR! node -v v10.23.2
node-pre-gyp ERR! node-pre-gyp -v v0.15.0
node-pre-gyp ERR! This is a bug in `node-pre-gyp`.
node-pre-gyp ERR! Try to update node-pre-gyp and file an issue if it does not help:
node-pre-gyp ERR!     <https://github.com/mapbox/node-pre-gyp/issues>
npm ERR! code ELIFECYCLE
npm ERR! errno 6
npm ERR! grpc-tools@1.9.1 install: `node-pre-gyp install`
npm ERR! Exit status 6
npm ERR! 
npm ERR! Failed at the grpc-tools@1.9.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/tomas/.cache/yay/mullvad-vpn/src/npm-cache/_logs/2021-02-14T13_23_58_046Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
error making: mullvad-vpn

eaburto commented on 2021-02-13 20:30 (UTC)

@whaler I suspect "the unit" refers to the systemd unit. You can check if it's started using "systemctl status mullvad-daemon" in the terminal. And if it's not started you can use "sudo systemctl enable --now mullvad-daemon" to start it and make it start in every boot.

john-doe commented on 2021-02-13 07:43 (UTC) (edited on 2021-02-13 07:44 (UTC) by john-doe)

@eaburto @andykluger @yochananmarqos

In continuation to my previous comment. I would be grateful to any one who could clearly state the steps (not just instructions but ACTUAL COMMANDS) so that newbies like me could upgrade to Mullvad & Network-Manager.

Thanks for support & cooperation!

whaler commented on 2021-02-13 05:10 (UTC)

So, I followed the tips from @andykluger and @yochananmarqos. Enabled and started systemd-resolved, installed systemd-resolveconf and linked /etc/resolv.conf to /run/systemd/resolv/stub-resolv.conf. No dice.

I then removed mullvad-vpn and reinstalled with git. Mullvad immediately worked fine, but, again, after a restart it is, assumably, not able to make a valid DNS lookup. It says "the unit" is not connected. What am I missing or doing wrong?

whaler commented on 2021-02-12 23:19 (UTC)

@eaburto Your solution worked instantly, but only for the current session. After a restart, Mullvad VPN complains "the unit" is not connected. Also the "Reconnect" in the Mullvad icon is grayed out. Is there a fix other than switching to systemd-resolved or trying the beta version?

john-doe commented on 2021-02-12 11:46 (UTC)

I'm facing problems in three cases

  1. with older or latest version of network manager & latest mullvad-vpn. The error throws up -- cannot establish a tunnel (wireguard) and in openvpn the wait is endless.
  2. in latest version of everything -- same problem.
  3. after systemd-resolved and symlink still nothing works with the latest version. Even the older version of mullvad throws up DNS error while pacman upgrade.

Please update me in this concern. BTW even beta is of no help.

Autodidaddy commented on 2021-02-08 20:45 (UTC)

I was going to say I had to switch to the beta cause I was having very weird DNS issues where mullvad did make a connection, I could browse the web through TOR, but everything else was offline. Don't have systemd-resolved installed, beta works indeed.

Zenzio commented on 2021-02-03 12:35 (UTC) (edited on 2021-02-03 12:36 (UTC) by Zenzio)

@eaburto Thank you, this worked for me with the newest version of NetworkManager and Mullvad-VPN-beta. I was hesitant to switch to systemd-resolved. No more downgrading Networkmanager for me! :)

eaburto commented on 2021-02-03 03:35 (UTC) (edited on 2021-02-05 01:18 (UTC) by eaburto)

For the people not wanting to change to systemd-resolved I just found another approach. You can still use openresolv with no problem adding this line to /etc/resolvconf.conf:

dynamic_order="tap[0-9]* tun[0-9]* vpn vpn[0-9]* wg-mullvad wg[0-9]* ppp[0-9]* ippp[0-9]*"

It's just the default value with the mullvad wireguard interface name added so it consider it a higher priority when adding the DNS servers to /etc/resolv.conf

cedricbambooza commented on 2021-01-13 22:41 (UTC)

@andykluger did it like you described it and it works now, thanks ^^

cedricbambooza commented on 2021-01-13 17:02 (UTC) (edited on 2021-01-13 17:13 (UTC) by cedricbambooza)

@null_matter ya your probably right ;D actually it's sad because i think many comment here but don't reach the Mullvad People :)

null_matter commented on 2021-01-13 16:26 (UTC)

cedricbambooza, I'm also just an arch user that has paid for the VPN and is upset it doesn't work sometimes :D

You can see the package maintainer above, but they are just another arch user as well as far as I know. You would want to contact Mullvad directly to give them feedback, I doubt any employee would read this package page. cheers

cedricbambooza commented on 2021-01-13 16:06 (UTC) (edited on 2021-01-13 16:17 (UTC) by cedricbambooza)

So is anyone working on getting this issue fixed?

only because I'm getting to see a pattern in this failures happing, first with the DNS not working with OpenVPN due to some network related changes from a kernel update i guess, that got fixed... and now again DNS issues with the whole thing not working at all also because of some update, this time probably networkmanager. what is going on?

not to be mean or something, but I've paid good money for a year of VPN Usage, but that doesn't help when it's broken most of the time...

and telling people to use the beta version can't be the fix either. why call it beta then if it is always the go to solution when the main release is broken?

when you need people to test your beta, just say so :) but don't force us to use it just by not fixing the main release, please.

for some reason i can't get electron to download during build of the beta package, it takes ages and stops before finishing. So even if tried i can't run beta at the moment...

andykluger commented on 2021-01-11 19:25 (UTC) (edited on 2021-01-11 19:27 (UTC) by andykluger)

I have not had any issues since the last release, using systemd-resolved.

That is, I have:

  • systemd-resolved enabled
  • systemd-resolvconf installed
  • /etc/resolv.conf symlinked to /run/systemd/resolv/stub-resolv.conf

For more info: https://wiki.archlinux.org/index.php/Systemd-resolved

Zenzio commented on 2021-01-11 19:16 (UTC)

Sadly no. I already tried reinstalling openresolv. It's curious how the proven solutions for this problem don't seem to work for me. I tried the different beta-packages (2020.8-beta2 still is the package I am using now) and openresolv was and is installed. Only downgrading NetworkManager seems to work for me. It's a minor annoyance for now, but I still wonder what's going on here.

hal_yawn commented on 2021-01-11 19:07 (UTC)

I did not have it previously installed. idk if re-installing will have the same effect.

Zenzio commented on 2021-01-11 15:08 (UTC)

Do you guys mean openresolv wasn't installed on your systems before? Because I have had it all along and it's only working for me when I downgrade networkmanager...

hal_yawn commented on 2021-01-11 15:05 (UTC)

Installing openresolv and rebooting fixed this for me as well.

stmrllr commented on 2021-01-10 13:04 (UTC)

Installing openresolv fixed this issue for me and now my /etc/resolv.conf is updating correctly.

Zenzio commented on 2021-01-10 11:53 (UTC) (edited on 2021-01-10 11:55 (UTC) by Zenzio)

Just a quick update: Installing the beta (bin or non-bin) did not help in my case. Though I am using the non-bin beta now. I ended up downgrading openresolv and networkmanager (not sure which one of those helped). If anybody notices this issue being fixed kindly drop a word about it here, please. Thank you!

Zenzio commented on 2021-01-09 19:07 (UTC)

Mhh. I did everything the way you did it with the tiny exception that I manually removed mullvad-vpn before installing the beta (yay -Rns mullvad-vpn). Rebooting hasn't helped for now. If nothing changes I might try doing the same and installing the bin package this time... Anyway, thank you for your help.

null_matter commented on 2021-01-09 18:12 (UTC)

Yes I had to reboot my system. I use yay as my AUR helper. When I installed mullvad-vpn-beta-bin it prompted me to remove the mullvad-vpn-bin package, which I did.

Then it didn't work, and I went to bed, and in the morning after rebooting it worked. So maybe reboot?

Zenzio commented on 2021-01-09 17:12 (UTC) (edited on 2021-01-09 17:14 (UTC) by Zenzio)

So are you saying switching to the beta helped you? But not at first? I just switched to it (the non-bin package 2020.8.beta2-2) and for now it doesn't seem to help. Do I need to do something besides uninstalling the stable version and a clean build of the beta and restarting my system? Did you do something else before it started working again?

stmrllr commented on 2021-01-09 15:14 (UTC) (edited on 2021-01-09 15:29 (UTC) by stmrllr)

I'm having the same problem with DNS, /etc/resolv.conf doesn't get updated with the Mullvad name server. It's kind of complicated bug at the moment, since the GUI isn't starting either. It shows in processes but I can't get it to show on desktop.

null_matter commented on 2021-01-09 14:34 (UTC) (edited on 2021-01-09 14:35 (UTC) by null_matter)

edit: this is a fix for the DNS issue

I requested feedback via the app and they told me to download the beta: "Please try our latest beta which should resolve this issue in most cases."

I installed the AUR package mullvad-vpn-beta-bin which is 2020.8.beta2-1 and at first it didn't work, I rebooted this morning and now it's working. I'm using the bin version because for some reason I can't build the mullvad package from source. So I would try to install mullvad-vpn-beta or mullvad-vpn-beta-bin and reboot. Cheers!

Zenzio commented on 2021-01-09 13:53 (UTC)

I don't know if I should post about this here. But as the post before mine states: After the system update (networkmanager and openresolv got updated) my system can't connect to anything anymore while Mullvad-VPN is active. It's fine while Mullvad-VPN is not connected. Is this a bug with one of the updated packages? Any pointers?

cedricbambooza commented on 2021-01-09 08:40 (UTC) (edited on 2021-01-09 08:40 (UTC) by cedricbambooza)

Mullvad VPN via App not working after Update of NetworkManager and reboot....

I'm getting an ERR_Name not Resolved Message when opening the Browser, I close the Mullvad App and voila I can visit kernel.org

Mullvad VPN App also connects to the servers just fine, "simply" DNS request don't seem to work anymore.

Rehls commented on 2020-11-27 06:22 (UTC)

Installing via makepkg worked w/o issue for me, thanks!

Yay just would not let me get past the PGP key importing step, even when I had manually added them: ==> :: (1/1) Parsing SRCINFO: mullvad-vpn

:: PGP keys need importing:
 -> EA0A77BF9E115615FC3BD8BC7653B940E494FE87, required by: mullvad-vpn
 -> 8339C7D2942EB854E3F27CE5AEE9DECFD582E984, required by:               mullvad-vpn
==> Import? [Y/n] 
:: Importing keys with gpg...
gpg: keyserver receive failed: General error
problem importing keys

andykluger commented on 2020-11-27 05:37 (UTC)

@Rehls

  1. What about without yay?

  2. Can you post the error?

Rehls commented on 2020-11-26 22:14 (UTC) (edited on 2020-11-26 22:15 (UTC) by Rehls)

Tried following all the steps outlined below by m00-aur and the mullvad install instructions and I'm still running into signing issues. All the keys are imported/signed, yet I'm still being asked for them on install while using yay.

gpg --list-keys
pub   rsa4096 2019-10-01 [SC]
  8339C7D2942EB854E3F27CE5AEE9DECFD582E984
uid           [  full  ] David Lönnhager (code signing) 
<david.l@mullvad.net>
sub   rsa4096 2019-10-01 [E]

pub   rsa4096 2015-07-08 [SC]
  EA0A77BF9E115615FC3BD8BC7653B940E494FE87
uid           [  full  ] Linus Färnstrand (code signing key) 
<linus@mullvad.net>
sub   rsa4096 2015-07-08 [E]
sub   rsa4096 2016-10-31 [S]

pub   rsa4096 2016-10-27 [SC]
  A1198702FC3E0A09A9AE5B75D5A1D4F266DE8DDF
uid           [ultimate] Mullvad (code signing) <admin@mullvad.net>
sub   rsa4096 2016-10-27 [E]
sub   rsa4096 2016-10-27 [S]

hal_yawn commented on 2020-11-24 22:20 (UTC) (edited on 2020-11-24 22:31 (UTC) by hal_yawn)

Newby here - I've followed the instructions linked in the pinned comment, downloaded and trusted the code signing key .asc and I'm still getting the following error when I run makepkg: https://pastebin.com/raw/8Gtr4eJM

SOLVED m00-aur's comment below fixed the issue.

takouhai commented on 2020-11-22 01:42 (UTC)

If you're having issues with compilation, Go might need some flags permitted to allow the build to start.

go build runtime/cgo: invalid flag in go:cgo_ldflag: -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now ==> ERROR: A failure occurred in build().

To fix, export the following flags to your environment:

$ export CGO_LDFLAGS_ALLOW=".*"

Solution found here: https://forum.golangbridge.org/t/invalid-flag-in-cgo-ldflags/10020/2

m00-aur commented on 2020-11-16 20:02 (UTC) (edited on 2020-11-16 20:02 (UTC) by m00-aur)

if having issues with the pgp keys, simply import the necessary keys:

gpg2 --keyserver pool.sks-keyservers.net --recv-keys 8339C7D2942EB854E3F27CE5AEE9DECFD582E984

gpg2 --keyserver pool.sks-keyservers.net --recv-keys EA0A77BF9E115615FC3BD8BC7653B940E494FE87

if still having issues, trust the main code signing with:

wget https://mullvad.net/media/mullvad-code-signing.asc

gpg2 --import mullvad-code-signing.asc

gpg2 --edit-key A1198702FC3E0A09A9AE5B75D5A1D4F266DE8DDF

trust

5

y

q

r381581 commented on 2020-11-08 18:28 (UTC) (edited on 2020-11-08 18:33 (UTC) by r381581)

@cardinal

Terminal: 1. git clone https://aur.archlinux.org/mullvad-vpn.git 2. cd mullvad-vpn 3. ls (list packages) 4. less PKGBUILD (check integrity) 5. makepkg -C (C = Clean build) * >>...<< 6. sudo pacman -U mullvad-vpn-***.tar.xz

*>> (I have to) change permissions to "chrome-sandbox" while building as non-root user<< ..you have to wait when this package is built.. > open in file manager and wait for it. Then: 5.1 sudo -s 5.2 chown root:$USER /home/ * /mullvad-vpn/src/mullvadvpn-app/gui/node_modules/electron/dist/chrome-sandbox 5.3 chmod 4755 /home/ * /mullvad-vpn/src/mullvadvpn-app/gui/node_modules/electron/dist/chrome-sandbox <<

If you want it really clean, first: sudo pacman -Rs mullvad-vpn, sudo rm -rf /var/log/mullvad-vpn/, sudo rm -rf /var/cache/mullvad-vpn/, sudo rm -rf /etc/mullvad-vpn, rm /home/***/.config/Mullvad VPN, then pacman -U

cardinal commented on 2020-11-02 12:19 (UTC)

can anyone help to build here,cant do it im newbie

deesnook commented on 2020-10-21 20:12 (UTC)

@andykluger Yeah, I read it right after I posted my comment. sorry for the dumb question

TeoBigusGeekus commented on 2020-10-21 19:34 (UTC) (edited on 2020-10-22 21:54 (UTC) by TeoBigusGeekus)

During update:

PGP keys need importing:

-> 8339C7D2942EB854E3F27CE5AEE9DECFD582E984, required by: mullvad-vpn

==> Import? [Y/n]

:: Importing keys with gpg...

gpg: keyserver receive failed: General error

problem importing keys

Trying with gpg:

$gpg --recv-keys 8339C7D2942EB854E3F27CE5AEE9DECFD582E984

gpg: keyserver receive failed: General error

EDIT: Nevermind, got it done with gpg2 --keyserver pool.sks-keyservers.net --recv-keys 8339C7D2942EB854E3F27CE5AEE9DECFD582E984

andykluger commented on 2020-10-21 17:59 (UTC)

@deesnook Please see the sticky comment here for how-to links.

deesnook commented on 2020-10-21 17:04 (UTC)

@noch918 How would you do this and, just out of curiosity, why hasn't this problem occured before?

noch918 commented on 2020-10-21 13:10 (UTC)

@dahikino you must add developers key and trust them, then the error will go away

dahikino commented on 2020-10-21 10:46 (UTC)

Vérification of signatures for file sources via gpg… mullvadvpn-app git repo ... Done mullvadvpn-app-binaries git repo ... Failed (public key unknown AEE9DECFD582E984)

dahikino commented on 2020-10-21 10:38 (UTC)

error One or more PGP signatures could not be verified.

Can you verify ?

yochananmarqos commented on 2020-10-02 02:43 (UTC) (edited on 2020-10-02 02:44 (UTC) by yochananmarqos)

@wilberfan: That's the installed size of go and rust, not mullvad-vpn. Yay will prompt you to remove build dependencies after.

wilberfan commented on 2020-10-02 02:27 (UTC)

@yochananmarqos The output from the yay command:

$ yay -S mullvad-vpn :: There are 4 providers available for mullvad-vpn: :: Repository AUR 1) mullvad-vpn 2) mullvad-vpn-beta 3) mullvad-vpn-beta-bin 4) mullvad-vpn-bin

Enter a number (default=1): :: Checking for conflicts... :: Checking for inner conflicts... [Repo Make:2] go-2:1.15.2-1 rust-1:1.46.0-1 [Aur:1] mullvad-vpn-2020.5-1

==> Remove make dependencies after install? [y/N] y :: Downloaded PKGBUILD (1/1): mullvad-vpn 1 mullvad-vpn (Build Files Exist) ==> Diffs to show? ==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4) ==> :: (1/1) Parsing SRCINFO: mullvad-vpn resolving dependencies... looking for conflicting packages...

Packages (2) go-2:1.15.2-1 rust-1:1.46.0-1

Total Download Size: 195.94 MiB Total Installed Size: 977.87 MiB

:: Proceed with installation? [Y/n]

yochananmarqos commented on 2020-10-02 01:52 (UTC)

@wilberfan: Where are you getting that from? It's 240.42 MiB on my system.

wilberfan commented on 2020-10-01 21:53 (UTC)

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

null_matter commented on 2020-07-17 14:21 (UTC)

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 https://github.com/rust-lang/crates.io-index

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 (UTC) (edited on 2020-07-21 16:47 (UTC) by nakor)

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 mullvad-vpn.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.sh ... 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 https://github.com/mullvad/mullvadvpn-app.git and verify it with git tag -v 2020.5 I get: object 0198a8b98683a768bb8306d7b8ead7f9a0ca114c type commit tag 2020.5 tagger Linus Färnstrand <linus@mullvad.net> 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) <linus@mullvad.net>" [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 (UTC) (edited on 2020-07-07 01:53 (UTC) by yochananmarqos)

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

gradiian commented on 2020-07-07 01:33 (UTC)

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 (UTC)

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 (UTC)

@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 (UTC) (edited on 2020-06-26 23:05 (UTC) by dahikino)

from installing with bauh, i have a issue ==> Starting prepare()... Submodule 'dist-assets/binaries' (https://github.com/mullvad/mullvadvpn-app-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 (UTC) (edited on 2020-06-25 22:22 (UTC) by yochananmarqos)

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

rfvgyhn commented on 2020-06-25 21:47 (UTC)

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

aurjin commented on 2020-06-25 18:56 (UTC)

Also experiencing the same issue as @wazlecracker

tuse commented on 2020-06-25 18:54 (UTC)

Having the same issue as @wazlecracker. I'm on Manjaro and Rust is at 1.44.0 in the repos, so I guess I just have to wait? (Yes I'm a newbie)

yochananmarqos commented on 2020-06-25 17:09 (UTC)

@wazlecracker: I had that issue with rust 1.44.0, I believe. Make sure you have 1.44.1 installed.

commented on 2020-06-25 16:30 (UTC)

Failing to build both within pamac and cloning then makepkg -si. Get these errors:

test routing::imp::imp::test::test_drop ... FAILED
test routing::imp::imp::test::test_drop_in_executor ... FAILED

failures:

---- routing::imp::imp::test::test_drop stdout ----
thread 'routing::imp::imp::test::test_drop' panicked at 'Failed to initialize route manager: ExclusionsRoutingTableSetup(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })', talpid-core/src/routing/linux.rs:920:13

---- routing::imp::imp::test::test_drop_in_executor stdout ----
thread 'routing::imp::imp::test::test_drop_in_executor' panicked at 'Failed to initialize route manager: ExclusionsRoutingTableSetup(Os { code: 13, kind: PermissionDenied, message: "Permission denied" })', talpid-core/src/routing/linux.rs:908:27
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
routing::imp::imp::test::test_drop
routing::imp::imp::test::test_drop_in_executor

test result: FAILED. 17 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '-p talpid-core --lib'

yochananmarqos commented on 2020-06-08 20:07 (UTC)

@atti_simon: I figured something like that would come up. I would open an issue upstream to ask about supporting arm64.

atti_simon commented on 2020-06-08 18:46 (UTC) (edited on 2020-06-08 19:23 (UTC) by atti_simon)

@yochananmarqos: Sorry for the late reply, I have now tried the aarch64 test package provided earlier. The build aborts with the following error:

   Compiling mullvad-cli v2020.4.0 (/home/xxxxxx/aur/mullvad-vpn-test/src/mullvadvpn-app/mullvad-cli)
error: could not find native static library `wg`, perhaps an -L flag is missing?

error: aborting due to previous error

error: could not compile `talpid-core`.

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed
==> ERROR: A failure occurred in build().
    Aborting...

yochananmarqos commented on 2020-06-08 16:33 (UTC)

@bbaserdem: I commented out the NPM test.

bbaserdem commented on 2020-06-08 06:12 (UTC)

@yochananmarqos; the test requires an attached X session. In clean chroot; I would not run makepkg as the logged in user (chroot does not have an active display) hence the gui runtime tests fail. It's not that I don't need the gui; it's that the gui test line cannot be run from within a chroot. (maybe it can with some dummy x session; but I have no idea how/if it can be done)

Regular users can run it; cause i assume running makepkg as your own user pulls in the XAUTHORITY variable.

Also; understandable regression from electron 8; i have another package that is affected.

yochananmarqos commented on 2020-05-25 00:18 (UTC)

@happybike: There is no signature file for this package as it pulls from verified git commits, not binaries. The same signing keys are used.

happybike commented on 2020-05-24 19:26 (UTC)

I'm an Arch noob trying to wrap my mind around securely downloading packages from the AUR. I don't quite understand how to verify the software using the gpg key because when I downloaded this package via git, it didn't download the signature file. The only .asc I see in the package is the code signing key. Thanks for any help you may provide!

yochananmarqos commented on 2020-05-20 21:28 (UTC)

@atti_simon: Try this test package and let me know if that does the trick.

atti_simon commented on 2020-05-20 09:39 (UTC) (edited on 2020-05-20 10:02 (UTC) by atti_simon)

Hello! Just for info, for anyone interested, I've managed to build and install on Raspberry Pi 4, running Manjaro RPI4. I have edited the PKGBUILD and changed the architecture to 'aarch64'. The build fails to package the .deb file, when running: 'npm run pack:linux'

However, I have executed all the other commands from the PKGBUILD manually, including the tests and install commands and everything's okay, the app works well. I've had to update some paths, 'dist/linux-unpacked' becomes 'dist/linux-arm64-unpacked'. I have used the official .deb file from the mullvad website to grab the .desktop file and the icons.

I know this is not an ideal way to build and install this app, but I am happy to be able to use mullvad-vpn on ARM64.

Cheers!

yochananmarqos commented on 2020-05-18 00:41 (UTC)

@bbaserdem: I'm not following why npm-test is failing for you. If you don't need the GUI, there is a CLI-only version in the AUR: mullvad-vpn-cli.

As far as Electron applications, each one is build against a specific Electron version. It doesn't always work out forcing a newer version. At this point tray icons are broken on Electron 8 so Mullvad downgraded to 7 for now. Once the issue is fixed upstream, we'll see.

bbaserdem commented on 2020-05-17 17:35 (UTC) (edited on 2020-05-17 17:42 (UTC) by bbaserdem)

The gui test fails for me (since I don't have a display available; I'm building in a clean chroot)

Also why is the installer downloading it's own electron version? Shouldn't the package should pull in electron dependency instead. I dont know much about rust to determine if this is a questionable build decision or not.

Eveready commented on 2020-05-14 22:14 (UTC)

@yochananmarqos Thanks a lot!

yochananmarqos commented on 2020-05-14 22:06 (UTC) (edited on 2020-05-14 22:07 (UTC) by yochananmarqos)

@Eveready: Yes, you can remove the build directory after a successful build. To automatically remove it next time, use the -c flag with makepkg; i.e., makepkg -Csrci.

Eveready commented on 2020-05-14 22:00 (UTC)

I'm a bit new at this, so sorry if this is a dumb question... I noticed that the package, once built, is pretty small, whereas the build folder becomes ~3 gigabytes. Is it ok to erase the build directory once the package is built?

XuLin commented on 2020-05-14 02:46 (UTC)

@yochananmarqos: yes, of course. I'll try installing it again to see what happens but thought I'd share what happened.

yochananmarqos commented on 2020-05-14 02:18 (UTC)

@XuLin: Did you perform a clean build as directed in the pinned comment?

XuLin commented on 2020-05-14 01:05 (UTC)

While building the latest version it went fine but never built the binary itself to run the vpn!

/usr/bin/mullvad-vpn: line 2: /opt/Mullvad VPN/mullvad-vpn: No such file or directory

Can't run the app anymore after that.

yochananmarqos commented on 2020-05-13 14:21 (UTC)

@jhenson: Thanks, added.

jhenson commented on 2020-05-13 00:12 (UTC) (edited on 2020-05-13 00:12 (UTC) by jhenson)

The latest version needs python added as a makedepend:

Installing JavaScript dependencies...

> fsevents@1.2.12 install /build/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/fsevents
> node-gyp rebuild

gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON

MrHotAir commented on 2020-03-22 15:31 (UTC)

Alright, so I asked around /rust and apparently, there is a library called curl that has a HTTP2 request bug in its 7.69.0 version.

AUR already has the bug-fixed verison, but people on Manjaro-stable side are going to have to wait for a moment.

yochananmarqos commented on 2020-03-21 20:02 (UTC) (edited on 2020-03-21 20:02 (UTC) by yochananmarqos)

@MrHotAir: I have been seeing the "spurious network error" from crates.io lately with quite a few packages that use Cargo to build. I'm not sure if it's an issue on their end or what.

MrHotAir commented on 2020-03-21 19:05 (UTC)

Right, so I just recently distro hopped a bit and returned back to Manjaro (XFCE stable). As pamac tried to build Mullvad, I get this weird error message:

==> Starting build()... Building Mullvad VPN 2020.3... runtime/cgo net github.com/mullvad/mullvadvpn-app/wireguard-go Removing old Rust build artifacts Building Rust code... Downloading crates ... Downloaded log-panics v2.0.0 warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of tokio-service v0.1.0 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for tokio v0.1.22 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of jsonrpc-client-core v0.5.0 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for ipnetwork v0.15.0 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of clap v2.33.0 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for chrono v0.4.9 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of uuid v0.7.4 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for tokio-timer v0.1.2 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of serde_derive v1.0.101 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for tokio-retry v0.2.0 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of tokio-io v0.1.12 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for globset v0.4.4 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of mio-named-pipes v0.1.6 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for bytes v0.4.12 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of miow v0.3.3 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for parking_lot v0.6.4 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of dbus v0.6.5 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for atty v0.2.13 within 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of atty v0.2.13 failed to transfer more than 10 bytes in 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for dbus v0.6.5 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of fern v0.5.8 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for err-derive v0.2.1 within 30s) Downloaded fern v0.5.8 warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of tokio-retry v0.2.0 failed to transfer more than 10 bytes in 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for serde_derive v1.0.101 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of zeroize v1.1.0 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for which v3.1.0 within 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of tokio-timer v0.1.2 failed to transfer more than 10 bytes in 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for uuid v0.7.4 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of notify v4.0.13 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for nix v0.15.0 within 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of parking_lot v0.6.4 failed to transfer more than 10 bytes in 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for miow v0.3.3 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of os_pipe v0.8.2 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for nftnl v0.2.1 within 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (download of libc v0.2.65 failed to transfer more than 10 bytes in 30s) warning: spurious network error (2 tries remaining): [28] Timeout was reached (failed to download any data for lazy_static v1.4.0 within 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of nftnl v0.2.1 failed to transfer more than 10 bytes in 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (failed to download any data for os_pipe v0.8.2 within 30s) warning: spurious network error (1 tries remaining): [28] Timeout was reached (download of err-derive v0.2.1 failed to transfer more than 10 bytes in 30s) error: failed to download from https://crates.io/api/v1/crates/dbus/0.6.5/download

Caused by: [28] Timeout was reached (failed to download any data for dbus v0.6.5 within 30s) ==> ERROR: A failure occurred in build(). Aborting...

I tried to check out any of the packages and tried a few tricks to make sure that the problem wasn't in my end (possible firewall issue), but I just can't seem to figure out why I couldn't download those specific files.

Anyway, still thanks for yochananmarqos for your work. I have enjoyed Mullvad on my Linux PC's a lot thanks to your effort in keeping the package on and updated.

yochananmarqos commented on 2020-02-25 15:17 (UTC)

@tylerwolf35: The issue is fixed now, it was a typo.

tylerwolf35 commented on 2020-02-25 04:40 (UTC)

@yochananmarqos I am going to bed as well, just decided to use Wireguard and it worked perfectly well.

yochananmarqos commented on 2020-02-25 04:21 (UTC) (edited on 2020-02-25 04:22 (UTC) by yochananmarqos)

@tylerwolf35: None of this touches your home directory, that's completely wrong. No wonder it can't find the daemon. You're on your own to figure it out for now, I'm going to bed.

tylerwolf35 commented on 2020-02-25 04:12 (UTC) (edited on 2020-02-25 04:13 (UTC) by tylerwolf35)

@yochananmarqos I simply changed the icon directory from /usr/share/icons/hicolor/${icon_size}x${icon_size}/apps to /home/$USER/mullvad-vpn/src/mullvadvpn-app/dist/usr/share/icons/hicolor/${icon_size}x{icon_size}. There was no error but now the daemon is not found.

yochananmarqos commented on 2020-02-25 04:10 (UTC)

@tylerwolf35: What did you edit? What is the exact error? You need to provide this information without me having to ask you.

tylerwolf35 commented on 2020-02-25 04:05 (UTC) (edited on 2020-02-25 04:09 (UTC) by tylerwolf35)

@yochananmarqos Didn't work but I was able to edit the icon directory in the PKGBUILD and it built and installed without errors. Now when I try to start the daemon it is not found. A few weeks ago I installed this package without any issues, I am unsure why it is not working for me now.

tylerwolf35 commented on 2020-02-25 03:44 (UTC) (edited on 2020-02-25 03:48 (UTC) by tylerwolf35)

@yochananmarqos Yep, I will try with -C once again.

yochananmarqos commented on 2020-02-25 03:42 (UTC)

@tylerwolf35: That's bizarre. You did indeed do a clean build with makepkg -C?

Maybe try the mullvad-vpn-beta package and see if the same error occurs. It's exactly the same as this package right now since there's no newer beta. I'm just curious since we have nothing else to go on.

tylerwolf35 commented on 2020-02-25 03:18 (UTC) (edited on 2020-02-25 03:19 (UTC) by tylerwolf35)

@yochananmarqos Yes, src/mullvad-app/dist/usr/share/icons/hicolor/16x16/apps/mullvad-vpn.png does exist.

yochananmarqos commented on 2020-02-25 03:14 (UTC)

@tyler35: Does src/mullvad-app/dist/usr/share/icons/hicolor/16x16/apps/mullvad-vpn.png exist?

tylerwolf35 commented on 2020-02-25 03:05 (UTC)

@yochananmarqos Used makepkg, same error.

❯ tyler/mullvad-vpn master [7m 40s] makepkg -R ==> Making package: mullvad-vpn 2020.3-2 (Mon 24 Feb 2020 10:04:44 PM EST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Starting package()... install: cannot stat '/usr/share/icons/hicolor/16x16/apps/mullvad-vpn.png': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

tylerwolf35 commented on 2020-02-25 02:56 (UTC)

@yochananmarqos Pikaur, I will try with makepkg.

yochananmarqos commented on 2020-02-25 02:48 (UTC)

@tylerwolf35: Are you using makepkg or pikaur? I don't see anything other than "Aborting" at the end when it starts the package. You can use makepkg -R to repackage without building again since the build itself was successful.

tylerwolf35 commented on 2020-02-25 02:32 (UTC) (edited on 2020-02-25 02:33 (UTC) by tylerwolf35)

@yochananmarqos https://privatebin.net/?62b28bfd990d2a95#SJhytyEuRpZRJx7P7enZf4E64oqjwF8682BrzR3aMKd

Does not appear to be full log for some reason though it should suffice as the only thing it's really missing is the previously mentioned error which occurred in package().

yochananmarqos commented on 2020-02-25 02:21 (UTC)

@tylerwolf35: It's the output in your terminal. You can either copy it from there or save it to a log file; i.e., makepkg -Csrif > build.log.

tylerwolf35 commented on 2020-02-25 02:18 (UTC) (edited on 2020-02-25 02:19 (UTC) by tylerwolf35)

@yochananmarqos Where can I get the build log? I've never needed to find it before.

yochananmarqos commented on 2020-02-25 02:16 (UTC)

@tylerwolf35: Please upload the full build log to a pastebin service and link it here.

tylerwolf35 commented on 2020-02-25 02:09 (UTC) (edited on 2020-02-25 02:16 (UTC) by tylerwolf35)

@yochananmarqos I have built the package again and have received the same error. The exact error is: 'install: cannot stat '/usr/share/icons/hicolor/16x16/apps/mullvad-vpn.png': No such file or directory'. I can tell that this means that I am not getting the icons for the application but cannot seem to figure out why.

Edit: Looking at the changes in the PKGBUILD I can see there are some changes in the way the icons are added, I am guessing there is a fault in the change.

tylerwolf35 commented on 2020-02-25 02:01 (UTC)

@yochananmarqos Sudo caused the build to fail very early on, I will do another clean install in an attempt to retrieve the exact error.

yochananmarqos commented on 2020-02-25 01:56 (UTC)

@tylerwolf: What failed to execute? What's the exact error?

You can't use makepkg with sudo. Don't try it.

tylerwolf35 commented on 2020-02-25 01:54 (UTC)

Just tried a clean build and got 'makepkg --force' failed to execute. I have already added all of the PGP keys. Will try as sudo and see if this fixes the issue.

yochananmarqos commented on 2020-02-24 16:52 (UTC)

@diazkun: It happened to me once, but rebuilding (clean) resolved it. The same has resolved it for everyone else that has reported it. I'm not sure what causes it.

@cvmd: Did you add David Lönnhager's key?

cvmd commented on 2020-02-24 16:49 (UTC) (edited on 2020-02-24 16:59 (UTC) by cvmd)

makepkg fails as the signature for mullvad-app-binaries cannot be verified. anyone solved a similar issue? (already tried following the instructions from @yochananmarqos and others with no luck)

EDIT: @yochananmarqos adding David L's key worked, thanks

diazkun commented on 2020-02-24 04:18 (UTC) (edited on 2020-02-24 04:36 (UTC) by diazkun)

@yochananmarqos it was my first time installing and building, no previous thing existed.

Comparing the generated package and installed files under /opt to the released deb package it seems to be missing the huge binary file "mullvad-gui".

The shell script there seems to just loop over itself, looking at htop the command keeps expading with --no-sandbox argument.

edit:

I've rebuilt again, exact same way as I did before and this time the "mulvad-gui" binary with ~110mb was properly generated. This is very weird, since both were clean, fresh builds. There must be somekind of weird thing going on. All compilation passed, the tests and checks also passed, but at the end the binary was not there.

yochananmarqos commented on 2020-02-24 03:33 (UTC)

@diazjun: Do a clean build.

diazkun commented on 2020-02-24 03:29 (UTC)

I just installed, and I'm getting the same problem as written here - https://aur.archlinux.org/packages/mullvad-vpn/?O=10&PP=10#comment-729029

Basically trying to launch form menu says: "Could not find the program /opt/Mullvad VPN/mullvad-vpn'".

Trying to execute the binary on the console just hangs and says nothing at all.

yochananmarqos commented on 2020-02-18 14:54 (UTC)

@serxxx: See Go package guidelines.

serxxx commented on 2020-02-18 13:37 (UTC)

Does this absolutely need go-pie? go-pie conflicts with go, and breaks cross-compiling.

MTBorg commented on 2020-02-18 09:15 (UTC)

It works now after clean building and rebooting, thanks!

yochananmarqos commented on 2020-02-17 17:06 (UTC)

I've just reverted using Electron 8, it should solve the tray icon issues.

yochananmarqos commented on 2020-02-17 16:31 (UTC)

The disappearing tray icon is an Electron / Chromium issue, see FS#65483 - [electron] No tray icons as of Electron 8.0.0.

MTBorg commented on 2020-02-17 11:42 (UTC)

I'm also missing the tray icon, both on startup and after manually starting/restarting the client, running on Arch Linux (kernel 5.4.20-1-lts) with i3.

yochananmarqos commented on 2020-02-14 22:34 (UTC)

@tuse: Yeah, the tray icon is a bit buggy now. It appears for me on GNOME, but after awhile it's gone and doesn't return without restarting the program.

tuse commented on 2020-02-14 21:58 (UTC)

Working great, but after 2020.2-2 I'm not getting a tray icon anymore? Weird, but ok. (running Manjaro XFCE Stable branch with 4.19)

catzybluphish commented on 2020-02-14 02:35 (UTC)

@yochananmarqos: The issue still persists for me. Error message: https://files.catbox.moe/dj0pa8.png. You can also see that I'm running the updated version. This is the rofi's error message when I try to run it off that: https://files.catbox.moe/8e7srw.png.

t1m0 commented on 2020-02-13 16:17 (UTC)

sorry for flagging:)

yochananmarqos commented on 2020-02-13 15:18 (UTC) (edited on 2020-02-13 17:08 (UTC) by yochananmarqos)

@catzybluphish: That doesn't make any sense. /usr/bin/mullvad-vpn is a symlink to /opt/Mullvad VPN/mullvad-gui, there is no /usr/bin/mullvad-gui.

EDIT: I can reproduce the issue, I'll work on it. I think it's due to the Electron 8 update. You can use mullvad-vpn-bin for now.

EDIT 2: It's fixed now, just pushed an update.

catzybluphish commented on 2020-02-13 12:38 (UTC)

After updating, I can't start the program anymore. I've always run it from rofi, but now it says it failed to execute /opt/Mullvad VPN/mullvad-vpn because it doesn't exist. Running mullvad-vpn in the terminal says "/usr/bin/mullvad-vpn: line 5: /usr/bin/mullvad-gui: No such file or directory", and running /opt/Mullvad\ VPN/mullvad-gui just hangs the prompt without showing the GUI. How can this be resolved?

yochananmarqos commented on 2020-02-12 15:16 (UTC)

Checksums are fixed.

redman commented on 2020-02-12 12:26 (UTC)

@mdarr: Yes, for me that worked like a charm. Thanks!

mdarr commented on 2020-02-12 10:35 (UTC)

The fourth sha256sum (corresponding to update-relays.sh) needs to be updated to 89267795175c5be95d13e8f700b69654faf2f38f35be5033eb8e94da404d2353

redman commented on 2020-02-12 07:25 (UTC)

Yes, that's my understanding too: update-relays.sh needs an update :) Thanks in advance for your attention!

For the sake of clearity my full output: Building mullvad-vpn... ==> Making package: mullvad-vpn 2020.1-1 (wo 12 feb 2020 08:20:32 CET) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Updating mullvadvpn-app git repo... Fetching origin From https://github.com/mullvad/mullvadvpn-app da923ea29..c30998261 consolidate-wg-wrappers -> consolidate-wg-wrappers + 6aa5e58d7...fbd0a8501 fix-service-init-race-condition -> fix-service-init-race-condition (forced update) da923ea29..c30998261 refs/pull/1468/head -> refs/pull/1468/head + 6aa5e58d7...fbd0a8501 refs/pull/1479/head -> refs/pull/1479/head (forced update) + e6aaf467a...a7aedc157 refs/pull/1479/merge -> refs/pull/1479/merge (forced update) da923ea29..e1ef816fa refs/reviewable/pr1468/r1 -> refs/reviewable/pr1468/r1 * [new ref] refs/reviewable/pr1468/r2 -> refs/reviewable/pr1468/r2 + 6aa5e58d7...fbd0a8501 refs/reviewable/pr1479/r1 -> refs/reviewable/pr1479/r1 (forced update) -> Cloning mullvadvpn-app-binaries git repo... Cloning into bare repository '/var/tmp/pamac-build-afw/mullvad-vpn/mullvadvpn-app-binaries'... -> Found mullvad-vpn.desktop -> Found update-relays.sh ==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.desktop ... Passed update-relays.sh ... FAILED ==> ERROR: One or more files did not pass the validity check! Failed to build mullvad-vpn

t1m0 commented on 2020-02-12 06:40 (UTC)

I think you need to update the sha-sum of your update-relays.sh. It fails with update-relays.sh ... FAILED ==> ERROR: One or more files did not pass the validity check!

yochananmarqos commented on 2020-02-11 18:02 (UTC)

@hawk-ee: My user info in my .gitconfig somehow got reset, I updated it. Next commit will have my name, never fear.

yochananmarqos commented on 2020-02-11 17:52 (UTC)

@hawk-ee: The changes were made by me, I don't know why it shows Test User. I'll look into it.

hawk-ee commented on 2020-02-11 17:21 (UTC) (edited on 2020-02-11 17:23 (UTC) by hawk-ee)

Weird that last changes was not made by the maintainer... You guys can skip update-relays.sh checksum via PKGBUILD file, I'm going to manually build it.

exiel commented on 2020-02-11 11:12 (UTC)

I have the same issue with the new update - the update-relays.sh file does not pass the validity check, even with keys imported from the Mullvad website.

twolf commented on 2020-02-11 02:33 (UTC)

Does anyone know if this issue persists in the beta build?

twolf commented on 2020-02-11 02:33 (UTC)

Added the Linus key as well, no change.

twolf commented on 2020-02-11 02:29 (UTC)

Currently the update-relays.sh file does not pass the validity check, even with keys imported from the Mullvad website.

twolf commented on 2020-02-11 02:28 (UTC)

This is just happening with the latest release, I guess the maintainer will fix it given the time.

MrHotAir commented on 2020-02-10 18:01 (UTC)

Hi!

Loved when moving from Windows to Manjaro that the AUR community had even this piece of nifty software already working. My thanks to you all wonderful people!

However, this reason update, I'm getting an error that one of the files.

"==> Validating source files with sha256sums... mullvadvpn-app ... Skipped mullvadvpn-app-binaries ... Skipped mullvad-vpn.desktop ... Passed update-relays.sh ... FAILED ==> ERROR: One or more files did not pass the validity check! "

Would this be an error on my end?

t1m0 commented on 2020-02-10 17:10 (UTC)

Hi and thanks for the good work,

I am building myself the package without the electron-stuff. I would like to know why you are using the old commit in the mullvadvpn-app-binaries repo. I see they removed libwg and then it does not build anymore. Do you have any idea how to use a newer commit like in their release? (90b0c06)

Best regards, Timo

sheevy commented on 2020-01-04 11:56 (UTC)

@ortizder @newb Thank you both. It turned out my issue was different. I imported the certificates as root and trizen couldn't see them. After importing them as regular user the installation went through.

newb commented on 2019-12-26 10:11 (UTC)

@sheevy If you are trying to update, make sure to close the installed version first. Worked for me...

ortizder commented on 2019-12-19 23:26 (UTC) (edited on 2019-12-19 23:33 (UTC) by ortizder)

@sheevy

I got the same thing but had luck adding Linus' key from the site when after it was failing:

# wget <https://mullvad.net/media/signing-keys/linus-code-signing.asc>
# gpg2 --import linus-code*.asc

sheevy commented on 2019-12-14 13:47 (UTC) (edited on 2019-12-14 13:55 (UTC) by sheevy)

I'm getting:

==> Verifying source file signatures with gpg...
    mullvadvpn-app git repo ... FAILED (unknown public key 78CEAA8CB72E4467)
    mullvadvpn-app-binaries git repo ... FAILED (unknown public key 78CEAA8CB72E4467)

Despite having imported both: signing and Linus' keys:

# gpg2 --edit-key A1198702FC3E0A09A9AE5B75D5A1D4F266DE8DDF

pub  rsa4096/D5A1D4F266DE8DDF
     created: 2016-10-27  expires: never       usage: SC  
     trust: ultimate      validity: ultimate
sub  rsa4096/C187D22C089EF64E
     created: 2016-10-27  expires: never       usage: E   
sub  rsa4096/A26581F219C8314C
     created: 2016-10-27  expires: never       usage: S   
[ultimate] (1). Mullvad (code signing) <admin@mullvad.net>
# gpg2 --edit-key 78CEAA8CB72E4467

pub  rsa4096/7653B940E494FE87
     created: 2015-07-08  expires: never       usage: SC  
     trust: ultimate      validity: ultimate
sub  rsa4096/8B0C4C0CCC536DAF
     created: 2015-07-08  expires: never       usage: E   
sub  rsa4096/78CEAA8CB72E4467
     created: 2016-10-31  expires: never       usage: S   
[ultimate] (1). Linus Färnstrand (code signing key) <linus@mullvad.net>

Any ideas what else needs to be done?

yochananmarqos commented on 2019-12-13 18:04 (UTC)

@XenGi: What are you using for cargo? It's best to use rust.

XenGi commented on 2019-12-13 17:54 (UTC)

The package isn't compiling for me since a while now.

   Compiling rs-release v0.1.7 (https://github.com/mullvad/rs-release?branch=snailquote-unescape#88b2afb0)
   Compiling log v0.3.9
   Compiling want v0.0.4
   Compiling log-panics v2.0.0
   Compiling base64 v0.9.3
   Compiling base64 v0.10.1
   Compiling generic-array v0.12.3
   Compiling aho-corasick v0.7.6
   Compiling aho-corasick v0.6.10
   Compiling bstr v0.2.8
   Compiling combine v3.8.1
   Compiling iovec v0.1.4
   Compiling net2 v0.2.33
   Compiling num_cpus v1.10.1
error[E0658]: imports can only refer to extern crate names passed with `--extern` on stable channel (see issue #53130)
  --> /home/xengi/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.1.12/src/error_impls.rs:13:5
   |
8  | extern crate std;
   | ----------------- not an extern crate passed with `--extern`
...
13 | use std::io;
   |     ^^^
   |
   = help: add #![feature(uniform_paths)] to the crate attributes to enable
note: this import refers to the extern crate imported here
  --> /home/xengi/.cargo/registry/src/github.com-1ecc6299db9ec823/getrandom-0.1.12/src/error_impls.rs:8:1
   |
8  | extern crate std;
   | ^^^^^^^^^^^^^^^^^

   Compiling rand v0.4.6
error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: Could not compile `getrandom`.
warning: build failed, waiting for other jobs to finish...
 error: build failed
==> ERROR: A failure occurred in build().
    Aborting...
Error making: mullvad-vpn

coderobe commented on 2019-12-13 17:51 (UTC)

No. That dep does not belong in this package, ras.

commented on 2019-12-13 14:32 (UTC)

Thanks @jhenson the package now correctly builds. I belive it is the same problem that @a.liedtke was experiencing. Maybe @yochananmarqos should add lmdb as a dep till the bug is fixed? Thanks again @jhenson

jhenson commented on 2019-12-13 14:13 (UTC)

@ras.anonymous the rpm-tools package is missing a dependency declaration so the rpm tool fails to run if you don't have lmdb installed. As a workaround until the package is fixed you can manually install lmdb.

https://bugs.archlinux.org/task/64824

commented on 2019-12-13 12:14 (UTC)

can't build this package. privatebin: https://privatebin.net/?9a367e9f3dac8020#8ZWh6Lk96V8n2iY989eek7FhWm6Vvk8APZBhhcRL6Lfc

yochananmarqos commented on 2019-12-13 02:25 (UTC) (edited on 2019-12-13 02:25 (UTC) by yochananmarqos)

@wilberfan: Please follow the instructions in the pinned comment.

wilberfan commented on 2019-12-13 02:24 (UTC)

I'm admittedly new at this, but is this a server issue, or...?

==> PGP keys need importing: -> EA0A77BF9E115615FC3BD8BC7653B940E494FE87, required by: mullvad-vpn ==> Import? [Y/n] Y :: Importing keys with gpg...... gpg: keyserver receive failed: No data ==> Error: Problem importing keys

jhenson commented on 2019-12-13 00:09 (UTC)

@yochananmarqos I just checked and it doesn't appear to be on the wiki anywhere, weird. I learned about it from other packages and have been using it myself.

yochananmarqos commented on 2019-12-12 22:50 (UTC)

@jhenson: I didn't know makepkg could do that, thanks! Where did you find that out? I didn't see anything in the wiki or the man page about it.

jhenson commented on 2019-12-12 22:17 (UTC) (edited on 2019-12-12 22:23 (UTC) by jhenson)

If you put ?signed at the end of the git urls makepkg will verify the commit/tag for you. This is needed for building in a clean chroot where the sources are verified outside of the chroot. The validpgpkeys array also needs to list the specific signing sub-key instead of the parent key.

The following patch fixes the chroot verification for me:

diff --git a/PKGBUILD b/PKGBUILD
index [`53c9852`](https://aur.archlinux.org/cgit/aur.git/commit/?h=mullvad-vpn&id=53c9852)..6f2752c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -16,16 +16,15 @@ depends=('libnotify' 'libappindicator-gtk3' 'libxss' 'nss')
 makedepends=('git' 'cargo' 'npm' 'rpm')
 install="$pkgname.install"
 _commit='0c1a0aca41492fbb9ef1f187122e2f5bda0927ba'
-source=("git+<https://github.com/mullvad/mullvadvpn-app.git#tag=>$pkgver"
-        "git+<https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=>$_commit"
+source=("git+<https://github.com/mullvad/mullvadvpn-app.git#tag=>$pkgver?signed"
+        "git+<https://github.com/mullvad/mullvadvpn-app-binaries.git#commit=>$_commit?signed"
         "$pkgname.desktop"
         'update-relays.sh')
 sha256sums=('SKIP'
             'SKIP'
             '121d90e6683e64d9c0d2dbb7b346fa918bdb37cf21fdaf9f66232304ed23abc2'
             'ec125bc9cfe2403bacfcaebf4b58f88b4d734b0f6194c23016efd7e15684f8e0')
-validpgpkeys=('A6A4778440D27368967A7A3578CEAA8CB72E4467')
-             # Linus Färnstrand (code signing key) <linus at mullvad dot net>
+validpgpkeys=('EA0A77BF9E115615FC3BD8BC7653B940E494FE87') # Linus Färnstrand (code signing key) <linus at mullvad dot net>

 prepare() {
        # Point the submodule to our local copy
@@ -34,13 +33,6 @@ prepare() {
        git config submodule.mullvadvpn-app-binaries.url \
                "$srcdir/mullvadvpn-app-binaries"
        git submodule update
-
-       # Verify git tag
-       git verify-tag "$pkgver"
-
-       # Verify git commit
-       cd "$srcdir/mullvadvpn-app-binaries"
-       git verify-commit "$_commit"
 }

 build() {

Thanks for all your work on this package!

yochananmarqos commented on 2019-12-10 22:31 (UTC) (edited on 2019-12-10 22:31 (UTC) by yochananmarqos)

@procyon-lotor: Why are you not running the stable 5.4.2 kernel? See Enable support to run unprivileged containers (optional)

procyon-lotor commented on 2019-12-10 18:24 (UTC)

@yochanamarqos

I'm using kernel Linux 5.4rc7.d1117.g1d4c79e-1

here's the pastebin of the build. https://pastebin.com/S1y1hehH

yochananmarqos commented on 2019-12-09 22:06 (UTC)

@procyon-lotor: That shouldn't happen during build, but could happen running the GUI. What kernel are you using? Please paste the build log to a pastebin service and link it here, I'll take a look.

@a.liedtke: Please also paste the build log to a pastebin service and link it here.

a.liedtke commented on 2019-12-09 21:12 (UTC)

Get error: 20 error code ELIFECYCLE 21 error errno 1 22 error mullvad-vpn@2019.9.0 pack:linux: gulp pack-linux 22 error Exit status 1 23 error Failed at the mullvad-vpn@2019.9.0 pack:linux script. 23 error This is probably not a problem with npm. There is likely additional logging output above.

procyon-lotor commented on 2019-12-09 13:26 (UTC)

Stupid question incoming:

I'm having trouble getting the mullvad build to run correctly.

I get an error message regarding chrome-sandbox not being owned by root and it should be set as chmod 4755.

Having done that, rerunning the build just replaces the files with newly generated.

How do i solve this?

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2020-11-17 03:00 (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.

yochananmarqos commented on 2019-12-05 03:25 (UTC) (edited on 2019-12-05 03:26 (UTC) by yochananmarqos)

@jpprovost: This package should have been created as mullvad-vpn-bin to begin with since it was a binary source.

All official Arch packages are built from source code. The packages installed via Pacman are already built by the package maintainers, but AUR packages are up to users to build. See the Arch Build System wiki entry for more info.

jpprovost commented on 2019-12-05 03:11 (UTC)

@yochananmarqos: I didn't know that. It's an important change. Is there a reason for this modification?

Thanks for the quick reply by the way.

yochananmarqos commented on 2019-12-05 03:09 (UTC)

@jpprovost: I takes awhile because it now builds from source code. The precompiled binary package is mullvad-vpn-bin. You can install that if you prefer quicker updates.

jpprovost commented on 2019-12-05 02:48 (UTC)

Is it normal that it takes so long to build ? It took me about 20+ minutes... I have no memories of such a long time to update this package...

Am I the only one?

commented on 2019-12-04 15:51 (UTC)

Can confirm, built and installed successfully.

Thanks.

yochananmarqos commented on 2019-12-03 23:41 (UTC)

It builds! I mean it this time. Let me know if I missed anything.

yochananmarqos commented on 2019-12-02 16:44 (UTC) (edited on 2019-12-02 17:57 (UTC) by yochananmarqos)

@dbirks: Thank you, that helps. EDIT: I think I just figured out what the problem is, rebuilding now...

dbirks commented on 2019-12-02 15:17 (UTC)

@yochananmarqos I haven't fully tested this, but while working on building this from source last week, this is what I got. I added dist-assets/binaries to the init to skip grabbing the windows-specific sources. Hopefully it helps some:

source=("git+https://github.com/mullvad/mullvadvpn-app.git#tag=$pkgver"
        "git+https://github.com/mullvad/mullvadvpn-app-binaries.git")

prepare() {
  # Point the submodule to our local copy
  cd mullvadvpn-app
  git submodule init dist-assets/binaries
  git config submodule.mullvadvpn-app-binaries.url "$srcdir/mullvadvpn-app-binaries"
  git submodule update
}

yochananmarqos commented on 2019-12-02 15:10 (UTC) (edited on 2019-12-02 15:22 (UTC) by yochananmarqos)

I can reproduce the error, I'll work on it.

@coderobe: Oh, I see what you mean. I'll do some research about it.

coderobe commented on 2019-12-02 15:00 (UTC)

@yochananmarqos: the difference is that your sources are not checked into SRCDEST. Please follow our guidelines for this.

Taijian commented on 2019-12-02 12:53 (UTC)

@blackpoll: The mullvad-vpn-bin package works fine and is quick and easy to install.

Taijian commented on 2019-12-02 12:46 (UTC)

Two things:

1) gui testing fails under wayland (..cannot open display...)

2) the 'cannot stat dist/linux-unpacked/' issue also occurs when building in a clean chroot (via clean-chroot-manager). So that needs to be fixed.

@yochananmarqos: Could you try the clean chroot build? Then compare your live system and see what the difference is, presuming that the build works for you in your 'regular' system?

FuelFlo commented on 2019-12-02 11:26 (UTC)

Hey, i have the same problem. None of the 3 changes in PKGBUILD worked for me. I'm still getting:

==> Entering fakeroot environment... ==> Starting package()... install: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

...using pamac and/or yay.

commented on 2019-12-02 06:03 (UTC)

@yochananmarqos I get the following errors when trying your recommended fixes:

cp: cannot stat 'dist/linux-unpacked/.': No such file or directory and install: cannot stat 'dist/linux-unpacked/*': No such file or directory

I'm using makepkg -si. Would it perhaps have anything to do with the new rust/cargo dependency?

yochananmarqos commented on 2019-12-02 02:23 (UTC) (edited on 2019-12-02 15:15 (UTC) by yochananmarqos)

@davedatum @ruabmbua @blackpoll: EDIT: I can reproduce it, working on it.

@coderobe: What does git submodule update --init --recursive not accomplish that the VCS package guidelines example does? The submodules are nested and the --recursive flag pulls them all.

coderobe commented on 2019-12-01 22:25 (UTC)

@yochananmarqos: Git submodules in sources require a bit more work. git submodule update --init --recursive is not sufficient. Please take a look at https://wiki.archlinux.org/index.php/VCS_package_guidelines#Git_Submodules

blackpoll commented on 2019-12-01 21:47 (UTC)

==> Starting package()... cp: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

There are multiple versions now of Mullvad in the AUR. Which one is recommended to properly work and update?

ruabmbua commented on 2019-12-01 19:02 (UTC)

Same problem here:

==> Starting package()... cp: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

commented on 2019-12-01 18:58 (UTC)

mullvad-vpn 2019.9-7

==> Entering fakeroot environment... ==> Starting package()... cp: cannot stat 'dist/linux-unpacked/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...

yochananmarqos commented on 2019-11-27 22:07 (UTC)

@Taijian: Thanks, good catch.

Taijian commented on 2019-11-27 21:47 (UTC)

Following up on my earlier post about dependencies: After some experimenting it seems that mullvad does not necessarily need 'libappindicator-gtk2' - which makes sense, because it also depends on gtk3 not gtk2. Apparently 'libappindicator-gtk3' will also do just fine displaying the tray icon.

yochananmarqos commented on 2019-11-27 14:52 (UTC)

@Taijian: I removed gconf. gsettings-desktop-schemas is covered by gtk3.

Taijian commented on 2019-11-27 10:00 (UTC) (edited on 2019-11-27 10:29 (UTC) by Taijian)

Just as a PSA/heads-up: Being annoyed at having to install gconf (which is heavily outdated and unmaintained) just to run mullvad, I've tried just removing it again. Voilá: As long as gsettings-desktop-schemas (which is the replacement for gconf) is installed, it seems as though mullvad will still run and work fine.

So, maybe try this out for yourself and switch the dependency to something that is supported.

UPDATE: I actually asked about this on the mullvad github and they clarified that the deb/rpm releases do not depend on gconf2. So that dependency should probably be removed. https://github.com/mullvad/mullvadvpn-app/issues/1269#issuecomment-559025618

coderobe commented on 2019-11-23 15:25 (UTC)

No it won't. Mullvad provides sources at https://github.com/mullvad/mullvadvpn-app - Please modify this PKGBUILD to build from source, or disown it so that someone else may do so.

yochananmarqos commented on 2019-11-20 18:12 (UTC)

PSA: This package will be now called mullvad-vpn-bin as soon as the merge request is accepted

bitreactor commented on 2019-11-20 12:06 (UTC) (edited on 2019-11-20 12:09 (UTC) by bitreactor)

The GUI doesn't work properly. I have to execute systemctl restart mullvad-daemon in terminal to establish a connection to the servers. Every time I reboot the computer I have to do this again.

yochananmarqos commented on 2019-10-30 19:33 (UTC)

@andykluger: Feel free to write a PKGBUILD that builds from source and share it with the rest of the class. ;)

andykluger commented on 2019-10-30 19:31 (UTC)

Currently this installs binary blobs, which is not at all appropriate for an AUR package that doesn't end in '-bin'. Please either rename this package so it's no longer deceptive, or have it build from source as is expected. Thank you for packaging this!

yochananmarqos commented on 2019-10-11 14:28 (UTC) (edited on 2019-10-14 19:45 (UTC) by yochananmarqos)

With v2019.9, a new symlink needs to be added to match upstream:

    ln -s "/opt/$pkgname/resources/mullvad-problem-report" "$pkgdir/usr/bin/mullvad-problem-report"

blackpoll commented on 2019-09-26 10:55 (UTC)

@Daxor That worked! Thanks for the helpful tip.

gin078 commented on 2019-09-26 06:12 (UTC)

@yochananmarqos I'm not sure I follow -- the PGP key has long been added to the package (https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=mullvad-vpn#n18).

Daxor commented on 2019-09-25 22:57 (UTC)

@blackpoll You probably need to reset your wireguard keys or make a new one. I had this issue earlier before.

blackpoll commented on 2019-09-25 21:00 (UTC) (edited on 2019-09-26 10:55 (UTC) by blackpoll)

The Wireguard functionality isn't working for me. It's stuck on "Blocking Internet." OpenVPN works fine.

Daxor commented on 2019-09-25 00:21 (UTC)

After the recent update, as of lastnight, the GUI has completely stopped functioning at all for me, whenver I attempt to launch the GUI I stumble uppon this error

/usr/bin/mullvad-vpn: line 5: /usr/bin/mullvad-gui: No such file or directory

eiko commented on 2019-08-28 17:31 (UTC)

i was having problems with a "failed to verify integrity or prepare mullvad-vpn package" error when trying to install via pacaur.

running: gpg2 --keyserver pool.sks-keyservers.net --recv-keys A1198702FC3E0A09A9AE5B75D5A1D4F266DE8DDF as described in https://mullvad.net/en/guides/verifying-signatures/ seemed to fix it

commented on 2019-08-09 20:56 (UTC)

Would you consider updating to beta version of the package? Currently at 2019.7-beta1

yochananmarqos commented on 2019-08-08 16:40 (UTC) (edited on 2019-08-08 16:49 (UTC) by yochananmarqos)

You don't need to provide the desktop and service file separately, they're included:

    # Systemd service
    sed -i 's/Mullvad\x20VPN/mullvad-vpn/g' "opt/Mullvad VPN/resources/mullvad-daemon.service"
    install -Dm644 "opt/Mullvad VPN/resources/mullvad-daemon.service" \
        "$pkgdir/usr/lib/systemd/system/mullvad-daemon.service"

    # Desktop Entry
    sed -i 's/Mullvad VPN/mullvad-vpn/g' \
        "usr/share/applications/${pkgname}.desktop"
    install -Dm644 "usr/share/applications/${pkgname}.desktop" \
        "$pkgdir/usr/share/applications/${pkgname}.desktop"

pkap commented on 2019-06-30 13:07 (UTC)

The Mullvad developers provide a GPG signature of the RPM package. I'd like to suggest to use this for verification. This makes it necessary to import Mullvad's GPG key once but increases security.

It could look like this:

https://privatebin.net/?90f661f554749cf5#JTMk5F/drmAcatO5CAj+NNLvJxaGh+M/0j2kvfE+tRg=

(I adopted this from the AUR package of the Tor Browser.)

bitreactor commented on 2019-06-17 14:53 (UTC) (edited on 2019-06-18 09:52 (UTC) by bitreactor)

Unable to update:

curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104 ==> FEHLER: Fehler beim Download von https://github.com/mullvad/mullvadvpn-app/releases/download/2019.5/MullvadVPN-2019.5_x86_64.rpm Breche ab...

EDIT: Nevermind, update is working again!

TheCraiggers commented on 2019-05-31 00:55 (UTC)

I use KDE, and when I am running this mullvad-vpn app, it causes KDE to freak out. Among other things, suspend no longer works, and when I try to use the start menu the GUI freezes, although I can still interact with already-open windows.

Anybody else experience issues like this? I've tried looking in the usual log locations but nothing looks odd.

The app itself works great- it just hoses the rest of my system. :(

ruabmbua commented on 2019-04-06 13:17 (UTC)

I created a patch for updating to the newer 2019.3 version of mullvad-vpn: https://gist.github.com/ruabmbua/baa640da268e02c3429c2f891f658950

someDude42 commented on 2019-03-21 02:58 (UTC) (edited on 2019-03-21 02:58 (UTC) by someDude42)

The mullvad-vpn GUI is currently broken for me (probably due to version mismatch), use the mullvad command for now

commented on 2019-03-13 14:45 (UTC)

More serious issue; with the old app sharing the tunneled connection over wifi was easy. Now because of the mullvad app clients can't connect anymore. I have 'Local network sharing' enabled of course. The ip addresses simply aren't released to clients. As soon as I close the app and the daemon everything works fine.. I tried this with NetworkManager as well as create_ap. Anyone know a solution?

blackpoll commented on 2019-03-11 15:42 (UTC)

Works great! Thanks for putting this together.

commented on 2019-02-20 20:36 (UTC)

@Sebversive Works fine for me.

commented on 2019-02-20 13:07 (UTC)

Horrible program, so heavy. Finally got it to work. The app window doesn't show up if the daemon is running. Only if I start the gui first and then the daemon.

yochananmarqos commented on 2018-11-16 16:31 (UTC)

@snarfies You need to restart the service after updating:

systemctl restart mullvad-daemon

snarfies commented on 2018-11-16 16:28 (UTC)

Okay, 2018.5-3 put the menu entry back, thank you. Now the app says "Inconsistent internal version information, please restart the app." Internet connection is dead until the app is closed.

snarfies commented on 2018-11-16 06:32 (UTC) (edited on 2018-11-16 06:32 (UTC) by snarfies)

This new build of Mullvad (2018.5-2) has removed my entry form XFCE and replaced it with... nothing. I have no menu entry anymore. Boo.

ethanrakoff commented on 2018-11-07 11:32 (UTC)

Doesn't need to conflict with mullvad-vpn-old anymore as that package no longer exists.

yochananmarqos commented on 2018-11-02 16:33 (UTC) (edited on 2019-09-25 23:51 (UTC) by yochananmarqos)

@oibind That's a great idea. I've implemented it in my PKGBUILD.

oibind commented on 2018-11-02 15:53 (UTC)

should really be validating the signature from mullvad

https://gist.github.com/oibind/36cb69e2a90dd4e2628adbe56fb1259e

sheevy commented on 2018-10-30 23:29 (UTC)

Thanks for this!

yochananmarqos commented on 2018-10-30 18:21 (UTC) (edited on 2019-09-25 23:52 (UTC) by yochananmarqos)

The package should be called mullvad-vpn-bin as the source is a prebuilt binary package.

The desktop file is no longer needed, it's in the source package.

rpmextract is not needed; the .rpm is extracted automatically.

To add messages to display after installing/upgrading, they should be in an .install file like this: https://github.com/yochananmarqos/pkgbuilds/blob/master/mullvad-vpn/mullvad-vpn.install

YaLTeR commented on 2018-10-29 16:17 (UTC)

Could you please add the CLI binary to the package? This seems to do the trick:

install -m755 "${srcdir}/usr/bin/mullvad" "${pkgdir}/usr/bin/mullvad"

lol-md5 commented on 2018-10-29 04:01 (UTC)

Anyone know why the original got removed?

petr.nehez commented on 2018-10-26 04:47 (UTC) (edited on 2018-10-26 04:47 (UTC) by petr.nehez)

Thanks! I was considering to bring it back too :)

hcjl commented on 2018-10-24 20:16 (UTC)

Thx for taking over!