On Thursday 19 November 2009 11:20:42 pm DenverD wrote:
The problem is that when you run file manager (Dolphin) in super user mode any task launched from dolphin should also run as super user.
i'm not at all sure that what you say there is a true statement..
that is, why would i (or the Dolphin development team) want _every_ task launched with a root powered file manager to have root powers?
Why? Because you can't even open a file for which USER does not have permissions even after supplying a password for root.
Dolphin is a *file manager* and as a file manager with root powers it should be able to manage (move, copy, delete, etc) *files* as root, not launch root powered anything..
now, if it were (say) a "root application launch pad" then if i launched kwrite from it, i'd expect that to also have root powers..
but, today if i'm using any root powered file manager i expect it to only have file manager duties root powered..
So moving, deleting of files is ok, but opening a text file or pdf is something you have to open a shell for?
anyway, my opinion is this 'problem' is not a problem, Dolphin is working as designed..
I'm not sure it is designed that way. In fact comments in man dbus-launch seem to suggest that this was intended, but has not been yet implemented. As I mentioned in a prior post, using Konqueror in superuser mode on kde3 allowed any operations kong performed, opened files, install rpms, what ever.
and, finally: do not log into KDE, GNOME, Xfce or any other *nix GUI system as root....ever...just don't do it...it is like begging for problems:
Please spare me the pontification . -- If stupidity got us into this mess, then why can't it get us out? - Will Rogers -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org