Gconf Error Failed To Contact Configuration Server Fedora
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about
Gedit Gconf Error Failed To Contact Configuration Server
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask stale nfs locks due to a system crash Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other.
Failed To Get Connection To Session: Failed To Connect To Socket
Join them; it only takes a minute: Sign up linux gedit: I always get “GConf Error: failed to contact configuration server …” up vote 9 down vote favorite 2 How come I always get "GConf Error: Failed to contact details - 1: not running within active session 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.)" when I start 'gedit' from a meld glib gerror failed to contact configuration server shell from my superuser account? linux gedit share|improve this question asked Sep 14 '09 at 13:17 jldupont 41.7k32140258 (and yes, that's normal, I don't remember what's the culprit, but it's one of the environment variables that prevents contact with configuration server. most likely HOME). –Michael Krelin - hacker Sep 14 '09 at 13:22 1 I think that this belongs to Super User or Server Fault. –Cristian Ciupitu Sep 14 '09 at 13:26 Sorry guys... I'll move to Super User. –jldupont Sep 14 '09 at 13:42 add a comment| 5 Answers 5 active oldest votes up vote 4 down vote accepted The technical answer is that gedit is a Gtk+/Gnome program, and expects to find a current gconf session for its configuration. But running it as a separate user who isn't logged in on the desktop, you don't find it. So it spits out a warning, telling you. The failure should be benign though, and the editor will still run. The real answer is: don't do that. You don't want to be running GUI apps as anything but the logged-in user, in general. And you never want to be running any GUI app as root, ever. share|improve this answer answered Sep 14 '09 at 17:10 Andy Ross 8,5651723 Most helpful... thanks! –jldupont Sep 14 '09 at 17:47 What's your argument for these prescriptions? –David
#1 2009-09-21 13:33:12 ajassat Member Registered: 2009-09-08 Posts: 9 Gconf error: "Failed to contact configuration server" on firefox start 1. The problem If I try
Could Not Send Message To Gconf Daemon
and load 32 bit applications which require gconf (such as firefox ssconvert gconf error failed to contact configuration server and totem) I recieve the following error:GConf Error: Failed to contact configuration server; some possible causes are
Failed To Connect To Socket Tmp Dbus Connection Refused
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: http://stackoverflow.com/questions/1421498/linux-gedit-i-always-get-gconf-error-failed-to-contact-configuration-server Failed to get connection to session: [b]Failed to connect to socket /tmp/dbus-KnKGBcSHAp: Connection refused[/b])The last line of the error suggests it is something to do with dbus too. I can tell you that the plug was pulled from my pc hence the problem is most likely to be a stale nfs lock. 2. Attempt at a https://bbs.archlinux.org/viewtopic.php?id=80644 solution I am new to ArchLinux and have searched how to resolve the stale nfs lock but find no clear instructions on how to do this. I was advised to change the permissions for ~/.dbus but this does not work.3. Other details Running 'sudo firefox' starts firefox fine.I have no .gconf directory in /home ! Offline #2 2009-09-23 04:03:40 grapescan Member From: Russia / Samara Registered: 2009-09-23 Posts: 2 Re: Gconf error: "Failed to contact configuration server" on firefox start I fully support this problem. Have anybody got a solution? Offline #3 2009-09-24 13:12:04 grey Member From: Europe Registered: 2007-08-23 Posts: 679 Re: Gconf error: "Failed to contact configuration server" on firefox start I'm not entirely sure, but here is what I would do:1. Create a new user account and try to start firefox as that user.2. are hal / dbus running (check with ps -ef |grep hal)3. If 1. works and hal/dbus are running, log out and remove everything under /tmp owned by you ,
Ubuntu Linux Install Package Manager Services X Server Other Linux Multimedia Shell Scripts Dialup Internet Disk Drives Email Password Web Server Help Software Sound Security Encryption Software Forensics Risk Information Mobile Programming http://www.askmeaboutlinux.com/?p=1386 Glade MySQL GTK+ Java Perl PHP Information Computer BIOS Hardware Internet Broadband Web Browser Windows VirtualBox Android « Concatenate multiple MP4 files using MP4Box in Linux Print Options for Transaction Statement https://lists.fedoraproject.org/pipermail/users/2010-May/371925.html in Gnucash » Overcoming GConf error: Failed to contact configuration server By Geetu R. Vaswani, on June 3rd, 2011 If you get the following error: Failed to contact configuration server; some possible causes failed to 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: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0) you can try resolving it by doing: $ mv .gconfd .gconfdtemp
[ subject ] [ author ] Hi guys, I have huge problem with virt-manager as it displays errors below [1]. Problem happened after I upgraded in quick succession from F10 to F11 and then to F12. If I do yum update, it says "No Packages marked for Update" - so I'm pretty sure my system is up-to-date F12. My libvirt is running: root 8030 1 0 10:34 ? 00:00:00 libvirtd --daemon However my polkit agent is not running [2]. (not sure if it is a must) I have two virutal machines defined under qemu-kvm and one is running fine and one is not. Without virt-manager I'm unable to investigate the problem. Is there any other way how can I get inside my running virtual machine (ssh does not work)? I'm also not sure if my problem is related to this bug or not, but I also have exactly the same problem as described in this bug https://bugzilla.redhat.com/show_bug.cgi?id=581387 And in final here are the packages I use: Package python-virtinst-0.500.1-2.fc12.noarch already installed and latest version Package 2:qemu-kvm-0.11.0-13.fc12.x86_64 already installed and latest version Package virt-manager-0.8.2-3.fc12.noarch already installed and latest version Package virt-viewer-0.2.0-1.fc12.x86_64 already installed and latest version Package libvirt-0.7.1-15.fc12.x86_64 already installed and latest version Any help is appreciated, I have web-server running inside non functional virt-machine and it is down now :( Thank you in advance, Jaiv [1] Unable to open connection to hypervisor URI 'qemu:///system': authentication failed Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 872, in _try_open None], flags) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 102, in openAuth if ret is None:raise libvirtError('virConnectOpenAuth() failed') libvirtError: authentication failed Error starting Virtual Machine Manager: 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.) Traceback (most recent call last): File "/usr/share/virt-manager/virt-manager.py", line 404, in