Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#7910 - gksu hangs

Attached to Project: Arch Linux
Opened by Laurent Hilsz (lolo) - Wednesday, 29 August 2007, 16:31 GMT
Last edited by Paul Mattal (paul) - Thursday, 10 January 2008, 04:03 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Paul Mattal (paul)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08 Don't Panic
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

gksu hangs after upgrading to pam-0.99.8.1-3 (in both su and sudo modes).


Additional info:
* package version(s)

pam 0.99.8.1-3.1
gksu 2.0.0-2
libgksu 2.0.5-1

Steps to reproduce: on the command line, start a program with gksu <progname> after typing "sudo -k". Nothing happens.
This task depends upon

Closed by  Paul Mattal (paul)
Thursday, 10 January 2008, 04:03 GMT
Reason for closing:  Fixed
Comment by Laurent Hilsz (lolo) - Wednesday, 29 August 2007, 18:09 GMT
I made a mistake. Only gksu in sudo mode hangs.
Comment by Laurent Hilsz (lolo) - Saturday, 01 September 2007, 15:28 GMT
Here is the debug output of the command line 'gksudo -u root -d gedit' :

No ask_pass set, using default!
xauth: /tmp/libgksu-V8CA2Q/.Xauthority
STARTUP_ID: gksudo/gedit/21111-0-Archie_TIME3076720320
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]: gedit
buffer: -Mot de passe : -
buffer: --
...
brute force GNOME_SUDO_PASS ended...
No password prompt found; we'll assume we don't need a password.

sudo: pam_authenticate: Erreur de conversation
xauth: /tmp/libgksu-V8CA2Q/.Xauthority
xauth_env: /home/lau/.Xauthority
dir: /tmp/libgksu-V8CA2Q
Comment by Laurent Hilsz (lolo) - Saturday, 17 November 2007, 06:51 GMT
Investigating further, it appears that the problem comes from the fact sudo now translates the password prompt. The result is that gksu doesn't work anymore in this case.

See : http://groups.google.com/group/linux.debian.bugs.dist/browse_thread/thread/79a14de4eff5d094/e6e5bf9be056d911

Could this be fixed with a patch in sudo package ? gksu is totally unusable in sudo mode on non-english locales.
Comment by Massimo Branchini (max.bra) - Saturday, 17 November 2007, 19:55 GMT
Confirmed:
gksu 2.0.0-2
libgksu 2.0.5-1
on sudo 1.6.9p7-1

with sudo new password prompt translation, gksu in sudo-mode is not able to parse "Password:" in non-english locales.

'LANG=C gksu <someprogram>' (in sudo-mode) give the expected graphical sudo-able user password request.

Laurent Hilsz (lolo) seems to have linked the only solution available on the web.
Comment by Roman Kyrylych (Romashka) - Sunday, 18 November 2007, 10:14 GMT
Attaching the patch for convenience.
Comment by Paul Mattal (paul) - Sunday, 30 December 2007, 23:27 GMT
The sudo 1.6.9p10-2 in testing seems now to correctly honor the -p flag.

Is it then possible to solve this by fixing gksu? Or does it already work? I can't get gksu to work here, even with my LANG=en_US.utf8 locale.

Seems to be it would be preferable to patch gksu if we can, now that sudo (I think) works properly.
Comment by Massimo Branchini (max.bra) - Monday, 31 December 2007, 13:14 GMT
already with sudo 1.6.9p9-1, in italian locale gksu in sudo mode is working
if other locale users can confirm, this bug can be closed.

definitely a sudo problem, not gksu one.
Comment by Paul Mattal (paul) - Monday, 31 December 2007, 15:43 GMT
Okay, I'm probably just doing something wrong getting gksu to work for me. (Do I first need to run a gksu-run-helper or something? It complains about that and then tells me my password is incorrect while expecting "gksu: waiting".

If nobody else complains, I will close this bug in a week.
Comment by Massimo Branchini (max.bra) - Tuesday, 01 January 2008, 14:26 GMT
i don't think so. whit p9-1 version, simply run out of the box.

this is my console output now:

$ gksu -u root -d gedit
No ask_pass set, using default!
xauth: /tmp/libgksu-zLEvVA/.Xauthority
STARTUP_ID: gksu/gedit/8933-0-rage_TIME3077255824
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]: gedit
buffer: -GNOME_SUDO_PASSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-zLEvVA/.Xauthority
xauth_env: /home/max/.Xauthority
dir: /tmp/libgksu-zLEvVA

since p9-1 version, sudo consider again the '-p GNOME_SUDO_PASS' parameter and, voilĂ ...

my config:
nothing special in /etc/sudoers
no *SUDO* environment variable set
only "sudo mode" flagged in gconf->/apps/gksu

did you have any password prompt override from past testing? i don't have any other idea about your problem...

however, happy new year and keep up the good work ;-)

Loading...