Author Topic: gconftool-2 fail to connect to server. Zen mini  (Read 692 times)

Offline MBantz

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 1317
gconftool-2 fail to connect to server. Zen mini
« on: June 28, 2010, 09:45:12 AM »
Haven't used gconftool-2 before - but need to import a nautilus action - and have been told that:

gconftool-2 --load action-01689b9f-07cc-4496-90aa-605c416c212a.xml

will import a Nautilus action (created with Nautilus).

As root (because I need systemwide change), I get a bunch of errors on problems on contacting configuration server. No errors when attempt as ordinary user.

This is Zen mini, fully updated.

Any ideas?




Code: [Select]
Error setting value: 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.)
Error setting value: 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.)
Error setting value: 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.)

EDIT: Corrected details
« Last Edit: June 28, 2010, 10:00:21 AM by MBantz »