i can't launch nautilus as root

jfca283 · 2009-06-17 15:02:12

i get a loot of error concernings to gconf and dbus
i've tested from gksu, root nautilus and more
but always it crashes
any help?

dmartins · 2009-06-17 16:56:23

Try using gksudo instead of gksu. You need sudo set up and working before gksudo will work. There seems to be some kind of issue with nautilus and su.

http://bbs.archlinux.org/viewtopic.php?id=73208

jfca283 · 2009-06-17 20:11:06

i don't understand what the post suggest
sorry...

plurt · 2009-06-17 20:18:47

maybe you could post the error you get when trying to start nautilus as root in a terminal?

jfca283 · 2009-06-17 22:18:23

[root@juan DD]# nautilus 

(nautilus:15143): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported


(nautilus:15143): Eel-WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

(nautilus:15143): Eel-WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)

(nautilus:15143): Eel-WARNING **: GConf error:
  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
GConf warning: failure listing pairs in `/apps/nautilus/preferences': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/file_views': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/desktop/gnome/background': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/desktop': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)GConf warning: failure listing pairs in `/apps/nautilus/icon_view': Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.)
(nautilus:15143): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:15143): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

(nautilus:15143): Unique-DBus-WARNING **: Unable to open a connection to the session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

(nautilus:15143): Unique-DBus-WARNING **: Unable to connect to the running instance, aborting.

Arisna · 2009-06-18 02:19:28

What dmartins was saying was to run the command "gksudo nautilus" as a normal user. You'll get a graphical popup asking for your root password. Also, I think you might want "gksudo nautilus --nodesktop" instead.

jfca283 · 2009-06-18 02:42:58

[juan@juan DD]$ gksudo nautilus

(gksudo:18531): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:18531): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:18531): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

(gksudo:18531): Gdk-CRITICAL **: gdk_x11_atom_to_xatom_for_display: assertion `atom != GDK_NONE' failed

i got this...

mandog · 2009-06-18 07:12:11

dmartins wrote:

Try using gksudo instead of gksu. You need sudo set up and working before gksudo will work. There seems to be some kind of issue with nautilus and su.
http://bbs.archlinux.org/viewtopic.php?id=73208

yes it always works for me

graysky · 2009-12-20 10:32:27

Sorry to resurrect an old thread but the op never marked this as solved . The solution for me is to:

gksu nautilus

Using gksudo failed to work, continuously asking for the correct root password.

Arch Linux

#1 2009-06-17 15:02:12

i can't launch nautilus as root

#2 2009-06-17 16:56:23

Re: i can't launch nautilus as root

#3 2009-06-17 20:11:06

Re: i can't launch nautilus as root

#4 2009-06-17 20:18:47

Re: i can't launch nautilus as root

#5 2009-06-17 22:18:23

Re: i can't launch nautilus as root

#6 2009-06-18 02:19:28

Re: i can't launch nautilus as root

#7 2009-06-18 02:42:58

Re: i can't launch nautilus as root

#8 2009-06-18 07:12:11

Re: i can't launch nautilus as root

#9 2009-12-20 10:32:27

Re: i can't launch nautilus as root

Board footer