![]() ![]() Oct 31 02:07:12 fedora mullvad-daemon: Caused by: Failed to load address cache Oct 31 02:07:12 fedora mullvad-daemon: Caused by: Unable to create RPC client ![]() ![]() Oct 31 02:07:12 fedora mullvad-daemon: Error: Unable to initialize daemon Oct 31 02:07:12 fedora mullvad-daemon: Caused by: Permission denied (os error 13) Oct 31 02:07:12 fedora mullvad-daemon: Caused by: Failed to open the address cache file Main PID: 12701 (code=exited, status=1/FAILURE) Process: 12701 ExecStart=/opt/Mullvad VPN/resources/mullvad-daemon (code=exited, status=1/FAILURE) Loaded: loaded (/etc/systemd/system/rvice disabled vendor preset: disabled)Īctive: failed (Result: exit-code) since Sun 02:07:12 CEST 4s ago Here is the output of when I then run sudo systemctl status mullvad × rvice - Mullvad Daemon ![]() When running this service with sudo systemctl start mullvad, it doesn’t give any output, but does not start as I’d expect it to. This is the service file that I made ĮxecStart='/opt/Mullvad VPN/resources/mullvad-daemon' Since /etc/systemd/system/ was mutable I decided to try and write my own service file. I assumed this is because the OS is immutable, so in the install it did not create the rvice file as the /lib/systemd/system/ directory is immutable. It seemed to install correctly, but upon running Mullvad VPN, I get stuck on a screen that shows “Connecting to Mullvad system service…”.Īfter some digging, I found out that in order for me to use Mullvad, the daemon needs to be running in the background, but the rvice file for Systemd was missing. rpm file from their site and layered it with rpm-ostree install. Since I use Mullvad VPN, I downloaded the. Just today I did a fresh Fedora Silverblue 34 install, and all went well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |