Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 5 Dec 2010 15:35:42 +0800
From:      xinyou yan <yxy.716@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   gedit 's problem
Message-ID:  <AANLkTimc3djaYLxq-JsyKDB4At3nxY2PN8_78Q39LEF_@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
hello

     freebsd 8.1  afer i su to root

     after i  beat  gedit

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

(gedit:75122): Gtk-CRITICAL **: gtk_widget_is_ancestor: assertion
`ancestor != NULL' failed

(gedit:75122): Gtk-CRITICAL **: gtk_widget_is_ancestor: assertion
`ancestor != NULL' failed

(gedit:75122): Gtk-CRITICAL **: gtk_widget_is_ancestor: assertion
`ancestor != NULL' failed

(gedit:75122): Gtk-CRITICAL **: gtk_widget_is_ancestor: assertion
`ancestor != NULL' failed


          when i back to normal user

 it shows


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.)
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.7

Fontconfig error: "local.conf", line 2: XML or text declaration not at
start of entity
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.)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimc3djaYLxq-JsyKDB4At3nxY2PN8_78Q39LEF_>