Arch Linux User Repository

This package will verify the signature of the source package. The Mullvad code signing key is available here and instructions are here.

Feature request: refactor logic for upgrade/install:

• it is fine to enable systemd units on first install
• on upgrades, if the systemd units are disabled, they should stay disabled instead of re-enabled

Are you accepting patches? I can submit one.

After trying again, it seems to work. I don't know if something has changed in the meantime or not, but it looks like it is solved.

Thanks.

I got an error while trying to upgrade to 2023.3:

  • electron-builder  version=23.6.0 os=6.2.9-arch1-1
  • writing effective config  file=/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/builder-effective-config.yaml
  • packaging       platform=linux arch=x64 electron=21.3.3 appOutDir=/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/linux-unpacked
  • file source doesn't exist  from=/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/build/relays.json
  • building        target=deb arch=x64 file=/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/MullvadVPN-2023.3_amd64.deb
  ⨯ cannot execute  cause=exit status 1
                    out={:timestamp=>"2023-04-06T09:31:41.951239+0300", :message=>"Invalid package configuration: Cannot chdir to '/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/build/shell-completions'. Does it exist?", :level=>:error}

                    command=/home/name/.cache/electron-builder/fpm/fpm-1.9.3-2.3.1-linux-x86_64/fpm -s dir --force -t deb -d libgtk-3-0 -d libnotify4 -d libnss3 -d libxss1 -d libxtst6 -d xdg-utils -d libatspi2.0-0 -d libuuid1 -d libsecret-1-0 --deb-recommends libappindicator3-1 --deb-compression xz --architecture amd64 --after-install /tmp/t-jtTSGd/0-after-install.sh --after-remove /tmp/t-jtTSGd/1-after-remove.sh --description '
     Mullvad VPN client' --version 2023.3 --package /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/MullvadVPN-2023.3_amd64.deb --name mullvad-vpn --maintainer 'Mullvad VPN <support@mullvad.net>' --url 'https://github.com/mullvad/mullvadvpn-app#readme' --vendor 'Mullvad VPN <support@mullvad.net>' --deb-priority optional --license GPL-3.0 --no-depends --version 2023.3 --before-install /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/linux/before-install.sh --before-remove /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/linux/before-remove.sh /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/linux/mullvad-daemon.service=/usr/lib/systemd/system/mullvad-daemon.service /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/linux/mullvad-early-boot-blocking.service=/usr/lib/systemd/system/mullvad-early-boot-blocking.service /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/mullvad=/usr/bin/ /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/mullvad-daemon=/usr/bin/ /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/mullvad-exclude=/usr/bin/ /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist-assets/linux/problem-report-link=/usr/bin/mullvad-problem-report /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/build/shell-completions/mullvad.bash=/usr/share/bash-completion/completions/mullvad /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/build/shell-completions/_mullvad=/usr/local/share/zsh/site-functions/_mullvad /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/build/shell-completions/mullvad.fish=/usr/share/fish/vendor_completions.d/mullvad.fish '/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/linux-unpacked/=/opt/Mullvad VPN' /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_16x16.png=/usr/share/icons/hicolor/16x16/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_32.png=/usr/share/icons/hicolor/32x32/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_48x48.png=/usr/share/icons/hicolor/48x48/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_64.png=/usr/share/icons/hicolor/64x64/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_128.png=/usr/share/icons/hicolor/128x128/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_256.png=/usr/share/icons/hicolor/256x256/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_512.png=/usr/share/icons/hicolor/512x512/apps/mullvad-vpn.png /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/dist/.icon-set/icon_1024.png=/usr/share/icons/hicolor/1024x1024/apps/mullvad-vpn.png '/tmp/t-jtTSGd/2-Mullvad VPN.desktop=/usr/share/applications/mullvad-vpn.desktop'
                    workingDir=
[09:31:41] 'builder-linux' errored after 3.64 s
[09:31:41] Error: /home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/app-builder-bin/linux/x64/app-builder process failed ERR_ELECTRON_BUILDER_CANNOT_EXECUTE
Exit code:
2
    at ChildProcess.<anonymous> (/home/name/.cache/yay/mullvad-vpn/src/mullvadvpn-app/gui/node_modules/builder-util/src/util.ts:250:14)
    at Object.onceWrapper (node:events:627:26)
    at ChildProcess.emit (node:events:512:28)
    at ChildProcess.emit (node:domain:552:15)
    at maybeClose (node:internal/child_process:1098:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)
[09:31:41] 'pack-linux' errored after 16 s
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: mullvad-vpn-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
mullvad-vpn - exit status 4

What could it be?

Could you add some checks in the mullvad-vpn.install file so that it won’t try to execute systemctl when I’m using Artix? For example a simple check if the systemctl executable exists.

I've set mullvad to lockdown mode and autoconnect, but whenever my computer boots initially I have to right click mullvad in the system tray and click "reconnect" before my internet actually starts working. Mullvad says it's connected, but until I tell it to RE-connect my internet just stays non-functional. Haven't tested on base arch but I've tested on EndeavourOS and Garuda with the same issue on both. (Garuda on a wired ethernet, Endeavour on laptop integrated wifi card) Is this just me or is this a known issue with some workaround? (hopefully a workaround at least, I'm trying to setup my computer for remote access)

Updating the package gives me the following error:

error fetching mullvad-vpn-bin: fatal: not a git repository (or any of the parent directories): .git context: exit status 128

Does anyone know how to fix it?

Update: So, installing mullvad-vpn-bin manually without using yay worked... Huh...

@kaulfield: Mullvad bundles libwg, there is no need for wireguard-tools.

This dependency is necessary to connect through wireguard wireguard-tools. Add it please!

Is anyone else having trouble with journalctl -f being spammed by this ? Every second or so mullvad posts mullvad-daemon[571]: [mullvad_daemon::management_interface][DEBUG] get_tunnel_state to the log and it makes it difficult to read.

@askreceive: This is exactly the same version as mullvad-vpn. The pkgrel is unrelated.