F11: As root-user, gedit blows up from the command line?

[Daniel B. Thurman]

# gedit

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

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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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.)