Doesn't return correct system exit code

[Sebastian Heinlein]

Gksu doesn't return the exit code of the wrapped application:

Steps to reproduce:

1. open language support

2. run the following command in a terminal:
gksu synaptic && echo "spitze"

sudo works perfectly:
sudo synaptic && echo "spitze"

[Jouni Mettala (jouni-mettala)]

gksu and sudo are doing exactly same thing now. Closing. Feel free to reopen if this is still a problem.

[Sebastian Heinlein (glatzor)]

This is not true. Please test the bug before you close it.

[Martin Pitt (pitti)]

I just spent 20 minutes banging my head over my code before it occured to me that gksu was to blame. And indeed:

$ gksu false; echo $?
0

This is wrong.

[Gustavo Noronha Silva (kov)]

I agree... this is done like this to let applications calling gksu know if an error to the process of scaling privileges has happened. We could change that to a message printed to stderr instead, and make gksu return the error code returned by the application. What do you think, Michael?

[wodz (wodz)]

In my opinion gksu should return exit code of wrapped application. It is dumb to have graphical su/sudo behaving differently than console su/sudo:
wodz@skatol:~$ sudo false; echo $?
Password:
1
wodz@skatol:~$ gksu false; echo $?
Password:
0

[Jens (sirion)]

I have scripts that use something like

sudoCmd="sudo"
[...]
"$sudoCmd" "$0" "$@"

In the [...]-part there is code that decides whether a terminal is connected or not and then changes $sudoCmd if not.

Is there another way for me to query whether the programm called with gksu(do) succeeded?

[udude (igal)]

I'm also having issues w/this behavior. My scripts count on gksudo exit code to error when the executed command fails.
Does anyone know about any workarounds/gksudo replacements?
I don't even mind launching a new terminal running sudo or something in that direction...