gksu does not work in dapper for me

[Ralph]

Gksu does not work in dapper right now. It's always giving me the error message that the password was wrong.

Gksudo on the other hand works just fine.

[sam tygier (samtygier)]

that is the correct behaviour unless you have set up a root pass word.

su is for change user (usually to root)
sudo is for run a program with the priviliges of another user.

also gnome-sudo should be used instead of gksudo, i believe for enviromental variable reasons.

see https://wiki.ubuntu.com/RootSudo for details of the sudo system

[Ralph (ralph-ubuntu)]

Then let me be more specific:
synaptic, gnome-user-manager, gdebi try to use gksu by default, which of course does not work!

[Michael Vogt (mvo)]

Thanks for your bugreport.

Gksu has a gconf option that makes it use sudo as default backend when gksu is called. In dapper we switched to use that instead of modifying every desktop file that uses gksu to gksudo.

Please send the output of:
$ gconftool-2 --get --ignore-schema-defaults /apps/gksu/sudo-mode

It should be "No value set for `/apps/gksu/prompt' if you haven't modified it with gconf-editor or gconftool-2 --set

You can use this to set it:
$ gconftool-2 --set /apps/gksu/sudo-mode --type boolean true

[Ralph (ralph-ubuntu)]

Ah, I see.

The output is (in German):
ralph@ubuntu:~$ gconftool-2 --get --ignore-schema-defaults /apps/gksu/sudo-mode
»/apps/gksu/sudo-mode« wurde kein Wert zugewiesen

Which translates to no value set.

Setting gksu to use sudo as you described works like a charm.
Thank you.

[Michael Vogt (mvo)]

Thanks for testing this.

There is still a bug somewhere, because you should get sudo mode as default with the current gksu. Can you please post the result of:

$ grep -A 3 "sudo-mode" /usr/share/gconf/schemas/gksu.schemas

Thanks,
 Michael

[Ralph (ralph-ubuntu)]

ralph@ubuntu:~$ grep -A 3 "sudo-mode" /usr/share/gconf/schemas/gksu.schemas
      <key>/schemas/apps/gksu/sudo-mode</key>
      <applyto>/apps/gksu/sudo-mode</applyto>
      <owner>gksu</owner>
      <type>bool</type>
      <default>false</default>

[Michael Vogt (mvo)]

Thanks! This is very odd because gksu is shiped with <default>true</default> in ubuntu/dapper.

Can you please run:
$ dpkg -l gksu
now and tell me the result?

On dapper, that should be "1.3.6-1ubuntu6". What do you get?

[Ralph (ralph-ubuntu)]

Weird, I'm getting 1.3.6-1ubuntu1

Dapper is fully upgraded though.
Maybe it's a ppc specific problem, as I'm using a ppc machine here?

[Michael Vogt (mvo)]

On Fri, Jan 20, 2006 at 12:33:29PM -0000, Ralph Schuengel wrote:
> Public bug report changed:
> https://launchpad.net/malone/bugs/28866
>
> Comment:
> Weird, I'm getting 1.3.6-1ubuntu1
>
> Dapper is fully upgraded though.
> Maybe it's a ppc specific problem, as I'm using a ppc machine here?

Yes, it's ppc specific, apparently later versions of gksu don't build
on ppc, I look into this now.

Cheers,
 Michael

--
Linux is not The Answer. Yes is the answer. Linux is The Question. - Neo

[Stephen McClain (smcclain)]

I'm getting this same problem, and I'm running a fully updated dapper on a 686 kernel. Same gksu version and all. So I'm thinking this isn't exactly a PPC problem.

[Sebastien Bacher (seb128)]

The gksu task is enough for that

[Michael Vogt (mvo)]

Stephen, can you please run the gconftool-2 commands mentioned earlier in this thread and post the result here?

Thanks,
 Michael

[Sean Harshbarger (harshy)]

Looks like the same issue on amd64 test beds. gksu is still at 1.3.6-1ubuntu1 as of 2/28/06.

Booleans and settings follow the same as above.

[Michael Vogt (mvo)]

The current version of gksu in dapper is up-to-date in all official arches. Can you confirm that this problem is fixed for you (when you upgrade)?

Thanks,
 Michael

[Matt Zimmerman (mdz)]

We're fairly confident this is fixed (simple matter of the package being out of date on some architectures(, and no one has responded to the request for confirmation, so closing.