<![CDATA[Dev1 Galaxy Forum / [SOLVED] System nag about Mullvad, even though Mullvad now working correctly]]> http://dev1galaxy.org/viewtopic.php?id=7870 Sat, 28 Mar 2026 12:52:45 +0000 FluxBB <![CDATA[Re: [SOLVED] System nag about Mullvad, even though Mullvad now working correctly]]> http://dev1galaxy.org/viewtopic.php?pid=62929#p62929 Thanks - that thread sorted it out. Now clean, no nags smile

]]> Sat, 28 Mar 2026 12:52:45 +0000 http://dev1galaxy.org/viewtopic.php?pid=62929#p62929 <![CDATA[Re: [SOLVED] System nag about Mullvad, even though Mullvad now working correctly]]> http://dev1galaxy.org/viewtopic.php?pid=62926#p62926 https://dev1galaxy.org/viewtopic.php?pid=62815#p62815
Should solve it.

]]> Sat, 28 Mar 2026 11:31:32 +0000 http://dev1galaxy.org/viewtopic.php?pid=62926#p62926 <![CDATA[[SOLVED] System nag about Mullvad, even though Mullvad now working correctly]]> http://dev1galaxy.org/viewtopic.php?pid=62919#p62919 Firstly, I'm only an intermediate user (despite almost 20 years of Linux), so somewhat technically challenged.

I installed Mullvad VPN successfully (although maybe untidily) on Excalibur SysVinit, and it's working fine with the GUI fully functional.

However, every time I'm updating other things, this nag appears along with all the normal output :

Setting up mullvad-vpn (2026.1) ...
/var/lib/dpkg/info/mullvad-vpn.postinst: line 6: systemctl: command not found
dpkg: error processing package mullvad-vpn (--configure):
 installed mullvad-vpn package post-installation script subprocess returned erro
r exit status 127

Even though Mullvad is already set up and working fine, the system thinks it should try again.

Google AI has this opinion:

If you are on a non-systemd distribution (like Devuan or MX Linux):
The Mullvad package expects systemd by default. To fix the broken install, you can manually edit the post-installation script to bypass the check:
Open the script: sudo nano /var/lib/dpkg/info/mullvad-vpn.postinst.
Comment out or replace the lines containing systemctl (usually around line 6).
Run sudo apt install -f to finish the configuration without the error.
Note: You will likely need to start the daemon manually or via a custom init script: sudo /usr/bin/mullvad-daemon -v.

I can live with the nag if necessary, as I don't want to break the install.

Any ideas please? Thank you smile

=================

]]> Sat, 28 Mar 2026 02:29:24 +0000 http://dev1galaxy.org/viewtopic.php?pid=62919#p62919