Steam Hardware
A place to discuss and support all Steam Hardware, including Steam Deck, Steam Machine, Steam Frame, and SteamOS in general.
As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title
The following is a list of suggested flairs:
[Deck] - Steam Deck related.
[Machine] - Steam Machine related.
[Frame] - Steam Frame related.
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.
If your post is only relevant to one hardware device (Deck/Machine/Frame/etc) please specify which one as part of the title or by using a device flair.
These are not enforced, but they are encouraged.
Rules:
- Follow the rules of Sopuli
- Posts must be related to Steam Hardware or Steam OS in an obvious way.
- No piracy, there are other communities for that.
- Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
- This is a place of civil discussion, no trolling.
- Have fun.
view the rest of the comments
If you didn't see any major errors when running the previous command, then you maybe just need to restart your deck (or alternatively log out and log back in).
Especially when installing things through non-normal means, the path may not have updated for something newly installed.
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 :
I don't know how to solve this issue
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 withsystemctl --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.I found the
mullvad-daemon,nix-daemonfiles in/nix/store/svf..............-user-environment/bin/mullvad, I don't know that's it. I copied and pasted both files into~/.config/systemd/user/then I open the terminal from~/.config/systemd/user/, I typedsystemctl --user enable mullvad-daemon.service, it says :Failed to enable unit: Unit mullvad-daemon.service does not exist