Mullvad vpn client issue [SOLVED]

[Hooten]

Ah thats, looks nice. The path differs from the one I gave above.
What happens if you start from the command line this

Code: Select all

/opt/Mullvad\ VPN/resources/mullvad-daemon -v --disable-stdout-timestamps

Note the backslash before the space.
Would the daemon run ?

"Houston, we've got lift off"
Man you made it run, even Mullvad support didn't find a solution. I'm gonna send them an email right now. Thank you again .

[fehlix]

What I would do now:
Get rid of the "space" with the path name like this:

Code: Select all

sudo ln -s /opt/Mullvad\ VPN /opt/MullvadVPN

( Spaces with linux path are known to be reason for lot's of issues!)
You just create a Starter-Icon on the Desktop :
Right-click on the Desktop "Create Starter"
Enter Namer :MullvadVPN
Comnand:

Code: Select all

/opt/MullvadVPN/resources/mullvad-daemon -v --disable-stdout-timestamps

Now without the space.
Now clicking on the MullvadVPN-Desktop starter,
will have your VPN ready to connect.
If need to run this automatically after login,
we can prepare this later...

[Hooten]

What I would do now:
Get rid of the "space" with the path name like this:

Code: Select all

sudo ln -s /opt/Mullvad\ VPN /opt/MullvadVPN

( Spaces with linux path are known to be reason for lot's of issues!)
You just create a Starter-Icon on the Desktop :
Right-click on the Desktop "Create Starter"
Enter Namer :MullvadVPN
Comnand:

Code: Select all

/opt/MullvadVPN/resources/mullvad-daemon -v --disable-stdout-timestamps

Now without the space.
Now clicking on the MullvadVPN-Desktop starter,
will have your VPN ready to connect.
If need to run this automatically after login,
we can prepare this later...

I've got this issue now:
$ sudo ln -s /opt/Mullvad\ VPN /opt/MullvadVPN
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

[fehlix]

I've got this issue now:
$ sudo ln -s /opt/Mullvad\ VPN /opt/MullvadVPN
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

Intersting, somebody messed around with you'r sudoers files/direcctory.
I'm sure it wasn't you
This is urgent and need to be fixed. As this might become a sever securtiy issue for you/system.
Reboot from Live media.
Mount the partition rootMX17.
Do this first ..., I check mean while the proper commands..

[Hooten]

I've got this issue now:
$ sudo ln -s /opt/Mullvad\ VPN /opt/MullvadVPN
sudo: /etc/sudoers is owned by uid 1000, should be 0
sudo: no valid sudoers sources found, quitting
sudo: unable to initialize policy plugin

Intersting, somebody messed around with you'r sudoers files/direcctory.
I'm sure it wasn't you
This is urgent and need to be fixed. As this might become a sever securtiy issue for you/system.
Reboot from Live media.
Mount the partition rootMX17.
Do this first ..., I check mean while the proper commands..

ooops, i just searched it on the web and i did this: pkexec chown root:root /etc/sudoers /etc/sudoers.d -R

How bad was this?

[fehlix]

ooops, i just searched it on the web and i did this: pkexec chown root:root /etc/sudoers /etc/sudoers.d -R
How bad was this?

Not so bad. But still let's check the permissions:

Code: Select all

sudo ls -al /etc/sudoers*

Post the output here. Paste beteewn the code-tags please.
Let see what is in sudoers, which apprears to have been changed:

Code: Select all

sudo cat /etc/sudoers

(Paste between the code-tags. )

[Hooten]

ooops, i just searched it on the web and i did this: pkexec chown root:root /etc/sudoers /etc/sudoers.d -R
How bad was this?

Not so bad. But still let's check the permissions:

Code: Select all

sudo ls -al /etc/sudoers*

Post the output here. Paste beteewn the code-tags please.
Let see what is in sudoers, which apprears to have been changed:

Code: Select all

sudo cat /etc/sudoers

(Paste between the code-tags. )

Code: Select all

r--r----- 1 root root  669 Jun  5  2017 /etc/sudoers

/etc/sudoers.d:
total 28
drwxr-xr-x   2 root        root         4096 Sep 24 18:39 .
drwxr-xr-x 151 hooten   hooten 12288 Sep 27 20:12 ..
-r--r-----   1 root        root          989 Apr 27  2017 antixers
-r--r-----   1 root        root          607 Jun  9 04:50 mxers
-r--r-----   1 root        root          958 Jun  5  2017 README

-----
Mod note: Post command output between [code] [/code] for better readability.

[Hooten]

ooops, i just searched it on the web and i did this: pkexec chown root:root /etc/sudoers /etc/sudoers.d -R
How bad was this?

Not so bad. But still let's check the permissions:

Code: Select all

sudo ls -al /etc/sudoers*

Post the output here. Paste beteewn the code-tags please.
Let see what is in sudoers, which apprears to have been changed:

Code: Select all

sudo cat /etc/sudoers

(Paste between the code-tags. )

And this: #

Code: Select all

# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaults	env_reset
Defaults	mail_badpass
Defaults	secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

# Host alias specification

# User alias specification

# Cmnd alias specification

# User privilege specification
root	ALL=(ALL:ALL) ALL

# Allow members of group sudo to execute any command
%sudo	ALL=(ALL:ALL) ALL

# See sudoers(5) for more information on "#include" directives:

#includedir /etc/sudoers.d

-----
Mod note: Post command output between [code] [/code] for better readability.

[fehlix]

Ok the permissions seem now to be ok, file date and size seem also to be unchanged.

[Hooten]

Ok the permissions seem now to be ok, file date and size seem also to be unchanged.

Phew... you scared me for a moment. Thank you again by the way for the mullvad fix