Nautilus failed to create $HOME/.config/nautilus when it is run as root when HOME=/root

[Ｖ字龍(Vdragon)]

As title, Nautilus failed to create $HOME/.config/nautilus when it is run as root when HOME=/root

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu9.9
Uname: Linux 4.1.4-ck1-1000hz-nehalem-preemptive-bfq-uksm-iommu-simplefb i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: i386
CurrentDesktop: KDE
Date: Mon Oct 5 04:37:45 2015
GsettingsChanges:
 b'org.gnome.nautilus.list-view' b'use-tree-view' b'true'
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']"
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

nautilus (nor other gtk softwares) is not supposed to be used as superuser

[Ｖ字龍(Vdragon) (vdragon)]

@Sabastien
> nautilus (nor other gtk softwares) is not supposed to be used as superuser
* How do you manage file/directories as "superuser" without using a console?
* If Gtk-based file managers is not supposed to be used as superuser, why does XFCE Thunar has a root mode[1]?
* If (nor other gtk softwares) is not supposed to be used as superuser, why galternatives(software that manages the alternatives system), Gparted(software that manages disk partition table and file systems), Synaptic(software that manages APT package management system), Bleachbit(software that cleans up useless files including system directories),... ever exist?
* If Nautilus shouldn't be run as superuser, why does [this bug](https://bugs.launchpad.net/ubuntu-gnome/+bug/1405441 ) ever exist and even patched in upstream?

[1]http://pix.toile-libre.org/?img=1444137274.png

I'm appreciate for your triage, but this bug is in any perspective a valid bug.

[Sebastien Bacher (seb128)]

Having graphical/GTK applications started under sudo is a security issue, the fact that you know some example of program doing so doesn't make it a good idea. The right way to give access to user-restricted action would be through polkit integration (which is what update-manager, software-center, control-center gnome-disks, etc are doing) and not by having the UI being under privileges as well.

In any case feel free to report that bug to GNOME since they are the ones writting nautilus, Ubuntu is not likely going to look at issues from non recommended usecases