Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Mullvad vpn client issue [SOLVED]

Message
Author
Hooten
Forum Novice
Forum  Novice
Posts: 32
Joined: Sat May 05, 2018 5:52 pm

Mullvad vpn client issue [SOLVED]

#1 Post by Hooten » Sun Sep 23, 2018 9:35 am

I'm using Mullvad vpn and they released a newer version of their client that after installation brakes synaptic and cannot remove it also. I haven't find any solution online like "apt-get install -f". I've reinstalled MX in the end to remove it and contacted Mullvad support but they didn't find a solution to this issue. Is any chance to be a fixed from the OS itself?

Thank you in advance.
Last edited by Hooten on Fri Sep 28, 2018 4:54 pm, edited 1 time in total.

User avatar
dreamer
Forum Regular
Forum Regular
Posts: 200
Joined: Sun Oct 15, 2017 11:34 am

Re: Mullvad vpn client issue

#2 Post by dreamer » Sun Sep 23, 2018 8:15 pm

Maybe you can try the Qomui client. It's compatible with Mullvad.

https://forum.mxlinux.org/viewtopic.php ... &hilit=vpn

https://github.com/corrad1nho/qomui

Hooten
Forum Novice
Forum  Novice
Posts: 32
Joined: Sat May 05, 2018 5:52 pm

Re: Mullvad vpn client issue

#3 Post by Hooten » Mon Sep 24, 2018 11:40 am

dreamer wrote:
Sun Sep 23, 2018 8:15 pm
Maybe you can try the Qomui client. It's compatible with Mullvad.

https://forum.mxlinux.org/viewtopic.php ... &hilit=vpn

https://github.com/corrad1nho/qomui
I've tried Qomui but when i launch it i press start and after that a message pops up says "Qomui service failed to start".

User avatar
dreamer
Forum Regular
Forum Regular
Posts: 200
Joined: Sun Oct 15, 2017 11:34 am

Re: Mullvad vpn client issue

#4 Post by dreamer » Mon Sep 24, 2018 4:18 pm

Hooten wrote:
Mon Sep 24, 2018 11:40 am
dreamer wrote:
Sun Sep 23, 2018 8:15 pm
Maybe you can try the Qomui client. It's compatible with Mullvad.

https://forum.mxlinux.org/viewtopic.php ... &hilit=vpn

https://github.com/corrad1nho/qomui
I've tried Qomui but when i launch it i press start and after that a message pops up says "Qomui service failed to start".
Probably related to (lack of) systemd. Reboot and when GRUB is shown choose MX advanced options. Then choose the option that says "MX...systemd" and boot that one. Then start Qomui and see if you get the same error.

Hooten
Forum Novice
Forum  Novice
Posts: 32
Joined: Sat May 05, 2018 5:52 pm

Re: Mullvad vpn client issue

#5 Post by Hooten » Tue Sep 25, 2018 9:16 am

Actually it's a systemd thing. Everything works when i boot in MX with systemd. Is it possible to enable only one program to use systemd (like mullvad client) without booting in MX with systemd?

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1709
Joined: Wed Apr 11, 2018 5:09 pm

Re: Mullvad vpn client issue

#6 Post by fehlix » Tue Sep 25, 2018 9:46 am

Hooten wrote:
Mon Sep 24, 2018 11:40 am
I've tried Qomui but when i launch it i press start and after that a message pops up says "Qomui service failed to start".
Would start the daemon from the cli like this

Code: Select all

/opt/mullvad-vpn/resources/mullvad-daemon" -v --disable-stdout-timestamps
# or if privileged start is needed
sudo /opt/mullvad-vpn/resources/mullvad-daemon" -v --disable-stdout-timestamps
make the vpn available for you?
If yes, I assume that's just a matter of putting this exec-starter into init.d startup script.
Which is generally spoken a kind of converting the mullvad-vpn systemd-service into an init.d-startup "service" .

EDIT: And for the Qomui startup service try this

Code: Select all

/usr/bin/env qomui-service
# or if privileged start is needed
sudo /usr/bin/env qomui-service
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Hooten
Forum Novice
Forum  Novice
Posts: 32
Joined: Sat May 05, 2018 5:52 pm

Re: Mullvad vpn client issue

#7 Post by Hooten » Tue Sep 25, 2018 10:35 am

fehlix wrote:
Tue Sep 25, 2018 9:46 am
Hooten wrote:
Mon Sep 24, 2018 11:40 am
I've tried Qomui but when i launch it i press start and after that a message pops up says "Qomui service failed to start".
Would start the daemon from the cli like this

Code: Select all

/opt/mullvad-vpn/resources/mullvad-daemon" -v --disable-stdout-timestamps
# or if privileged start is needed
sudo /opt/mullvad-vpn/resources/mullvad-daemon" -v --disable-stdout-timestamps
make the vpn available for you?
If yes, I assume that's just a matter of putting this exec-starter into init.d startup script.
Which is generally spoken a kind of converting the mullvad-vpn systemd-service into an init.d-startup "service" .

EDIT: And for the Qomui startup service try this

Code: Select all

/usr/bin/env qomui-service
# or if privileged start is needed
sudo /usr/bin/env qomui-service
Unfortunately, same for Mullvad.

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1709
Joined: Wed Apr 11, 2018 5:09 pm

Re: Mullvad vpn client issue

#8 Post by fehlix » Tue Sep 25, 2018 10:40 am

Hooten wrote:
Tue Sep 25, 2018 10:35 am
Unfortunately, same for Mullvad.
oops.. no error message?
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Hooten
Forum Novice
Forum  Novice
Posts: 32
Joined: Sat May 05, 2018 5:52 pm

Re: Mullvad vpn client issue

#9 Post by Hooten » Tue Sep 25, 2018 10:48 am

fehlix wrote:
Tue Sep 25, 2018 10:40 am
Hooten wrote:
Tue Sep 25, 2018 10:35 am
Unfortunately, same for Mullvad.
oops.. no error message?
Client just stuck at "Connecting to daemon".

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 1709
Joined: Wed Apr 11, 2018 5:09 pm

Re: Mullvad vpn client issue

#10 Post by fehlix » Tue Sep 25, 2018 10:53 am

Hooten wrote:
Tue Sep 25, 2018 10:48 am
fehlix wrote:
Tue Sep 25, 2018 10:40 am
Hooten wrote:
Tue Sep 25, 2018 10:35 am
Unfortunately, same for Mullvad.
oops.. no error message?
Client just stuck at "Connecting to daemon".
I meant, when you start the above daemon , do you got any messages?
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

Post Reply

Return to “General”