After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 575661 - GConf Error
GConf Error
Status: RESOLVED DUPLICATE of bug 555745
Product: gconf-editor
Classification: Applications
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-17 10:45 UTC by KYROS
Modified: 2009-03-24 13:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description KYROS 2009-03-17 10:45:31 UTC
Please describe the problem:
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 

Steps to reproduce:
1. If I login with root.
2. using gedit at GNOME Terminal
3. 


Actual results:
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 

Expected results:
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 

Does this happen every time?
yes

Other information:
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
Comment 1 Christian Persch 2009-03-17 12:19:41 UTC
It's a known problem with gconf demon now using dbus. See e.g. bug 555745 and
https://bugs.freedesktop.org/show_bug.cgi?id=17970 .
Comment 2 Christian Persch 2009-03-24 13:04:57 UTC

*** This bug has been marked as a duplicate of 555745 ***