Package Details: mullvad-vpn-daemon-bin 2026.2-1

Git Clone URL: https://aur.archlinux.org/mullvad-vpn-bin.git (read-only, click to copy)
Package Base: mullvad-vpn-bin
Description: The Mullvad VPN client app for desktop (daemon and CLI)
Upstream URL: https://www.mullvad.net
Licenses: GPL-3.0-or-later
Conflicts: mullvad-vpn-daemon
Provides: mullvad-vpn-daemon
Submitter: yochananmarqos
Maintainer: yochananmarqos
Last Packager: yochananmarqos
Votes: 162
Popularity: 5.33
First Submitted: 2019-11-20 18:07 (UTC)
Last Updated: 2026-04-28 18:28 (UTC)

Pinned Comments

yochananmarqos commented on 2020-04-07 17:37 (UTC)

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

Latest Comments

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

CMUYB commented on 2026-05-04 07:57 (UTC)

@rado84, thanks for your suggestion, but they've already fixed the issue upstream, see my edit.

rado84 commented on 2026-05-03 22:24 (UTC)

@CMUYB you can't make them patch anything, believe me, I've tried. Mullvad devs evade responsibility by saying "we don't support Arch" (I talked to them recently and that was their default line), the maintainer probably doesn't feel like it... So instead of waiting for solutions, I found my own solution. I know it's not exactly the solution you asked for but it's better than nothing.

  1. Disable early boot: sudo systemctl disable mullvad-early-boot-blocking.service sudo systemctl mask mullvad-early-boot-blocking.service sudo systemctl status mullvad-early-boot-blocking.service (to make sure it's dead)

  2. add these 3 lines to /etc/sudoers: [your username] ALL=(ALL) NOPASSWD: /usr/bin/systemctl start mullvad-daemon [your username] ALL=(ALL) NOPASSWD: /usr/bin/systemctl stop mullvad-daemon [your username] ALL=(ALL) NOPASSWD: /usr/bin/systemctl status mullvad-daemon

  3. sudo systemctl enable mullvad-daemon.service sudo systemctl start mullvad-daemon (add this to autostart and set delay of 4-5 seconds)

Sometimes it won't autostart with the system (pob. a bug, IDK), so you can create an alias to start it manually: alias vpnon="sudo systemctl start mullvad-daemon" and it won't even ask you for password. This one is safe to be executed without a password.

And after that you start the GUI app and connect wherever you want.

CMUYB commented on 2026-05-03 21:47 (UTC) (edited on 2026-05-03 22:04 (UTC) by CMUYB)

Is it possible to patch mullvad-early-boot-blocking.service to start before network-pre.target instead of basic.target?

The comment in there says the following:

This is required since almost no distributions use a network-pre.target

Arch does have network-pre.target. Whether it's used, I'm not sure.

I just noticed that this service writes stuff to /var/log before anything from fstab gets mounted. I have a separate Btrfs subvolume mounted to /var/log, yet I discovered mullvad-vpn/early-boot-fw.log and mullvad-vpn/early-boot-fw.old.log in a snapshot of my root subvolume. Not that these files are particularly large, but still.

EDIT: apparently, this is taken care of upstream - https://github.com/mullvad/mullvadvpn-app/commit/7b35f1f48d9b199343659a868e7f3ec8603ed4db. Just gotta wait for the next release.

rado84 commented on 2026-03-26 18:48 (UTC)

@yochananmarqos, I know it's a separate package. But it comes as a mandatory dependency to this one and on top of that systemd is trying (and failing, fortunately) to start it during system boot. At least make it so that systemd isn't trying to start it during system boot. Or ever, really.

yochananmarqos commented on 2026-03-26 15:29 (UTC)

@rado84: mullvad-vpn-daemon-bin is a split package as it can be used separately for CLI only. This effectively replaces the old mullvad-vpn-cli package. mullvad-vpn-bin cannot be used separately as it requires the contents of mullvad-vpn-daemon-bin. Upstream packages it all together. One can disable the service if one wishes.

rado84 commented on 2026-03-26 13:52 (UTC)

mullvad-vpn-daemon-bin should be optional dependency, not mandatory. Not only that it fails to startup (dmesg) but also daemonizing it should be the user's choice, not forced. I for one don't want my internet blocked/filtered in any way whenever I'm NOT using the VPN.

Wayward9 commented on 2026-02-25 22:48 (UTC)

Version 2025.14-5 seems to have fixed my issue

KMoretti commented on 2026-02-25 21:45 (UTC)

I get the following when trying to update from 2025.14-1 to 2025.14-4: error: failed to commit transaction (conflicting files) /usr/bin/mullvad exists in both 'mullvad-vpn-daemon-bin' and 'mullvad-vpn-bin' /usr/bin/mullvad-daemon exists in both 'mullvad-vpn-daemon-bin' and 'mullvad-vpn-bin' /usr/bin/mullvad-exclude exists in both 'mullvad-vpn-daemon-bin' and 'mullvad-vpn-bin' /usr/bin/mullvad-problem-report exists in both 'mullvad-vpn-daemon-bin' and 'mullvad-vpn-bin' Errors occurred, no packages were upgraded.

wilkins commented on 2026-02-25 20:50 (UTC)

Still fails.

ln: failed to create symbolic link '/home/user/.cache/paru/clone/mullvad-vpn-bin/pkg/mullvad-vpn-bin/usr/share/doc/mullvad-vpn-bin/': No such file or directory

Wayward9 commented on 2026-02-25 20:17 (UTC) (edited on 2026-02-25 20:31 (UTC) by Wayward9)

I got the following error message when updating from mullvad-vpn-bin 2025.14-1 -> 2025.14-2:

rm: cannot remove '/home/xxxx/.cache/paru/clone/mullvad-vpn-bin/pkg/mullvad-vpn-bin/usr/share/doc/mullvad-vpn-bin/changelog.gz': No such file or directory ==> ERROR: A failure occurred in package_mullvad-vpn-bin(). Aborting... error: failed to build 'mullvad-vpn-bin-2025.14-2 (mullvad-vpn-daemon-bin mullvad-vpn-bin)': error: packages failed to build: mullvad-vpn-bin-2025.14-2 (mullvad-vpn-daemon-bin mullvad-vpn-bin)

==> ERROR: An error has occurred during the update process The update has been aborted

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