I don't know about "nemo", but it has been my experience with other file managers, a file manager that is not intended to used as root might not work as expected when you try to use it as root. There are file managers designed and made to be used by root, IE: "root thunar", MC, and there probably are others.
Generally, it is best to use the cli when working as root, all though yes, some people try using the normal user GUI's, and occasionally we get questions from them wondering how to repair the system they borked.
Post by ChameleonScales » 2019-05-18 08:12
I rename files.
Renaming system files that require root to do this is a good way to bork a system,..is there some reason you do not simply use sudo or su , like normal people would, and the CLI, ?
IE:
- Code: Select all
# mv foo foo-newname
Not recommended, since the 'mv' command moves the file to one with a new name,
it is better to use 'cp'
- Code: Select all
# cp foo foo-newname
That way you still have a copy of the original file, with the original name, in case whatever file name you changed does not work as expected any more.
Maybe read this:
From:
https://wiki.archlinux.org/index.php/Running_GUI_applications_as_root Warning: All of the following methods have security implications that users should be aware of. As put by Emmanuele Bassi, a GNOME developer: "there are no *real*, substantiated, technological reasons why anybody should run a GUI application as root. By running GUI applications as an admin user you're literally running millions of lines of code that have not been audited properly to run under elevated privileges; you're also running code that will touch files inside your $HOME and may change their ownership on the file system; connect, via IPC, to even more running code, etc. You're opening up a massive, gaping security hole [...]."[1]