menu launcher (gksu.desktop) still uses gksudo instead of gksu

Thanks for your bug. That's an easy change and will be done before dapper

Thanks for your bugreport.

This problem is fixed in the current bzr tree and will be part of the next uplaod.

It seems, that gnome-software-properties.desktop icon is identifical to update-manager icon :-/
I think that in the same submenu (in this case System->Administration) should't be same icons for 2 or more launchers

gksudo was replaced with gksu in all .desktop files from /usr/share/applications folder in Baltix GNU/Linux version 1.2rc.
We still need technology, which should check/replace gksudo with gksu if some package with gksudo in .desktop file is installed.
It would be wise to create a policy for ubuntu/debian packages, which should require to use gksu, not gksudo in packages.

Same bug in gksu package - menu launcher (/usr/share/applications/gksu.desktop file) still uses gksudo instead of gksu :(

There are also other packages, which .desktop files in /usr/share/applications still uses gksudo instead of gksu, simple text file search for gksudo in body of .desktop files can help to find these.

Maybe it would be easier way to fix such bugs, than reporting a bug for every package ?

Thanks for this report.

I fixed gksu and gnome-system-tools today to no longer use gksudo. If there are more packages you notice with gksudo instead of gksu, please let me know.

My gnome-system-tools menu items use gksu, as described above. However, this stops them from working. I get the same problem that is described in https://launchpad.net/distros/ubuntu/+source/sudo/+bug/5100 - it tells me that my password is invalid. Running, for example, disks-admin from a root shell gives me exactly the same error. However, running disks-admin from a normal user shell works perfectly - it asks me for my password, and then runs fine.

This would seem to indicate that disks-admin does its own sudo'ing, and doesn't require gksu or gksudo to elevate its permissions for it? This would explain the problem, too - gksu becomes root, and runs disks-admin, which then tries to use the root user's password, which of course does not exist.

Should these desktop files be altered to remove the 'gksu' from the launch command?