Bug 178590

Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Several times to modify a configuration file in Linux et similia you should edit a text file (e.g. /etc/X11/xorg.conf, /etc/fstab, /boot/grub/menu.lst and so on). To be able to save in its original position you should run an editor as privileged user (generally root); in particular if you want to do that from a graphical editor you need to do some bad things:
- find a (unintuitive) way to start a graphical editor as root (e.g. Alt+F2 followed by "kdesu kwrite");
- run a whole application as root (that's bad for security I think).


NOTE: I don't know if it's doable of if it actually makes sense.

My idea is to somehow integrate KSaveDialog with PolicyKit-KDE; for example:
- check if the user running the GUI can write to destination folder;
- if he can then save and do not prompt anything as usual;
- if he can't then open another dialog asking if he wants to abort the save or he wants to be asked for password to perform an action (save the file) as privileged user;
- if the user chooses to be asked for password then do the things needed to actually save the file (PolicyKit-KDE?).