You are not logged in.

Pages: 1

#1 2015-07-21 15:20:11

andrekp
Member
Registered: 2012-06-07
Posts: 112

Problem after sudo update [SOLVED]

I did an update today that included a sudo update.  Afterwords, sudo is apparently giving me problems.

I use Openbox and wrote my own menu XML files.  Among the program entries are a few that open an app as root so that I can do things that require such permissions. 

The command I use in the menu files is "gksudo application".  Previously, it would ask for my sudo password, then run the application.  This no longer does anything at all when run from a menu and nothing when run from a command line.

If I change the command to "sudo application", it does noting from the menu and runs it from the command line (after asking for my usual sudo password)

If I change the command to "gksu application",  it asks for the root user password, then runs the application.  (this is expected behavior).

Below is the relevant portion of my sudoers file.  I am a member of the wheel group.

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

ALL ALL=NOPASSWD: /usr/sbin/hddtemp

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

# Reset environment by default
Defaults      env_reset
# Set default EDITOR to nano, and do not allow visudo to use EDITOR/VISUAL.
Defaults      editor="/usr/bin/nano", !env_editor

I feel like I am missing something simple here, but I'm just not seeing it.  Searches I have done explain to use the gksudo command, as I have been, but it no longer seems to work.    I'm not sure where to look beyond this.  Any ideas what's going on?

Thanks

Last edited by andrekp (2015-07-23 12:02:18)

Offline

#2 2015-07-21 20:31:15

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Problem after sudo update [SOLVED]

You could set `gksu` to ask for your user password instead of the root password.

gconftool-2 --set --type boolean /apps/gksu/sudo-mode true

Are you infected with Wetiko?

Offline

#3 2015-07-21 20:38:49

nixpunk
Member
Registered: 2009-11-23
Posts: 271

Re: Problem after sudo update [SOLVED]

Try invoking gksudo with -d for debug info.

Offline

#4 2015-07-21 21:09:49

soundman
Member
From: Istanbul, Turkey
Registered: 2010-06-05
Posts: 17

Re: Problem after sudo update [SOLVED]

http://bugzilla.sudo.ws/show_bug.cgi?id=706
https://bugs.archlinux.org/task/45735?p … tring=sudo

Offline

#5 2015-07-22 17:42:26

andrekp
Member
Registered: 2012-06-07
Posts: 112

Re: Problem after sudo update [SOLVED]

Tried running debug mode with meld:

DIR: ~/$ gksudo -d meld
No ask_pass set, using default!
xauth: /tmp/libgksu-BlyVsR/.Xauthority
STARTUP_ID: gksudo/meld/3100-0-bokuarch_TIME0
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: root
cmd[7]: --
cmd[8]: meld
buffer: -sudo: main: unable to allocate memory-
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
buffer: --
brute force GNOME_SUDO_PASS ended...
No password prompt found; we'll assume we don't need a password.
xauth: /tmp/libgksu-BlyVsR/.Xauthority
xauth_env: /home/andrekp/.Xauthority
dir: /tmp/libgksu-BlyVsR

I'm not sure what it means.  I LOOKS like it can't integrate with the password authentication or something, but this isn't really clear to me.

Offline

#6 2015-07-22 22:01:37

nixpunk
Member
Registered: 2009-11-23
Posts: 271

Re: Problem after sudo update [SOLVED]

Have you tried with -u option and the username you are logged into X with?

Offline

#7 2015-07-22 22:10:44

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Problem after sudo update [SOLVED]

The sudo package has been updated today and `gksudo` now works as expected on my system.

Are you infected with Wetiko?

Offline

#8 2015-07-23 09:33:33

jedijimi
Member
From: Hartford Wi
Registered: 2013-12-10
Posts: 93

Re: Problem after sudo update [SOLVED]

I added the line

username ALL=(ALL) ALL
Not sure if this was a correct fix, but found it on the mighty google search.

Crude matter we are not, Luminous beings we are

Offline

#9 2015-07-23 11:09:05

loafer
Member
From: the pub
Registered: 2009-04-14
Posts: 1,772

Re: Problem after sudo update [SOLVED]

jedijimi wrote:

I added the line

username ALL=(ALL) ALL
Not sure if this was a correct fix, but found it on the mighty google search.

What were you trying to "fix"?  The gksudo issue is resolved by the package update.

All men have stood for freedom...
For freedom is the man that will turn the world upside down.
Gerrard Winstanley.

Offline

#10 2015-07-23 12:01:59

andrekp
Member
Registered: 2012-06-07
Posts: 112

Re: Problem after sudo update [SOLVED]

Todays sudo update to 1.8.14.p3-2 fixed the problem.  Obviously it was a bug in sudo.

marked as solved.

Offline

Pages: 1

Board footer

Powered by FluxBB