From owner-freebsd-questions@FreeBSD.ORG Sun Dec 5 07:36:05 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0931D1065672 for ; Sun, 5 Dec 2010 07:36:05 +0000 (UTC) (envelope-from yxy.716@gmail.com) Received: from mail-ew0-f68.google.com (mail-ew0-f68.google.com [209.85.215.68]) by mx1.freebsd.org (Postfix) with ESMTP id 93AA88FC16 for ; Sun, 5 Dec 2010 07:36:04 +0000 (UTC) Received: by ewy3 with SMTP id 3so2910226ewy.7 for ; Sat, 04 Dec 2010 23:36:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:from:date :message-id:subject:to:content-type; bh=b22R2ne3/Mi3NX3HIbqUNMTuxTLDrZQdhZQHO6R4kU0=; b=hLGjxCZwU3eiB8Tr1kyfs9u+G8TImlwABS+9Cq2oipTOYsxWQuWvZIO4VCkVs3SVb0 PbQZWp7v7bC6awUg/lDgzo3z7SUP94L5gKJBYr2zXSbkZu4FTDgJvDUkdEs/mRnVlH48 XBfS5YALkmeBAna4VWF3CKVzxL7eclDrR/P+Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; b=Jz8THf5YjN8VlhaZg8hh0Cpi7Km6f7NWbAvWkqIlrVM9PNt84ooJ6h+4u2aRptiT57 EHwoqSb/+ex9JmFD1h+Sf2S14elOubb1z5mlrxy2CyVtDoAkO42pEQLH84b+1u4itjdf jYn7Z6K+5UcOaUzCv5F2GQvKY+1Eyl6WPeL58= Received: by 10.213.9.135 with SMTP id l7mr4435363ebl.37.1291534562400; Sat, 04 Dec 2010 23:36:02 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.25.131 with HTTP; Sat, 4 Dec 2010 23:35:42 -0800 (PST) From: xinyou yan Date: Sun, 5 Dec 2010 15:35:42 +0800 Message-ID: To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: gedit 's problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Dec 2010 07:36:05 -0000 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.)