kdesudo and the config problem
david at davidedmundson.co.uk
Mon May 14 22:57:14 UTC 2012
On Sat, May 12, 2012 at 6:02 PM, Terence Simpson <tsimpson at kubuntu.org> wrote:
> On 12 May 2012 17:44, David Edmundson <david at davidedmundson.co.uk> 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)
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.
I hunted through kate's bugzilla to see if this had come up, as I
assume it would have done. There is a WONTFIX from 4 years ago which
says "there's no real technical way to do this". Which is no longer
Obviously that would only fix kate, are there any things people would
(think they) want to run as root?
Coming up with some a crazy scheme to copy styles and themes across
problems is a solution to a problem that shouldn't exist, and not one
(IMHO) we should encourage.
> Terence Simpson
> kubuntu-devel mailing list
> kubuntu-devel at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
More information about the kubuntu-devel