how 2 sudo? [Solved by changing to gnsu]

[jpg153]

After upgrading from 14.0 to 14.1 I installed the wheelsudo as described.

However, when keying in i.e.

Code: Select all

sudo gparted

I am prompted for the password.
However, regardless what password I key in, the one for the user or the one for root, its wrong.
The user as well as root are a member of the group "wheel".

In addition, when I try to run gparted form the xfce menue/bar, I receive an error message

Code: Select all

could not execute >>gksudo /usr/bin/gparted %f <<
child process >>gksudo<< could not be executed (file or directory not found)

Where to look up whats wrong?

Thanks.

[gapan]

If you just added your user to the wheel group, then you need to at least log out and log back in for the changes to take effect.

And you most probably need the gnsu package.

Otherwise, you can install the ktsuss package and keep using the root user as you did in 14.0.

[jpg153]

Gapan,

thanks for your answer.

Well, the user setup (wheel) was done some reboots ago...

ktsuss is installed as I don't need sudo - I was always fine with the bevaviour.

And all other programs seem to work with the "ktsuss" way, execpt "gparted".
When I open a terminal session and enter

Code: Select all

su root

I am asked for the password. Keyed in the secret I enter

Code: Select all

gparted

and it comes up as it should.
So maybe there is a slight error in the way gparted is addressed via the menu?

thanks

[knome]

Code: Select all

could not execute >>gksudo /usr/bin/gparted %f <<
child process >>gksudo<< could not be executed (file or directory not found)

In 14.0 the path for gparted is /usr/sbin/gparted. Does that help at all?

[jpg153]

Well,

at least, yes in 14.1 it is also in /usr/sbin and not /usr/bin .

But, is that really the problem?
If so, where can I fix it?

However, I the issue with sudo remains or...?

[gapan]

Let's take it from the top.

Running as your user, post the output of the following commands:

Code: Select all

whoami
echo $PATH
which gksudo
file `which gksudo`

as well as the contents of your /etc/sudoers file.

[jpg153]

ok,

here are the results of the German jury

Code: Select all

jpg[~]$ whoami
jpg
jpg[~]$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/jre/bin:/usr/lib64/qt/bin:/usr/local/sbin:/sbin:/usr/sbin
jpg[~]$ which gksudo
which: no gksudo in (/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/jre/bin:/usr/lib64/qt/bin:/usr/local/sbin:/sbin:/usr/sbin)
jpg[~]$ file 'which gksudo'
which gksudo: ERROR: cannot open `which gksudo' (No such file or directory)
jpg[~]$ 

Obviously, there is no "gksudo"...

[gapan]

You need to install the gnsu package if you want to have gksudo available. Also post the contents of your /etc/sudoers file.

[jpg153]

Hi,

well, as said, I dont need the sudo solution as I could live with how it was (and is) in 13.x and 14.0.

I did not touch the sudoers file...so I think the content is pretty much standard/generic:

Code: Select all

## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias	WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users.  These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias	ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands.  Often used to group related commands together.
# Cmnd_Alias	PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
# 			    /usr/bin/pkill, /usr/bin/top

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file.  Note that other programs use HOME to find   
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods.  Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output

##
## Runas alias specification
##

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

## Uncomment to allow members of group wheel to execute any command
# %wheel ALL=(ALL) ALL

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo	ALL=(ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw  # Ask for the password of the target user
# ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d
## (the '#' here does not indicate a comment)
#includedir /etc/sudoers.d

[jpg153]

After reading the Blog about the ktsuss, gksu...problem I installed gnsu and it seems fine.