<div class="gmail_quote">2012/5/15 David Edmundson <<a href="mailto:david@davidedmundson.co.uk" target="_blank">david@davidedmundson.co.uk</a>> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On Sat, May 12, 2012 at 6:02 PM, Terence Simpson <<a href="mailto:tsimpson@kubuntu.org">tsimpson@kubuntu.org</a>> wrote: > On 12 May 2012 17:44, David Edmundson <<a href="mailto:david@davidedmundson.co.uk">david@davidedmundson.co.uk</a>> wrote: >> There is never a case to run "kdesudo kate /someFile". >> >> Use "sudoedit /someFile". This uses root to copy the file to /tmp, you >> then run the default editor (hopefully kate) as yourself, then >> whenever the file changes you copy the file back (as root). >> >> Not really answering the question/real problem, but making sure people >> do this makes the problem less bad. > > You really can't expect (normal) users to open a terminal and use > sudoedit, which would use nano by default (unless they knew how to > change /etc/alternatives/ stuff). > Ideally, kdesudo would copy the running users style/theme settings, > possibly by using a custom $KDEHOME when launching the application. > (Or just use polkit) > </div>That's a valid point. Well the ideal solution still seems to be to update kate to have a "save as root" which again uses Polkit for the actual saving. </blockquote><div> "Save as root" would be a good solution only in cases when the file can be read but not written to by the user.. But what about files that cannot even be opened by the user? like /etc/fuse.conf ? Admittedly, this case is quite rare. Donatas </div></div>