Code: Select all

greg@greg-Inspiron-5767 ~/Downloads $ kdesudo dolphin
Executing Dolphin as root is not possible.
greg@greg-Inspiron-5767 ~/Downloads $ kdesudo kate
Executing Kate as root is not possible. To edit files as root use:
SUDO_EDITOR=kate sudoedit <file>
greg@greg-Inspiron-5767 ~/Downloads $ SUDO_EDITOR=kate sudoedit ~/testfolder/fred.txt
sudoedit: /home/greg/testfolder/fred.txt: editing files in a writable directory is not permitted
Hangup


I tried this which is pretty new info https://iwf1.com/linux-users-bypass-exe ... privileges but allas i could not even run dolphin as user after making these changes.

Why? & are we expected to just use the terminal for root actions now ?

They think its dangerous for noobs to play with the file-system as root with a GUI ! well you want to see what a mess i can make with the terminal as root

System: Host: greg-Inspiron-5767 Kernel: 4.10.0-42-generic x86_64 (64 bit) Desktop: KDE Plasma 5.11.4 Distro: neon Dev-Stable 16.04 xenial

you do not half to try to launch Kate with kdesudo any more ,,,,,,,just open the file and edit ,,when going to save it kate will ask for your password .

Dolphin on the other hand ,,,,,well you cant use it as root any more , BUT their is work being done to it to allow it to work in much the same way as Kate .

maybe by the time we move to the 18.04-LTS ,,,,,,but for now you can install Krusader and it will still work in root mode for you .

their are security concerns that come with running any GUI as root and when things move to Wayland it will not allow any root started GUI's at all ,,,,,,,,

have a look at this thread https://www.kubuntuforums.net/showthrea ... post407873

VINNY

thats cool info about kate , i really don't keep up but then again i'd have to be reading 50 hours a day to even stand a chance.

I installed a gnome file browser & editor and setup dolphin service menus to run them as root for now (but after what you have sid i can remove the editor). I hardly ever use either as root but as i say i can cause a whole lot of more damage through terminal than a GUI when i do need to.

Iv read this whole thread tonight https://forums.opensuse.org/showthread. ... t-possible

I personally think they should have waited until they were ready with the finished product (use of polkit) before taking this "half measure" , You might notice that the slogan they once displayed at their website -- "Experience Freedom!" -- is no longer there ^^. Cheers

Why do you need to run a file manager as root? Either you do a "server admin" kind of task, then you can certainly use cp to copy a file, or you don't, then I don't see a use case where you need it. In which case do you need to modify files which do not belong to your user in an end user desktop setup nowadays?

It was the same with Opensuse Tumbleweed. There was such a negative user reaction when root access was blocked (for Dolphin or Kate) that opensuse removed the changes. It all felt too much like MS to me. With Neon I just use thunar and leafpad instead.

scummos wrote:Why do you need to run a file manager as root? Either you do a "server admin" kind of task, then you can certainly use cp to copy a file, or you don't, then I don't see a use case where you need it. In which case do you need to modify files which do not belong to your user in an end user desktop setup nowadays?

I must have needed to move/copy/edit root files about 50 times in the last 3 years or so , usually to try and fix all the broken things i keep finding every time i almost get a decent working disrto/DE

I know its an edit but just this distro the grub misses all (except 1) of my other bootable OS, had to use root edits on grub to gain access to the other 5. Then there was the screen tearing which i seem to remember i had to alter some root files on another distro. If everything just worked then yes i would agree with you but they dont

"Experience Freedom!" -- is no longer there ^^. Cheers

It's a security measure I have mixed feelings about.