Need help sudoers file

[chicknfangz]

[quote author=Jerry link=topic=2777.msg21360#msg21360 date=1455750825]
[quote author=chicknfangz link=topic=2777.msg21358#msg21358 date=1455748242]

OK will do jerry Thanks

[chicknfangz]

Understand this, the output of your original post means nothing to me. As I can not see any modifications you've made. Now if you use the command I posted and copy the lines mentioned in your original post and share them... (line 19 and 25) we can FIX them for you. Otherwise you can simply use the default shared.


With no modifcations this is the default sudoers file:

Code:

#
# 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

# Members of the admin group may gain root privileges
%admin 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

Using the command

Code:

pkexec visudo

Will allow you to edit the sudoers file properly, and you can resume using sudo after this is solved.

I thought you wanted the error output i posted. sorry i think i get you now.

you want me to do that command. And show you what i have in my sudoers so you see what i did wrong to help me fix it

[shaggytwodope]

Indeed, the two lines that provide the error message. If you can share them we can fix it.

In general for security or other reasons, error messages like that one do not provide much details. This can not be debugged without more detailed info in alot of cases. The pkexec command uses a different means to access the stuff sudo can be used for. But it's not a replacement in the future.  So keep that in mind.

[chicknfangz]

OK so i fixed it i think.

did sudo leafpad /etc/sudoers. this came up

I did however get this

Code:

(leafpad:3674): IBUS-WARNING **: The owner of /home/chicknfangz/.config/ibus/bus is not root!

Code:

#
# 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

# Members of the admin group may gain root privileges
%admin 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

I still can't go into root with su says su: Authentication failure

[chicknfangz]

OK never mind

i did

Code:

sudo grub-mkconfig -o /boot/grub/grub.cfg

and it worked so i guess i don't need su. no point in going into root and messing stuff up  ;D

[chicknfangz]

Thanks shaggytwodope & jerry & rokytnji  ;D

[rokytnji]

Re read my post and you will see sudo -i is how I get root access in terminal in Linux Lite. Glad you got it sorted. I am busy with garage remodeling.
Hence why I am not on a computer during the day.