GKSU says my password is wrong

apport information

apport information

Anyone? GKSU is compeletly broken for me because of this :(

Output with 'update-manager -d' looks like this:

kai@Kai-Desktop:~$ gksu -d wireshark
xauth: -97b24e73370d870ed5dac53fe8ac3c63
-
display: -:0-
final xauth: -97b24e73370d870ed5dac53fe8ac3c63
-
final display: -:0-
STARTUP_ID: gksu/wireshark/14947-0-Kai-Desktop_TIME1886786
gksu_context_run: buf: -Password: -
no password on keyring
DEBUG (run:after-pass) buf: -Password: -
-EBUG (run:post-after-pass) buf: -
-EBUG (run:post-after-pass) buf: -su: Authentication failure
-EBUG (auth_failed) buf: -su: Authentication failure

Status changed to 'Confirmed' because the bug affects multiple users.

I have the same problem here. Installed Ubuntu 12.04 frome alternate CD. Sudo works fine, gksu doesn't accept my password.

I tried to use gksudo instead and it works perfectly fine.

Hi everyone,

Is this bug solved? I've juste upgraded from 11.10 to 12.04 and neither gksu nor gksudo work with the option --user: both always answer that selected user password is wrong though this user belongs to sudo group.

An example:
Session opened with user "johan" that doesn't belong to sudo group and a try to open Thunar with user "administrateur" (member of the sudo group):

johan@johan-backup:~$ gksu -d -u administrateur thunar
No ask_pass set, using default!
xauth: /tmp/libgksu-KKWb4O/.Xauthority
STARTUP_ID: gksu/thunar/3548-0-johan-backup_TIME2551651
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: administrateur
cmd[7]: --
cmd[8]: thunar
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-KKWb4O/.Xauthority
xauth_env: /home/johan/.Xauthority
dir: /tmp/libgksu-KKWb4O
No ask_pass set, using default!
xauth: /tmp/libgksu-mDF1RN/.Xauthority
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: administrateur
cmd[7]: --
cmd[8]: thunar
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-mDF1RN/.Xauthority
xauth_env: /home/johan/.Xauthority
dir: /tmp/libgksu-mDF1RN
No ask_pass set, using default!
xauth: /tmp/libgksu-s1ID6U/.Xauthority
cmd[0]: /usr/bin/sudo
cmd[1]: -H
cmd[2]: -S
cmd[3]: -p
cmd[4]: GNOME_SUDO_PASS
cmd[5]: -u
cmd[6]: administrateur
cmd[7]: --
cmd[8]: thunar
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-s1ID6U/.Xauthority
xauth_env: /home/johan/.Xauthority
dir: /tmp/libgksu-s1ID6U
johan@johan-backup:~$

3 password trials and that always fails with "Wrong password".

Distro:
Xubuntu 12.04 Precise x86_64

GKsu version 2.0.2

All packages are up to date

uname -a:
Linux johan-backup 3.2.0-29-generic #46-Ubuntu SMP Fri Jul 27 17:03:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise

Regards,
Johan

No this is not solved and is driving me insane. I cannot use any application that relies on GSKU and nobody seems to care about this imo major bug.

Still have this issue in Quantal!

Also i get the following assertion printed to the console.
"(gksu:8263): Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed"

During the next week, I will try Linux Mint 13 (based on Ubuntu 12.04) to see if I can find the same bug. If this bug is present, I will try last the Debian distro Ubuntu is based on.

Same bug with Linux Mint 13 and with Debian 6.0.5 (Xfce) that gives:
«
johan@johan-backup:~$ gksu -d -u administrateur thunar
No ask_pass set, using default!
xauth: /tmp/libgksu-8s2a0j/.Xauthority
STARTUP_ID: gksu/gdmsetup/3144-0-johan-backup_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]: administrateur
cmd[7]: --
cmd[8]: gdmsetup
buffer: -GNOME_SUDO_PASS-
brute force GNOME_SUDO_PASS ended...
Yeah, we're in...
xauth: /tmp/libgksu-8s2a0j/.Xauthority
xauth_env: /home/johan/.Xauthority
dir: /tmp/libgksu-8s2a0j

(gksu:3144): GLib-CRITICAL **: g_str_has_prefix: assertion `str != NULL' failed
»

-- BUT --

It seems to be a sudo bug or limitation, when looking at this bug report: https://savannah.nongnu.org/bugs/?24318

I cite the answer:
« Please note that the temporary xauth file is created with working permissions with the su backend (gksu -w).

gksu -w -u firefoxuser firefox

That workaround does not provide the configurability of sudo, though. So a fix for sudo would be much appreceated. »

So I tried using the not-always-well documented "-w" option (aka "--su-mode"; see 'man gksu') and it works, both on the last Debian (6.0.5) and Ubuntu (12.04)...

AND "sudo -u user command" (gksu calls "sudo" by default, exactly same as gksudo) doesn't seem to match the philosophy of calling a program using sudo privileges of another user...

By the way, with some programs (such as the small optional "system-config-samba") that works only when calling directly the root user ("gksu -w -u root system-config-samba")...

This seems not to be the same issue I have. Neither "gsku -w synaptic", nor "gsku -w -u root synaptic" work for me :/

I tried purging and reinstalling gksu again, but it didn't help :/

(gksu:6930): Gdk-CRITICAL **: IA__gdk_error_trap_pop: assertion `gdk_error_traps != NULL' failed

Did you try to investigate around su and sudo? Because gksu calls them regarding the option you passed (or not). In my case, the source of the problem is sudo.

By the way, I did manually set a root password in command line with "sudo passwd". Then I can connect as root in command line using "su" (with no option). Probably that's why "gsku -w -u root synaptic" works in my case...

Well, sudo works fine for me. It's really only gsku that doesn't work.
Thats what confuses me.

Luckily there aren't may Apps that use gksu anymore.

Unless you want to open nautilus instead of using the terminal.

Same problem here in 13.04.

Apparently gksu uses 'su' by default, which won't work in Ubuntu (since root user is disabled and cannot be switched to). The solution is really simple: run gksu-properties and set “Authentication mode” to “sudo” – see: http://askubuntu.com/a/57452/19674