Idea #14054: Use of gksu in synaptic, nautilus, gedit etc...

Written by natureflow the 4 Oct 08 at 09:34. Category: System.
Related to: Nothing/Others. Status: New

Description

See GDebi and update-manager for great use of gksu. You can start the application without root rights and be able to get them when needed. Please implement this great feature in synaptic, nautilus, gedit and may other applications, too.

Tags: (none)

Attachments

No attachments.

Duplicates

[Report a duplicate and merge its votes to this idea]

Comments

ampers wrote on the 4 Oct 08 at 11:28

I would love to see this in Gnome Commander

Hands up anyone old enough to remember Norton Commander, back in the pre windows days of DOS?

Gnome Commander is almost identical. Right down to the blue panels.

Ampers.

Ape wrote on the 4 Oct 08 at 12:06

Every time when something says: "You do not have the permissions necessary to do X." or similar there should be a button called "Do it as root". That would start gksu and ask for the password.

juno eclipse wrote on the 4 Oct 08 at 14:52

I think it should be handled by PolicyKit...

francois wrote on the 4 Oct 08 at 15:11

yeah policykit should be used, not gksu.

testit wrote on the 14 Oct 08 at 17:19

NOTE: Policykit is only for d-bus actions.

adelie wrote on the 16 Oct 08 at 18:29

synaptic: update manager already does this, and running synaptic from the menu already uses gksu. The only way to start synaptic without root is from a graphical terminal or the run command. Maybe what they really need to do is add the "unlock" button, or ask for password upon 'apply', though it appears to e intentional as synaptic does grab a lock on apt as soon as it starts up. Too often I try to use apt-get from a command line while synaptic has been open because I was browsing, and it fails due to lock... but that is my own fault. I think the more appropriate suggestion is "bring synaptic authentication in line with other ubuntu administrative tools".

other tools: maybe what would be interesting, and think I may look into writing a script to do this, but there is already something called the Module::Process::UID that allows you to "portably get, set, and switch the current process’s real, effective, and saved user IDs". I LOVE using xkill from the run (alt-F2) command. maybe a similar tool should be implemented that lets you click a window to change the effective UID of the process parent to that window. I think that would be better than adding another button to everything you try to do. I like the current setup where necessity for authentication can always be anticipated by the user rather than somewhat random requests for the users password. That is just asking for people to get lazy with their password use.

Post your comment