I installed Fedora 43 with this command distrobox create -i registry.fedoraproject.org/fedora:43 --init --additional-packages "systemd" -n test then I installed Mullvad VPN with these commands sudo dnf config-manager addrepo --from-repofile=https://repository.mullvad.net/rpm/stable/mullvad.repo and sudo dnf install mullvad-vpn. Once it’s finished, I tried to type mullvad status but it gives an error message

Error: Management RPC server or client error  

Caused by:  
         0:   transport error  
         1:   No such file or directory (os error 2)  
         2:   No such file or directory (os error 2)  

How to solve this issue ? I just want to use mullvad-cli

  • Pamboo@piefed.socialOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    12 hours ago

    nix and mullvad vpn are installed on my steam deck under steamos 3.7 now but it’s the same issue as before (Management RPC server or client error). Also I can open the Mullvad VPN GUI application which works but there is a message on the app :

    Unable to contact the Mullvad system 
    service, your connection might be unsecure. 
    Please troubleshoot or send a problem 
    report by clicking the "Learn more" button.
    

    I don’t know how to solve this issue

    • Fubarberry@sopuli.xyzM
      link
      fedilink
      English
      arrow-up
      1
      ·
      9 hours ago

      Alright, so I probably can’t help you with this without having some personal hands on experience with it.

      What’s probably happening is it’s trying to install a system level systemd service, but you can’t due to the steam deck being locked down. Your options would be to unlock the filesystem, find a way to install the Mullvad systemd service as a user instead, or figure out how to use systemd-sysext to install I as a system extension separate from the immutable filesystem.

      Of those, I’m guessing the best solution would be the middle option, assuming you can get the right systemd mullvad-daemon.service file. Once you have it, it could be placed in ~/.config/systemd/user/ and enabled with systemctl --user enable mullvad-daemon.service. But as stated, the catch is you need the mullvad-daemon.service file, and I’m not sure the best way to do that. Maybe you could unlock the filesystem , let it install it as a system level service, and then convert it to a user level service? Either way it’s complicated and I’d have to mess around with it myself to figure out what would work.