gconf error please help
sachin <[email protected]> Thu, 04 Dec 2008 11:57:25 +0530
| Newsgroups | gmane.comp.gnome.lib.gconf |
|---|---|
| Organization | Crompton Greaves Ltd. |
| Message-ID | <1228372045.13083.67.camel@sachin-desktop> |
--===============0400413938==
Content-Type: multipart/alternative; boundary="=-hwFiLjtJrxjXdsP5TR29"
--=-hwFiLjtJrxjXdsP5TR29
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Exact error messages from any applications.
When I give a command 'gedit' from command prompt I get an error as
follows
*************************************************************************************
root@sachin-desktop:/home/sachin/Desktop/oof2-2.0.5a5# gedit README
(gedit:6907): 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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 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://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.)
**************************************************************************************************************************************
Exact version of GConf 1 and GConf 2 that you have installed.
Installed Version: 2.24.0-0ubuntu1
Output of ps jaxwww | grep gconf.
6515 6518 6515 6515 ? -1 S 1000
0:00 /usr/lib/pulseaudio/pulse/gconf-helper
1 6520 6512 6512 ? -1 S 1000
0:01 /usr/lib/libgconf2-4/gconfd-2
6795 13409 13408 6757 pts/0 13408 D+ 0 0:00 grep gconf
Output of gconf-sanity-check-1 or gconf-sanity-check-2 if any.
this command does not run
root@sachin-desktop:/usr/lib/libgconf2-4# gconf-sanity-check-1
bash: gconf-sanity-check-1: command not found
root@sachin-desktop:/usr/lib/libgconf2-4# ./gconf-sanity-check-1
bash: ./gconf-sanity-check-1: No such file or directory
root@sachin-desktop:/usr/lib/libgconf2-4#
What operating system are you using, and what version of it.
Ubuntu-8.10 Intripid Ibex
What appears in the user.* syslog (see above for how to turn on cc)
Not enabled
when tried with the procedure explained above for syslog it gave
following error
root@sachin-desktop:/etc# service syslog restart
$syslog: unrecognized service
************************************ D I S C L A I M E R ***********************************************
The information contained in this electronic message / attachments may contain confidential or privileged information. If you are not the intended recipient, then any dissemination, use, review, distribution, printing or copying of the information contained in this electronic message or attachments is strictly prohibited. If you have received this communication in error, please notify to us by reply on electronic message or telephone and immediately / permanently delete the message / attachments.
WARNING: Computer viruses can be transmitted via electronic message. The recipient should check this electronic message / attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this electronic message.
***********************************************************************************************************
--=-hwFiLjtJrxjXdsP5TR29
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: 7bit
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
<B>Exact error messages from any applications.</B><BR>
<BR>
When I give a command 'gedit' from command prompt I get an error as follows<BR>
<BR>
*************************************************************************************<BR>
root@sachin-desktop:/home/sachin/Desktop/oof2-2.0.5a5# gedit README<BR>
<BR>
(gedit:6907): EggSMClient-WARNING **: Failed to connect to the session manager: None of the authentication protocols specified are supported<BR>
<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
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 <A HREF="http://www.gnome.org/projects/gconf/">http://</A><A HREF="http://www.gnome.org/projects/gconf/">www.gnome.</A><A HREF="http://www.gnome.org/projects/gconf/">org/projects/</A><A HREF="http://www.gnome.org/projects/gconf/">gconf/</A> 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.)<BR>
**************************************************************************************************************************************<BR>
<BR>
<B>Exact version of GConf 1 and GConf 2 that you have installed.</B><BR>
<BR>
Installed Version: 2.24.0-0ubuntu1<BR>
<BR>
<B>Output of </B><B><TT>ps jaxwww | grep gconf</TT></B><B>.</B><BR>
6515 6518 6515 6515 ? -1 S 1000 0:00 /usr/lib/pulseaudio/pulse/gconf-helper<BR>
1 6520 6512 6512 ? -1 S 1000 0:01 /usr/lib/libgconf2-4/gconfd-2<BR>
6795 13409 13408 6757 pts/0 13408 D+ 0 0:00 grep gconf<BR>
<BR>
<B>Output of </B><B><TT>gconf-sanity-check-1</TT></B><B> or </B><B><TT>gconf-sanity-check-2</TT></B><B> if any.</B><BR>
<BR>
this command does not run<BR>
<BR>
root@sachin-desktop:/usr/lib/libgconf2-4# gconf-sanity-check-1<BR>
bash: gconf-sanity-check-1: command not found<BR>
root@sachin-desktop:/usr/lib/libgconf2-4# ./gconf-sanity-check-1<BR>
bash: ./gconf-sanity-check-1: No such file or directory<BR>
root@sachin-desktop:/usr/lib/libgconf2-4# <BR>
<BR>
<B>What operating system are you using, and what version of it.</B><BR>
Ubuntu-8.10 Intripid Ibex<BR>
<BR>
<B>What appears in the </B><B><TT>user.*</TT></B><B> syslog (see above for how to turn on cc)</B><BR>
<BR>
Not enabled<BR>
when tried with the procedure explained above for syslog it gave following error<BR>
<BR>
root@sachin-desktop:/etc# service syslog restart<BR>
$syslog: unrecognized service<BR>
<BR>
<BR>
<BR>
<br>************************************ D I S C L A I M E R ***********************************************<br>
<br>
The information contained in this electronic message / attachments may contain confidential or privileged information. If you are not the intended recipient, then any dissemination, use, review, distribution, printing or copying of the information contained in this electronic message or attachments is strictly prohibited. If you have received this communication in error, please notify to us by reply on electronic message or telephone and immediately / permanently delete the message / attachments. <br>
<br>
WARNING: Computer viruses can be transmitted via electronic message. The recipient should check this electronic message / attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this electronic message.<br>
<br>
***********************************************************************************************************<br>
</BODY>
</HTML>
--=-hwFiLjtJrxjXdsP5TR29--
--===============0400413938==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
gconf-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/gconf-list
--===============0400413938==--