unable to start as root

[e-letter <inpost gmail com>]

Readers,

Received the following command terminal response trying to start
nautilus as root:

nautilus

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


(nautilus:7473): 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:7473): 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:7473): 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:7473): 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 `/desktop/gnome/lockdown': 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.)GConf warning:
failure listing pairs in `/apps/nautilus/desktop-metadata': 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:7473): 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:7473): Unique-DBus-WARNING **: Unable to connect to the
running instance, aborting.

(nautilus:7473): 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:7473): Unique-DBus-WARNING **: Unable to connect to the
running instance, aborting.
[root@localhost tmp]#

Is this a bug? Using mandriva20102.