I notice the bottom of their install page that you linked, has a link to download the configs to use openvpn. That package is in our repos. Have you, or would you be willing to try that?
I do know that different distros use different package naming schemas and have different group names/numbers. All of these can cause serious issues. Sadly developers can’t build for every individual distro.
This may be a bumb question please forgive my ignorance but if an app cant find a library because of different naming would it be possible to create a symlink with the name the app expects to find?
Does OpenVPN require the command-line to use? I would rather that be a last resort, especially because Mullvad are phasing out support for OpenVPN to focus solely on WireGuard
I have no idea. I have not used it. I was just noticing that it was something they offered. Without an account number, I could not go further. It just looked as if it could buy some time.
Thanks for suggesting it though. I didn’t see that until you brought it up. There’s a WireGuard version of the same option, but along with OpenVPN, they both appear to be CLI tools, but I didn’t read into it a lot. I’ll try to use that if I can’t get this dependency issue resolved, I just very much prefer to use the official GUI is all.
I’m heading to bed now so thanks everyone for the help you’ve given me so far, I’ll see if I get any more replies tomorrow.
Until a solution to the GUI version is found, I can confirm the wireguard cli method works for Mullvad VPN using these instructions:
My system is running ROME Plasma6 AMD CPU (newer than 2017)
Prerequisites:
You need Wireguard:
sudo dnf install wireguard-tools
You will also need to install iptables:
sudo dnf install iptables
The rest of the instructions work as written in this tutorial.
NOTE:
Pay attention if you use the “kill switch” option in the config generator, you will not be able to connect to the internet without adding the “Local network sharing” option to the config file.
If you need help figuring out your local network address:
One method to find your local network setting is to open the terminal (Konsole) and enter the command:
ip addr
This will print out your network protocols. Don’t worry, it will not change anything on your system.
You are looking for the “inet” entry. Do NOT use the “inet 127.0…” address. That is your local loopback address.
Find an entry for “inet 10.0.0.8/24” or “inet 192.168.0.35/24” or “inet 192.168.1.54/24”. Your numbers may be a little different than mine. The important bits are the 10.0.0 , 192.168.0 , or the 192.168.1 - the last digit(s) will be different for you.
Examples:
If your inet address is or is similar to:
10.0.0.8/24 then use “! -d 10.0.0.0/24” in the config file
If it is:
192.168.0.35/24 then use “! -d 192.168.0.0/24”
If it is:
192.168.1.54/24 then use “! -d 192.168.1.0/24”
This should get you up and going.
The GUI method is preferred as this method is very manual, and requires remembering various commands to start and stop. I set up some bash scripts to start and stop the process for me so I don’t have to remember everything.
Hope this helps! Let me know if I need to clarify anything or add further instruction.
This is their recommendation:
If you do a sudo dnf in mullvad-vpn --refresh it should sync up the repo and give you a list of the packages it is missing. We can then cross reference and possibly force the install.
Again the RPM is checking for specific package names rather than the required libraries (as in the .so and other files themselves), you do already have the needed dependencies installed as far as I understood, they are just named differently in OM repos so the installer is confused since the RPM is intended for fedora (not all RPMs check for dependencies like this but those that do can be a problem)
Judging by the output you posted it skipped the Mullvad package itself so nothing was in fact installed (since dnf considers it the broken package in question). I tried the rpm -i --force --nodeps way and indeed the app appeared in my menu and is working fine, so I recommend you do try
Also tested if it uninstalls properly, and yeah it does
If the app has an updater mechanism, you’ll probably need to manually update but that’s kinda how it goes with having fedora packages on OM
Brilliant! This worked and I now have the GUI client installed, thank you very much!
Could you tell me the command to uninstall it too, please?
Glad to help
That’ll be dnf remove mullvad-vpn
So now that I’ve found a workaround to install the app, what would be a proper solution to this problem? Is this on the part of OpenMandriva to change specific package names so that applications like Mullvad VPN can be installed without the user having to mess around like I did? I’m ignorant here, so if that’s not the solution, then what is?
Can we make a tutorial from this topic?
You could make a request to have it packaged in Packages and features requests , or you can make a request here:
There is unfortunately no way to anticipate how they may name things in the future.
