You are not logged in.

#1 2009-01-20 22:27:43

speng
Member
Registered: 2009-01-17
Posts: 136

gconf - Failure to contact configuration server

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

This happens when trying to add a printer within gnome-cups-add as root using the gnome-cups-manager, also crops up in some other programs.

So I discovered this error when I couldn't print a test page, I later found out that I could print using more or less ANY program, but  it would simply not work in Gnome.
This program might NOT be simply a gnome setting error as I also cannot print a test page from localhost:631! Same thing, pstoraster fails.
One thing I'm also wondering is if localhost:631 (cups) uses any gnome settings?

What I am trying to fix is the error shown above (ORBit), is there something I have done wrong or configured wrong that is causing this?

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_GB.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/London"
KEYMAP="uk"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(ndiswrapper forcedeth snd-mixer-oss snd-pcm-oss 
snd-seq-oss 
snd-seq-device snd-seq-midi-event snd-seq snd-hwdep snd-page-alloc snd-pcm snd-rawmidi snd-timer snd snd-hda-intel soundcore snd-usb-audio snd-usb-lib)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="spengpc"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
wlan0="dhcp"
wlan_wlan0="wlan0 essid linksys key xxxxxxxxxxxxxxxxxxxxx"
INTERFACES=(wlan0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond hal cups @alsa fam)

Is there any other info I should include? I really want to sort this out. smile

Thanks!

Offline

#2 2009-01-21 18:46:15

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bump, can't seem to find a solution!

I hate Google. :x

Offline

#3 2009-01-24 12:01:38

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bumpizzle. smile

Offline

#4 2009-01-25 14:47:56

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

neutral

Offline

#5 2009-01-26 18:14:52

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bump. neutral

Offline

#6 2009-01-27 17:42:38

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bump, still haven't solved this problem.

Offline

#7 2009-01-28 18:05:35

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bump, still haven't figured this one out. Sorry about all the bumps.

Offline

#8 2009-01-29 17:38:23

speng
Member
Registered: 2009-01-17
Posts: 136

Re: gconf - Failure to contact configuration server

Bump. neutral

Offline

#9 2009-01-29 20:09:26

kidawesome
Member
From: Toronto
Registered: 2008-10-04
Posts: 13

Re: gconf - Failure to contact configuration server

I had a similar problem trying to use gconf-editor (exactly the same error message)

I think i just built gconf and gconf-editor from ABS and it fixed it... worth a shot atleast

Offline

#10 2011-08-05 19:37:59

linuxvic
Member
Registered: 2011-08-05
Posts: 1

Re: gconf - Failure to contact configuration server

See this link,

http://www.rootninja.com/fix-gconf-exce … us-launch/

The following command got my virt-manager to run!

dbus-launch --exit-with-session virt-manager

Offline

Board footer

Powered by FluxBB