nautilus exits when opened using sudo user and properties of a file/folder is opened

[Cassio]

I have a similar problem, when I type the command sudo nautilus happens the error below.

Nautilus opens, closes however if I want to get into any folder properties.

$ sudo nautilus

(nautilus:7610): Nautilus-Python-WARNING **: g_module_open libpython failed: /usr/lib/libpython2.7.so.1.0: Não é possivel abrir arquivo de objetos compartilhado: Arquivo ou diretório não encontrado
ImportError: could not import gobject (error was: '/usr/lib/x86_64-linux-gnu/libpyglib-gi-2.0-python2.7.so.0: undefined symbol: _Py_ZeroStruct')

(nautilus:7610): Nautilus-Python-WARNING **: pygobject initialization failed

(nautilus:7610): Nautilus-Python-WARNING **: nautilus_python_init_python failed

I want to change the permissions of a folder and subfolders and files, however the terminal does not present any error but too does not change the permissions. And to change opening the Nautilus happens that I reported above.

My system is Ubuntu 13.04 updated
My computer is Notebook HP AMD A8 64 bits

-----------------------------------------------------------------------------------------

Confirmed that this bug exists on 14.04 release with nautilus version 3.10.1 but the error message is as follows:

(nautilus:13221): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
**
ERROR:nautilus-properties-window.c:1839:schedule_owner_change_timeout: assertion failed: (NAUTILUS_IS_FILE (file))

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[C de-Avillez (hggdh2)]

This is the current BT:

#0 0x00007fe771aaaf79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007fe771aae388 in __GI_abort () at abort.c:89
#2 0x00007fe7725e6175 in g_assertion_message (domain=domain@entry=0x0, file=file@entry=0x4f5010 "nautilus-properties-window.c", line=line@entry=1839,
    func=func@entry=0x4f5e60 <__FUNCTION__.52098> "schedule_owner_change_timeout", message=message@entry=0x2350540 "assertion failed: (NAUTILUS_IS_FILE (file))")
    at /build/buildd/glib2.0-2.39.92/./glib/gtestutils.c:2291
#3 0x00007fe7725e620a in g_assertion_message_expr (domain=domain@entry=0x0, file=file@entry=0x4f5010 "nautilus-properties-window.c", line=line@entry=1839,
    func=func@entry=0x4f5e60 <__FUNCTION__.52098> "schedule_owner_change_timeout", expr=expr@entry=0x4ef2ca "NAUTILUS_IS_FILE (file)")
    at /build/buildd/glib2.0-2.39.92/./glib/gtestutils.c:2306
#4 0x000000000045959e in schedule_owner_change_timeout (window=0x23c5080, window@entry=<error reading variable: value has been optimized out>)
    at nautilus-properties-window.c:1839
#5 0x00007fe7725c2703 in g_timeout_dispatch (source=0x23cf450, callback=<optimized out>, user_data=<optimized out>) at /build/buildd/glib2.0-2.39.92/./glib/gmain.c:4472
#6 0x00007fe7725c1ce5 in g_main_dispatch (context=0x1db1490) at /build/buildd/glib2.0-2.39.92/./glib/gmain.c:3064
#7 g_main_context_dispatch (context=context@entry=0x1db1490) at /build/buildd/glib2.0-2.39.92/./glib/gmain.c:3663
#8 0x00007fe7725c2048 in g_main_context_iterate (context=context@entry=0x1db1490, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>)
    at /build/buildd/glib2.0-2.39.92/./glib/gmain.c:3734
#9 0x00007fe7725c20ec in g_main_context_iteration (context=0x1db1490, context@entry=0x0, may_block=may_block@entry=1) at /build/buildd/glib2.0-2.39.92/./glib/gmain.c:3795
#10 0x00007fe772b7467c in g_application_run (application=0x1d89140, argc=argc@entry=1, argv=argv@entry=0x7fff1bc51828)
    at /build/buildd/glib2.0-2.39.92/./gio/gapplication.c:2114
#11 0x000000000042b561 in main (argc=1, argv=0x7fff1bc51828) at nautilus-main.c:104

[C de-Avillez (hggdh2)]

er. I forgot to add more data:

* 14.04, nautilus 1:3.10.1-0ubuntu8.
* executed via 'sudo nautilus', and 'gksudo nautilus'.

[Sebastien Bacher (seb128)]

running graphical softwares under sudo is neither recommended nor supported, don't do that

[C de-Avillez (hggdh2)]

and under gksudo? I thought it should have worked, then.

[Sebastien Bacher (seb128)]

no, it's neither secure to run that much code (including GUI) under sudo right nor working right with the user session (the process run with another uid and with the wrong environment which means basic integration with the session components is going to fail working since there is not even a session for the user running the binary)