I’d noticed some of this before on 11.1 with KD4 versions but until now, I’ve had KDE3 options so it hasn’t bothered me:
If (I know some may not approve but it’s there and the way I like to work) If I open Dolphin in SuperUser mode, I can not open a file using KWrite or Kate. , eg. Open with KWrite will give “KDEInit could not launch /usr/bin/kwrite”
If I su in a terminal and try to use KWrite or Kate, I get the error messages: “Communication error with launcher. Exiting!”. The programs do open though but I can’t open files using the menu. If I try, I get a popup window saying “Could not start process. Cannot talk to klauncher. Not connected to D-Bus server.”
How was it before on KDE3 and Konqueror in SuperUser mode? Did the default settings allow that then?
Anyway, for the length of a likely root Dolphin session, I prefer the convenience to what be a very slight risk if someone hacked the PC, I’m suppose. Can’t say I’m bothered about parents on the LAN doing it.
I sort of agree with tpe, but also understand the need/desire for integrity of the security architecture.
Is there a way to get Dolphin(in root mode) to open files in “Read-Only” mode, such as the “Preview in embedded text editor” that was in Konquerer-KDE3?
I find I use file manager-super user a lot when tracking down problems. Frequently need to be able to look everywhere (root privileges) but really only want to read-only.
Switching out to a console for a true edit session, when needed, would be a necessary but workable solution.
How about merge the 2 thread?
Any way, in order to answer “palladium”:
If you don’t need root power, then do not have it.
Look, in console you can
rm -rf . /
Nobody stops you from that kind of mistakes. So, if I make a mistake, its all my fault!
When I open a file manager in SU mode, I choose to do so and I do know the risks. The reason I use a DE is because it’s simple. Otherwise, I would stay in console mode!
For example (I have to test it, because I had no chance so far). I have a bounch of server (>20) that run in my inside network (=secure). Shall I be able to edit a configuration file via fish, like I did with Konq3? I will try that and report back.