Package Details: mullvad-vpn-beta 2023.1.beta2-1

Git Clone URL: https://aur.archlinux.org/mullvad-vpn-beta.git (read-only, click to copy)
Package Base: mullvad-vpn-beta
Description: The Mullvad VPN client app for desktop (beta channel)
Upstream URL: https://www.mullvad.net
Licenses: GPL3
Conflicts: mullvad-vpn
Provides: mullvad-vpn
Submitter: None
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 10
Popularity: 0.107068
First Submitted: 2019-08-09 21:46 (UTC)
Last Updated: 2023-02-07 15:28 (UTC)

Pinned Comments

yochananmarqos commented on 2022-10-05 15:33 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)

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

yochananmarqos commented on 2019-12-07 17:44 (UTC) (edited on 2020-02-26 18:30 (UTC) by yochananmarqos)

--> ALWAYS DO A CLEAN BUILD <--

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

Latest Comments

1 2 3 4 5 6 Next › Last »

reclusivesage commented on 2022-10-23 19:25 (UTC)

When I ran $ makepkg -sirc, I received some sort of connection error below (both with and without Mullvad VPN activated) and I do not use a proxy. (I have been able to build this package before behind Mullvad VPN in the past and I have updated my system.)

I also have the complete log.

~/AUR/mullvad-vpn-beta/src/mullvadvpn-app
~/AUR/mullvad-vpn-beta/src/mullvadvpn-app/gui ~/AUR/mullvad-vpn-beta/src/mullvadvpn-app
Installing JavaScript dependencies...
npm ERR! code ECONNREFUSED
npm ERR! syscall connect
npm ERR! errno ECONNREFUSED
npm ERR! FetchError: request to https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: connect ECONNREFUSED 2606:4700::6810:1b23:443
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:513:28)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:488:9)
npm ERR!     at TLSSocket.emit (node:events:525:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
npm ERR!  FetchError: request to https://registry.npmjs.org/yocto-queue/-/yocto-queue-0.1.0.tgz failed, reason: connect ECONNREFUSED 2606:4700::6810:1b23:443
npm ERR!     at ClientRequest.<anonymous> (/usr/lib/node_modules/npm/node_modules/minipass-fetch/lib/index.js:130:14)
npm ERR!     at ClientRequest.emit (node:events:513:28)
npm ERR!     at TLSSocket.socketErrorListener (node:_http_client:488:9)
npm ERR!     at TLSSocket.emit (node:events:525:35)
npm ERR!     at emitErrorNT (node:internal/streams/destroy:151:8)
npm ERR!     at emitErrorCloseNT (node:internal/streams/destroy:116:3)
npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
npm ERR!   code: 'ECONNREFUSED',
npm ERR!   errno: 'ECONNREFUSED',
npm ERR!   syscall: 'connect',
npm ERR!   address: '2606:4700::6810:1b23',
npm ERR!   port: 443,
npm ERR!   type: 'system'
npm ERR! }
npm ERR! 
npm ERR! If you are behind a proxy, please make sure that the
npm ERR! 'proxy' config is set properly.  See: 'npm help config'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/uSER/AUR/mullvad-vpn-beta/src/npm_cache/_logs/2022-10-23T11_15_29_303Z-debug-0.log
==> ERROR: A failure occurred in prepare().
    Aborting...

yochananmarqos commented on 2022-10-09 20:55 (UTC)

@Technetium1: Instead of whining and complaining about what you don't like, please propose the change you want made. This has been discussed here before.

Technetium1 commented on 2022-10-09 20:44 (UTC)

I don't feel like I should have to mask a service I don't use. Please check to see if the service was already enabled in the first place.

yochananmarqos commented on 2022-10-05 15:33 (UTC) (edited on 2022-11-13 19:21 (UTC) by yochananmarqos)

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

Technetium1 commented on 2022-10-05 13:37 (UTC)

2022.5-beta2 has been released.

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

@Ranguvar: Thanks for the heads up, it's fixed.

Ranguvar commented on 2022-02-16 02:38 (UTC)

2022.1.beta1-1 fails to compile with glibc 2.35-2, binutils 2.38-3, and gcc(-libs) 11.2.0-3.

This is due to a ruby binary (~/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86_64/lib/ruby/bin.real/ruby), which runs in the last steps and requires /usr/lib/libcrypt.so.1.

Downgrading temporarily works to build.

foot commented on 2022-02-04 22:49 (UTC) (edited on 2022-02-04 22:50 (UTC) by foot)

@reclusivesage

I'm having the same issue as you did, however I'm not able to use your fix to solve it. I will post my logs down below. I've installed the most recent nodejs and npm with pacman npm --version yields 6.14.11. I've also run nvm use system

Note that I have very little experience developing with nodejs, so there might be some obvious configuration that I'm missing.

the output of /home/user/programs/mullvad-vpn/src/npm-cache/_logs/2022-02-04T22_23_06_151Z-debug.log is

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'ci',
1 verbose cli   '--cache',
1 verbose cli   '/home/user/programs/mullvad-vpn/src/npm-cache'
1 verbose cli ]
2 info using npm@6.14.11
3 info using node@v14.16.0
4 verbose npm-session fbef7ef77badd8de
5 info prepare initializing installer
6 verbose prepare starting workers
7 verbose prepare installation prefix: /home/user/programs/mullvad-vpn/src/mullvadvpn-app/gui
8 verbose prepare using package-lock.json
9 warn prepare removing existing node_modules/ before installation
10 verbose checkLock verifying package-lock data
11 verbose teardown shutting down workers.
12 info teardown Done in 0.001s
13 verbose stack Error: string.prototype.trimend not accessible from es-abstract
13 verbose stack     at reqAddr (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:159:17)
13 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:129:22
13 verbose stack     at Array.forEach (<anonymous>)
13 verbose stack     at addChild (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:128:40)
13 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:133:7
13 verbose stack     at Array.forEach (<anonymous>)
13 verbose stack     at addChild (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:128:40)
13 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:133:7
13 verbose stack     at Array.forEach (<anonymous>)
13 verbose stack     at addChild (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:128:40)
13 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:133:7
13 verbose stack     at Array.forEach (<anonymous>)
13 verbose stack     at addChild (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:128:40)
13 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:113:5
13 verbose stack     at Array.forEach (<anonymous>)
13 verbose stack     at lockTree (/usr/local/lib/node_modules/npm/node_modules/npm-logical-tree/index.js:107:5)
14 verbose cwd /home/user/programs/mullvad-vpn/src/mullvadvpn-app/gui
15 verbose Linux 5.16.5-arch1-1
16 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "ci" "--cache" "/home/user/programs/mullvad-vpn/src/npm-cache"
17 verbose node v14.16.0
18 verbose npm  v6.14.11
19 error string.prototype.trimend not accessible from es-abstract
20 verbose exit [ 1, true ]

ardency commented on 2021-11-16 18:24 (UTC)

Not sure how to resolve this...

==> Starting prepare()...
Submodule 'dist-assets/binaries' (https://github.com/mullvad/mullvadvpn-app-binaries) registered for path 'dist-assets/binaries'
Cloning into '/home/erin/.cache/pikaur/build/mullvad-vpn-beta/src/mullvadvpn-app/dist-assets/binaries'...
Submodule path 'dist-assets/binaries': checked out '19a97997b188855d0ba5aedb7419683df45d93bc'
Removing old Rust build artifacts
error: failed to download `zeroize_derive v1.2.0`

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at `/home/erin/.cargo/registry/src/github.com-1ecc6299db9ec823/zeroize_derive-1.2.0/Cargo.toml`

Caused by:
  feature `resolver` is required

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

I followed instructions to enable nightly features for rust/cargo, but still can't proceed.

Ranguvar commented on 2021-11-04 04:19 (UTC) (edited on 2021-11-19 10:48 (UTC) by Ranguvar)

Fails to build with LTO, works once disabled.

Not required, but would appreciate an options=('!lto') for those enabling LTO globally.

I had a build log, but my terminal ate it...

Thanks!