Can't navigate in nautilus as root

Hi. I’m trying to enter as root to /usr/local/bin but I get this error:

psyfurius@linux-jdsx:~> su
Password: ***
linux-jdsx:/home/psyfurius # nautilus

(nautilus:7641): Eel-WARNING **: Error of GConf: it Failed when
contacting with the servidor of configurations; some of the possible
causes are that it need to enable TCP/IP in ORBit, or that has blockades
of NFS of a fall of system. It see
http://www.gnome.org/projects/gconf/(Details - 1: it Failed when
obtaining the connection with the 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.)


Psyfurius

Psyfurius’s Profile: http://forums.opensuse.org/member.php?userid=20340
View this thread: http://forums.opensuse.org/showthread.php?t=405663

‘Eel-WARNING - Google Search’ (http://tinyurl.com/8rzrx8)


Box: Linux 2.6.27.7-9 i686 | OS 11.1 | (KDE4.1.96) "78.1"rc1 | M2N4-SLI
| AMD 64 X2 5200+ | nVidia 8500GT | 2GB RAM
Lap: OS 11.1 | Celeron 550 | (KDE4.1.96)"78.1"rc1 | Intel 965 GM |
Lenovo R61e | 3GB RAM

caf4926’s Profile: http://forums.opensuse.org/member.php?userid=204
View this thread: http://forums.opensuse.org/showthread.php?t=405663

Hi
If you use su - or xdg-su you will get the warnings but it won’t die on
you…


Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.1 x86 Kernel 2.6.27.7-9-default
up 3 days 15:58, 2 users, load average: 0.24, 0.25, 0.18
GPU GeForce 6600 TE/6200 TE - Driver Version: 180.22

I have read some of the posts but I am not convinced this is my
problem.

When I try to go to the console and open nautilus as root (su etc) I
get an error message and although nautilus opens, I can’t change any of
the files.

I have to log in as root to do this. That is a pain. I even did a fresh
install and I still have the problem.

Iam running 1md 3700+ with 128 mb nvidia gf4 card, 2gb memory. This is
opensuse 11.1 64-bit

here is the error:

(nautilus:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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:25921): 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 ‘GConf configuration system’
(http://www.gnome.org/projects/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.)


allstar1960

allstar1960’s Profile: http://forums.opensuse.org/member.php?userid=6132
View this thread: http://forums.opensuse.org/showthread.php?t=405663

Try Alt+F2 then enter gnomesu nautilus

/Geoff


Core 2 Duo 3.16GHz, 4GB DDR2, 2.5TB, GeForce 7600 GS, OS 11.1
x86_64, KDE4.2 (82.3) ‘Smolt specs’ (http://tinyurl.com/9hgxhl)

geoffro’s Profile: http://forums.opensuse.org/member.php?userid=75
View this thread: http://forums.opensuse.org/showthread.php?t=405663