Gconf Error Failed To Contact Configuration Server Ubuntu
Contents |
people Affects Status Importance Assigned to Milestone dbus (Ubuntu) Edit Expired Low Unassigned Edit You need to log in to change this bug's status. Affecting: dbus (Ubuntu) Filed here gconf error failed to contact configuration server centos by: Adam Petaccia When: 2009-10-27 Completed: 2011-10-15 Target Distribution Baltix BOSS Juju Charms
Gconf Error Failed To Contact Configuration Server Redhat
Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM
Gedit Gconf Error Failed To Contact Configuration Server
Package (Find…) Project (Find…) Status Importance Expired Low Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Nominated for Karmic by muenalan Nominated for Lucid
Stale Nfs Locks Due To A System Crash
by muenalan gconf (Ubuntu) Edit Expired Low Unassigned Edit You need to log in to change this bug's status. Affecting: gconf (Ubuntu) Filed here by: Keith Buel When: 2009-04-26 Completed: 2011-10-15 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Expired Low enable tcp/ip networking for orbit redhat Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Nominated for Karmic by muenalan Nominated for Lucid by muenalan Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: gconf I am connecting from a Jaunty computer to another computer running Jaunty, using ssh X11 forwarding. When I try to open any application such as gedit, I get the following error over and over again: 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://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-QS6NzEDBEh: Connection refused) The application does not open. Client machine: lsb_release -rd Description: Ubuntu 9.04 Release: 9.04 Server: lsb_release -rd Description: Ubuntu 9.04 Release: 9.04 Add tags Tag help Pedro Villavicencio (pedro) wrote on 2009-04-27: #1 Thank you for taking the time to report this bug and helping to make Ubuntu better. Also, please answer these questions: * Is this reproducible? * If so, what specifi
people Affects Status Importance Assigned to Milestone gconf (Ubuntu) Edit Invalid Low Ubuntu Desktop Bugs Edit You need to log in to change this bug's status. Affecting: gconf (Ubuntu) Filed here by: Vadim Nevorotin When: 2009-03-02 Assigned: 2009-03-02 Completed: 2009-03-02 failed to get connection to session: failed to connect to socket Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD details - 1: not running within active session Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Invalid Low Assigned to Me Ubuntu Desktop failed to connect to socket /tmp/dbus connection refused Bugs (desktop-bugs) Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description Binary package hint: gconf Since Ubuntu 8.10 (I've tried it in https://bugs.launchpad.net/bugs/367169 8.10 and 9.04 alpha5) there is a very strange bug. If you set a root password (e.g. with command sudo passwd root) and then log in to root in a terminal using command su a lot of GNOME applications start from this root session with an error like this: 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 https://bugs.launchpad.net/bugs/336660 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.) For example, gedit and firefox. But if you log in into root session with command sudo su everything works perfectly. To be honest, I can't understand difference between su and sudo su. Yes, I extremely well know, that using sudo instead of root account is safer and preferable BUT sometimes it's better and easier to use root account. Add tags Tag help Sebastien Bacher (seb128) wrote on 2009-03-02: #1 thank you for your bug report, that's not a bug though, you need to start a dbus session bus or use dbus-launch Changed in gconf: assignee: nobody → desktop-bugs importance: Undecided → Low status: New → Invalid Arnaldo Mandel (am-ime) wrote on 2009-04-13: #2 tomboy.backtrace Edit (4.3 KiB, text/plain) I just upgraded to Jauunty alpha6 from intrepid. The bug is new. gnome-terminal opens fine from my user account. However gksudo gnome-terminal sudo gnome-terminal end with just the line: Failed to contact the GConf daemon; exiting. (there was not even a linefeed at the end) Tried the same with gedit, it came up. Tried
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 http://superuser.com/questions/163058/how-to-fix-a-gconf-error Overflow the company Business Learn more about hiring developers or posting ads with us Super User Questions Tags Users Badges Unanswered Ask Question _ Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How failed to to fix a gconf error? up vote 0 down vote favorite Whenever I log into Ubuntu(10.04), I get the following error. 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://projects.gnome.org/gconf/ for information. (Details - 1: Could not send message to GConf daemon: Connection is closed) My start menu gconf error failed and bottom panel have gone missing. How do I re-configure it? ubuntu-10.04 gconf share|improve this question edited Oct 9 '11 at 7:51 jonsca 2,55592338 asked Jul 13 '10 at 6:21 user41652 1113 migrated from serverfault.com Jul 13 '10 at 13:40 This question came from our site for system and network administrators. add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted I've found the solution and now it is working fine. All of my desktop apps were back and there were no error messages during reboot. I issued the commands: mv .gconfd/saved_state .gconfd/.saved_state pkill -x gnome-session (see ubuntuforums) share|improve this answer edited Oct 9 '11 at 7:51 jonsca 2,55592338 answered Jul 13 '10 at 6:46 user41652 1113 add a comment| up vote 0 down vote see this forum thread and see if any of the fixes help: http://ubuntuforums.org/archive/index.php/t-1169825.html share|improve this answer answered Jul 13 '10 at 6:35 Luma 1963 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer yo