FS#45735 - [sudo] 1.8.14.p2-1 - execute command without password only works from terminal
Attached to Project:
Arch Linux
Opened by nerdix (nerdix) - Tuesday, 21 July 2015, 18:07 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 22 July 2015, 12:02 GMT
Opened by nerdix (nerdix) - Tuesday, 21 July 2015, 18:07 GMT
Last edited by Jan Alexander Steffens (heftig) - Wednesday, 22 July 2015, 12:02 GMT
|
Details
Description: execting sudo /usr/bin/systemctl suspend does
not work anymore when not run inside a terminal.
Additional info: * 1.8.14.p2-1 /etc/sudoers %power ALL=(ALL) NOPASSWD:/usr/bin/systemctl suspend ~/.fluxbox/menu [exec] (Supend) {sudo /usr/bin/systemctl suspend} my user is in group power and this was working with sudo 1.8.14.p1-1 and prior versions, now I have to run avove command from an xterm to get it working: [exec] (Supend) {xterm -e 'sudo /usr/bin/systemctl suspend'} same if invoked from fbrun I tried to put the following in /etc/sudoers Defaults !requiretty but no luck. Downgrading to sudo 1.8.14.p1-1 fixed it. If no bug please explain how to get back old behaviour. Steps to reproduce: |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Wednesday, 22 July 2015, 12:02 GMT
Reason for closing: Fixed
Additional comments about closing: sudo 1.8.14p2-2
Wednesday, 22 July 2015, 12:02 GMT
Reason for closing: Fixed
Additional comments about closing: sudo 1.8.14p2-2
-- error message --
sudo: main: unable to allocate memory
-- steps to reproduce --
TMP_SYS='tmp_sys'
mkdir ${TMP_SYS}
pacstrap -c -d ${TMP_SYS} base sudo
systemd-nspawn --quiet --directory=${TMP_SYS} whoami
systemd-nspawn --quiet --directory=${TMP_SYS} sudo -u nobody whoami
http://www.sudo.ws/repos/sudo/rev/c58cce92d5e0
Simply reverting that commit fixes the issue for me. It's a rather big commit, so I don't have a patch ready... I'll report this upstream tomorrow evening (but I guess someone else will beat me to it ;-)).
http://bugzilla.sudo.ws/show_bug.cgi?id=706
Full ack, especially since this is a core package
How do you get the error message about "unable to allocate memory"? I can't find anything related in my logs. When trying to trace it, it works because invoked from a tty/pty...
So how do I test if my problem is related to the "unable to allocate memory" error?
gksudo does not work at all with this new sudo package...