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.

Mullvad released new version 2024.3, but seem to be only some minor changes for Linux:

• Fix GUI not working on Ubuntu 24.04 by adding an AppArmor profile.
• Service failed to start when IPv6 was disabled in the kernel.

By the way, the issue is fixed with 2024.3-beta1.

Thanks very much for the link, @yochananmarqos. I, too, was not aware this was an acknowledged bug, sorry. Anyway, turning on IPv6 fixed the problem for me.

Hi, since this update, I have no connection. As soon as I uninstall the application, I get my connection back. With the previous version, I had no problem. The daemon is launched via systemctl. Here's part of the log file with the error :

ERROR] Error: Unable to initialize daemon
Caused by: Tunnel state machine error
Caused by: Unable to spawn offline state monitor
Caused by: The route manager returned an error
Caused by: Internal route manager error
Caused by: Failed to get a route for the given IP address
Caused by: Received a netlink error message Operation not supported (os error 95)
<\code><\pre>

@yochananmarqos, sorry, I was not aware. The GitHub issue link you shared has a work around and it has worked for me.

cc @rf2020.

@rf2020: Apparently it also happens on Ubuntu, see the related upstream issue.

Folks, remember, this package is the official Debian / Ubuntu package unpacked. This is not the place to report issues with the program itself.

I can confirm that the 2024.2-1 mullvad-vpn-bin (and mullvad-vpn, too) package creates a mullvad-daemon service that fails to start, after 5 automatic retries.

systemctl status mullvad-daemon.service
× mullvad-daemon.service - Mullvad VPN daemon
     Loaded: loaded (/usr/lib/systemd/system/mullvad-daemon.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Sat 2024-05-04 11:05:51 CEST; 14s ago
   Duration: 57ms
    Process: 3647 ExecStart=/usr/bin/mullvad-daemon -v --disable-stdout-timestamps (code=exited, status=1/FAILURE)
   Main PID: 3647 (code=exited, status=1/FAILURE)
        CPU: 32ms

May 04 11:05:51 teleo systemd[1]: mullvad-daemon.service: Scheduled restart job, restart counter is at 5.
May 04 11:05:51 teleo systemd[1]: mullvad-daemon.service: Start request repeated too quickly.
May 04 11:05:51 teleo systemd[1]: mullvad-daemon.service: Failed with result 'exit-code'.
May 04 11:05:51 teleo systemd[1]: Failed to start Mullvad VPN daemon.

This was after installing and then rebooting. I can't start the service manually either. I haven't tried the early boot blocker status, but internet access is blocked until the package is uninstalled. Yes, I've tried uninstalling, rebooting and reinstalling, doesn't help. Not sure how to trace things from here.

@carport: Well, if you can figure out what happened by checking logs, let me know if there's anything that needs to be done.

If you contact Mullvad support and they say they don't support the AUR package, let them know the source is their own signed .deb using the same pre/post install scripts.

@yochananmarqos, thanks.Yes, I think removing the services it creates might have fixed the issue. But since it happened in two computers, IHMO it's highly likely it's an issue with the package (or package + something else that came from Arch repo). It's easily reproducible on my end. If I install, the issue comes back :)