Home > Failed To > Gconf Error Failed To Contact Configuration Server Ssh

Gconf Error Failed To Contact Configuration Server Ssh

Contents

I am, however, able to use virt-viewer, and the problem with running virt-manager is now a solid failure. You don't want to be running GUI apps as anything but the logged-in user, in general. Affecting: dbus (Ubuntu) Filed here by: Adam Petaccia When: 2009-10-27 Completed: 2011-10-15 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu I was advised to change the permissions for ~/.dbus but this does not work.3. http://blogeurope.net/failed-to/gconf-error-failed-to-contact-configuration-server-opensuse.php

up vote 5 down vote favorite 2 Logging into a remote host using ssh -X [email protected], I successfully run gnome-terminal -e "tail -F /var/log/file" &. Registration is quick, simple and absolutely free. export DBUS_SESSION_BUS_ADDRESS="" share|improve this answer answered Nov 3 '09 at 15:27 Kevin Wright 1,2131119 6 don't work. Peacedog View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Visit Peacedog's homepage!

Gconf Error Failed To Contact Configuration Server Centos

If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Reported by: Vincent Lefevre Date: Mon, 24 May 2010 01:15:02 UTC Severity: normal Found in version gconf/2.28.1-3 Fixed in versions gconf/2.31.4-1, gconf/2.28.1-4 Done: Josselin Mouette Bug is archived. 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.)" when I We Acted.

Hardware: Dell Poweredge 1950, 2 x XEON 5160 Install: CentOS 6.3 via 'CentOS-6.3-x86_64-bin-DVD1.iso' Select 'Virtual Host' during the Install-Package Group Selection. I do have a 389-ds server running on a virtual client, and I can forward X from it. At the terminal prompt issue the following command #find / -iname "gconfd" if you get more that one gconf for your system, remove one of them. Enable Tcp/ip Networking For Orbit Redhat ALIENDUDE5300May 25th, 2009, 09:08 PMOk, this just started today after trying to install an apache server on my Ubuntu desktop as a sort of "sandbox" for me to play around with

We Acted. Electo9 View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Electo9 01-23-2012, 04:58 AM #9 bhavisavla LQ Newbie Registered: Aug 2011 Posts: also hopefully i didn't hurt anything by changing the ownership to me. Get More Info I simply deleted all the files in ~/.dbus/session-bus, and now it works fine.

I had not seen the thing about .esd_auth reported so I just wanted to let you know. Failed To Get Connection To Session: Failed To Connect To Socket Click Here to receive this Complete Guide absolutely free. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Did not receive a reply. Acknowledgement sent to Vincent Lefevre : Extra info received and forwarded to list.

Gconf Error Failed To Contact Configuration Server Redhat

If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate. Toggle useless messagesView this report as an mbox folder, status mbox, maintainer mbox Report forwarded to [email protected], Josselin Mouette : Bug#582839; Package gconf2. (Mon, 24 May 2010 01:15:04 GMT) Full text Gconf Error Failed To Contact Configuration Server Centos Why is absolute zero unattainable? Gedit Gconf Error Failed To Contact Configuration Server libvertd working correct (also able to start the guest-OS via virsh), only the virt-manager (and also virt-viewer) don't work.

I fixed this, but I'm not quite sure how... news These were the errors I was seeing on the command line: yast2 ** (y2controlcenter-gnome:9981): WARNING **: error accessing /desktop/gnome/lockdown/disable_command_line [Failed to contact configuration server; some possible causes are that you need safe to ignore ? Well, DBus is used as a communication-protocol for programs on the system (from low-level to high-level). Stale Nfs Locks Due To A System Crash

Below is what I did: [email protected]:~$ 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 Browse other questions tagged ssh gnome d-bus or ask your own question. What session? have a peek at these guys Changed in gconf (Ubuntu): status: Invalid → New Mikhail Veygman (mveygman) wrote on 2009-11-12: #18 A little further investigation revealed the following.

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. Failed To Connect To Socket /tmp/dbus Connection Refused Joe McPherson (alicesresturantm) wrote on 2009-07-13: #12 There are three cause the gconfd not making connection. 1. Martje_001April 27th, 2010, 06:17 PMHmm...

You are currently viewing LQ as a guest.

abchirk View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by abchirk 06-18-2010, 05:17 PM #7 smj2118 LQ Newbie Registered: Jun 2010 Posts: Search this Thread 06-14-2004, 09:56 PM #1 qwijibow LQ Guru Registered: Apr 2003 Location: nottingham england Distribution: Gentoo Posts: 2,672 Rep: GConf Error: Failed to contact configuration server when I simply deleted all the files in ~/.dbus/session-bus, and now it works fine. Details - 1: Not Running Within Active Session Notification sent to Vincent Lefevre : Bug acknowledged by developer. (Sat, 18 Sep 2010 13:36:03 GMT) Full text and rfc822 format available.

Mark as duplicate Convert to a question Link a related branch Link to CVE You are not directly subscribed to this bug's notifications. Message #35 received at [email protected] (full text, mbox, reply): From: Josselin Mouette To: Vincent Lefevre , [email protected] Cc: [email protected] Subject: Re: Bug#582839: gconf2: many GConf errors when applications are started If this is not a bug with gconf, how would I determine what package is setting these permissions and therefore has the bug? check my blog Can anyone explain how that worked?

See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-FQHSOkYllt: Connection refused)GConf warning: failure listing pairs in `/desktop/gnome/background': Failed to contact configuration Our configuration used xCAT, GPFS, NFS. Guest-OS shutdown, Host-OS (CentOS 6.3) reboot, and after the reboot of the Host-OS the descripted error occurred. Notification sent to Vincent Lefevre : Bug acknowledged by developer. (Sat, 19 Jun 2010 07:39:03 GMT) Full text and rfc822 format available.

M. s.foxMay 25th, 2009, 09:16 PMHi, This (http://www.linuxhelp.net/forums/lofiversion/index.php/t8237.html) person on a different forum experienced same error as you. Cheers gord-s (gord-sssnaps) wrote on 2010-10-03: #25 This occurs for me on 10.04.1, several server machines and a couple of Ubuntu desktops, acting as remote (ssh-into these machines) and local (ssh IMHO, any method based on the environment (except DISPLAY, > > which doesn't change in general) is broken because the environment > > isn't something global. > > Huh?

This is on Debian stable. True or False? Register If you are a new customer, register now for access to product evaluations and purchasing capabilities. You can find out more about the development release at http://www.ubuntu.com/testing/ .

By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Current Customers and Partners Log in for full access Log In New to Red Hat? And you never want to be running any GUI app as root, ever. share|improve this answer answered Mar 21 '14 at 0:44 hourback 188119 Incredibly enough, it worked also in 16.04.

blackest_knight (blackest-knight) wrote on 2009-05-03: #4 Thanks very much for reporting this all the files were owned by root and changing them to my user name solved the problem. I found this when comparing known working servers with servers showing this error. I just can't do it from this server. It I tried all of the suggestions listed here: made sure ~/.dbus had proper ownership, service messagbus restart, etc.