How do I start Nautilus as root?
I've got a problem with Nautilus in Ubuntu 12.04 LTS.
When I run the command
gksu nautilus /, the password ask box appears and I type my super-user password, then the password box disappears and Nautilus is not opened.
When I try to open Nautilus as a normal user in with the command
nautilus, the folder is opened.
When I try in terminal
$ sudo nautilus
I got the following error
$ sudo nautilus / ** (nautilus:8523): WARNING **: Command line `dbus-launch --autolaunch=2c8ce9b7da2257c2609b749700000007 --binary-syntax --close-stderr' exited with non-zero exit status 1: Autolaunch error: X11 initialization failed.\n Could not parse arguments: Cannot open display:
How can I fix this error?
You could also try installing nemo (linux mint file browser), which has an "open as root" option.
Then type your own password just like when using sudo.
Gksudo man page: http://linux.die.net/man/1/gksudo
I use Ubuntu 12.04 LTS 2 week ago, and i m ok will gksu nautilus command. and yesterday, I face with that problem, type comand " gksu nautilus / " and I type my password . no folder window open up .. so, i cant edit some file in root.
How to run
Nautilusas administrator with
GVfs method tested in Ubuntu 18.04
Use the GVfs admin backend, just add
admin://to the beginning of the full path to your preferred directory.
Open Nautilus the usual way and press Ctrl+L to enable typing in the address-bar, and then enter for example
admin:///usr/to open the
Enter your admin password when prompted and you will see something like this:
At this point clicking on the folders with locks will open with admin privileges.
You may bookmark a folder that is opened with
admin:///prefix. When you click on such a bookmark later you may be prompted for the admin password again.
Alternatively, from the Terminal open nautilus with the argument
to open the /usr/ directory as root in Nautilus.
Editing text files with admin privileges
From Nautilus opened in this way, if you click on a text file that needs admin privileges, you will be prompted for password again, before it opens in your default editor such as Gedit.
If you are using Ubuntu 17.10
The following method does not work with Wayland by default. There are some workarounds. The easiest one is not to use Wayland. How do you switch from Wayland back to Xorg in Ubuntu 17.10? Other alternatives are described in Why don't gksu/gksudo or launching a graphical application with sudo work with Wayland?
Ubuntu will switch back to Xorg by default in 18.04 LTS and the workarounds will not be needed then.
gksuhasn't been updated since 2009 and is not recommended any more. In fact, Ubuntu no longer ships with gksu by default (though it may be installed for many of you, because some apps still depend on it) and it may even be completely removed at some point.
Nautilus adminadds PolicyKit files for both Nautilus and Gedit and it allows opening a file or folder from Nautilus as root, via PolicyKit:
Nautilus Adminin Ubuntu, open a terminal by pressing Ctrl+Alt+T and use the following command:
sudo apt-get install nautilus-admin
And to restart Nautilus use either of the following commands:
After this when you right click on a folder you will see:
If you right click on a text file editable by Gedit you will see:
Then you will be prompted for password:
Related question: "Open in terminal" not working on nautilus as root
nautilus-adminalso allows opening nautilus as root from the command line. Use the following command instead of
to open nautilus as root.
Hope this helps
FYI After installing `nautilus-admin` and running `$ nautilus -q` it generates 5 error messages in Ubuntu 16.04.3 with kernel 4.14.19, the first of which is `(nautilus:14964): GLib-GIO-CRITICAL **: g_dbus_interface_skeleton_unexport: assertion 'interface_->priv->connections != NULL' failed`
@WinEunuuchs2Unix I get the same 5 error messages. I removed `nautius-admin` and still get these errors. . So I can't verify if the errors are caused by `nautilus-admin`. On the other hand, killall anutilus kills it without any errors. finally, I get a different error in Ubuntu 17.04.
When I click `Open as Administrator` for folder, it asks password and then nothing is happen (Ubuntu 17.10 Gnome). Any way to fix this?
Not sure why but admin doesn't work. I had to run it from the terminal using sudo
@DonnyV. Sometimes I get the password prompt twice, but other than that, I had no issues with `admin:///` to open `/` as root in the address-bar. Please ask a new question linking this question and then add a comment below the new question starting with **@user68186** so that I get a notification. In the question please mention if you tried the address-bar method or the command line `nautilus admin:///` method.
When opening Nautilus with root privileges, it is best to use the command
unless your root account is unlocked, and in that case, Ubuntu discourages this.
The reason for the "gk" is because
sudo, by itself, doesn't perform the necessary actions automatically to properly run graphical applications as another user.
However for instance, if you were on a KDE system such as Kubuntu, you would want to issue the command
p.s. Do not leave your Nautilus root window open when you are not using it,then forgetting about it, as using a window you do not know is root is a bad idea.
For more information view the Ubuntu man page for
Unfortunately not works in Ubuntu 17.10: **`Failed to run nautilus as user root.`** `Unable to copy the user's Xauthorization file.`
If you find yourself opening nautilus as root often, I would recommend adding the option to the right-click menu in Unity: (it uses the same command as the top answer,
You will need to edit a
*.desktopfile in order to add the menu option, and you have two choices:
/usr/share/applications/nautilus.desktop(requires root access to edit) - The menu option will be added for all users. Note that you may need to re-edit this file, adding the option if an update to Nautilus occurrs that overwrites your changes.
~/.local/share/applications/nautilus.desktop(If you can't find it there, make a duplicate of the one found in
/usr/share/applications/, and save it to this new location) - The menu option will only be available for the specified user, and is considered "better practice". Note that if you already have it docked to your Unity bar, you will need to choose
Unlock from Launcheron your existing Nautilus icon (by default shows up as named
Files), then re-add your "custom" version. These changes should stay even if Nautilus gets an update.
Edit the text file
nautilus.desktop, adding the following block of code (you can use the existing two blocks as a template):
[Desktop Action RootWindow] Name=Open a Root Window Exec=gksu nautilus OnlyShowIn=Unity;
Next, add the new action to the list (should be at around line 18 of the text file):
Now right-clicking the text editor window in Unity brings up this handy new option:
I was trying this except for file nautilus.desktop is not exist on my Ubuntu 15.10 !
"sudo nautilus" works for me. Here are some alternatives:
Enter superuser mode with "sudo su" in the terminal (will ask for your password), then run the commands from there:
sudo su nautilus
Another alternative is to use something else for file exploration than nautilus, something that does not require graphical environment. GNU Midnight Commander -
mccomes to mind. You can install and run it like this:
sudo apt-get install mc mc
Your error messages suggest that the root "Cannot open display". The reason might be that the DISPLAY environment is not properly set up. You can check it from the terminal like this:
printenv | grep DISPLAY
You should see something like
DISPLAY=:0.0in response. If not, take care of the display environment for the root first.
No command is needed! Here is the GUI way:
Open Nautilus using one of the following ways:
In the sidebar (on the left-hand-side), click on "Other Locations".
An address field appears on the bottom of Nautilus, with the text of "Enter server address...". Enter
admin:///), and press Enter (or click on the "Connect" button).
Enter your root password when prompted.
Enjoy working as administrator (but be really careful)!
Note: The benefit of using this way over others is that you can safely switch between root and non-root. You can use Nautilus as a root user and as a non-root one (i.e. the user yourself) in two separated tabs. This way, you will be ensure that, for instance, you will not make a file in your home directory with root permissions.
Add it to bookmarks
Note: By adding administration explorer to bookmarks, sometimes Nautilus prompt you for root password when you open it.
Follow the steps in the section above. Navigate to the directory of choice if needed, e.g.
Use one of the following ways:
Use this shortcut:
From the toolbar on top, click on more button (with three dots). From the appeared drop-down menu, click on "Bookmark this location" button. The button is on the center of the first three buttons set.
From the location bar, click on "Administrator Root" or "/" (i.e. the folder you want to bookmark). From the appeared list, click on "Add to bookmarks".
To rename the bookmark you created, right click on it and choose "Rename...". Now you can enter a new name for it, e.g. "Root".
By clicking on your new bookmark, you can access files and directories as root. For me, it prompt the root password if I haven't enter it recently.
Hope it helps!
If you are running Ubuntu Live or Persistent install, sudo nautilus is ok, everything on the drive, except home, is already owned by root and is read only.
If you create, copy or modify a file or folder, inside the home folder on the persistent drive as root using sudo nautilus the permissions will be restored to owner on reboot. If you create, copy or modify a file on a different drive using sudo nautilus the permissions will revert to owner once the usb drive is shut down.
Nope, the home directory of the default user `ubuntu` is owned by that user. If one uses `sudo` for graphical applications it may still mess up the permissions (however they're restored after reboot because the changes are not persistent). -1
Are you saying it is not OK to use sudo nautilus while using a Live or Persistent install, that it can damage something or permanently mess up permissions? Can you be a little more specific? What is the worst that can happen? I have used sudo nautilus many times working with live/persistent installs since gksu was removed and have never had a problem with permissions. I have spent the last four hours playing with a 17.04 persistent flash drive and sudo nautilus and have not been able to create a problem.
I'm saying that in principle the live system is no different than a proper installation regarding the side-effects of `sudo nautilus`, however, without persistence, the effects are *easily reversed* with a reboot. You *not* encountering an undesirable side-effect is no sufficient evidence that there are none. In fact, this side-effect is a well documented behaviour that may appear under the right circumstances which *do not* depend on a regular Ubuntu installation.