Limitation for sudo? about argos HOT 8 CLOSED

Well it seems working fine here. I did the following test ~/.config/argos/uptime.3s.sh

#!/usr/bin/env bash

echo "Test"

echo "---"
echo "Run uptime with sudo | bash='sudo uptime' terminal=false" 

if you run the journalctl /usr/bin/gnome-shell -f command on a seperate terminal then you can see the output of the command when you click on Test > Run uptime with sudo

On my case I can execute sudo without password, I think the best that you can do it's move your script to some place and then just call it from your argos script

from argos.

Normally using when you use the sudo command you need to type your password (this is what prevent the script to run completely in Argos)

You've visudo ?

from argos.

This is why I was wanting to sudo (an extension to check and notify user if any hardware/software issue... and smartctl requires sudo)

from argos.

I dont know if the | make that the command dont run properly, a simple workaround that I said on my previous comment (probably I didnt express well my english is a bit bad)

the workaround is move what you need execute with sudo to an external script, example

# ~/.scripts/sudo_uptime.sh
echo mypassword | sudo -kS uptime

dont forget add execution permissions to tour external script chmod +x ~/.scripts/sudo_uptime.sh then your argos config it'll be something like

#!/usr/bin/env bash

echo "Test"
echo "---"
echo "Run uptime with sudo | bash='~/.scripts/sudo_uptime.sh' terminal=false" 

I've tested this by myself and it's working fine (I enable password for my sudo)

from argos.

You purpose exactly what I tried in first place ;)

Your code will "almost work" because the command is not used in the script itself, it's a button... but if you use the button the command will not run properly due to the password required.

Try to store the result of the command in a variable, you will understand.

#!/usr/bin/env bash

system_uptime=`echo mypassword | sudo -kS uptime`

echo "Test"
echo "---"
echo "uptime: $system_uptime" 

from argos.

the journalctl command result in:
janv. 29 07:21:44 Serveur-NAS org.gnome.Shell.desktop[2526]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4e00028 (test.c.sh )

from argos.

Whatever the issue is here, it has nothing to do with Argos. Argos runs executable files, that's all. It doesn't care whether those files in turn invoke sudo, or top, or any other program.

The "Buggy client" warning shown above is a GTK+ bug that has been around forever, and has nothing to do with Argos either.

from argos.

If someone stumbles upon this issue: At least in my case it seemed that the prompt for the password caused the problem. After setting an empty prompt with -p '' the script executes as expected.

SOMETHING=$(sudo -Sk -p '' <<< $password some_command)
echo "${SOMETHING}"

from argos.