[MacPorts] #28077: gnome-terminal and gconf error
#28077: gnome-terminal and gconf error -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gnome-terminal -------------------------------------+-------------------------------------- Upgrade to the new version of gconf, now gnome-terminal fails to start with following error: Failed to summon the GConf demon; exiting. 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: Command line `dbus-launch --autolaunch=537233c7d8732f36e8be01074d373c87 --binary-syntax --close- stderr' exited with non-zero exit status 1: Autolaunch requested, but X11 support not compiled in.\nCannot continue.\n) -- Ticket URL: <https://trac.macports.org/ticket/28077> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gnome-terminal and gconf error -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gnome-terminal -------------------------------------+-------------------------------------- Comment(by jaguarul@…): I have the exact same problem, while running 'meld'. I think dbus is seriously broken at the moment. I managed to recompile dbus with X support (by modifying the Portfile) and hit another error: {{{ Failed to get connection to session: Command line `dbus-launch --autolaunch=dcd4a7ddcfeaaf21e1b9c3444d39597f --binary-syntax --close- stderr' exited with non-zero exit status 1: EOF in dbus-launch reading address from bus daemon\n) }}} -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gnome-terminal and gconf error -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gnome-terminal -------------------------------------+-------------------------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => devans@… * cc: devans@… (removed) -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gnome-terminal and gconf error -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gnome-terminal -------------------------------------+-------------------------------------- Description changed by macsforever2000@…: Old description:
Upgrade to the new version of gconf, now gnome-terminal fails to start with following error: Failed to summon the GConf demon; exiting. 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: Command line `dbus-launch --autolaunch=537233c7d8732f36e8be01074d373c87 --binary-syntax --close- stderr' exited with non-zero exit status 1: Autolaunch requested, but X11 support not compiled in.\nCannot continue.\n)
New description: Upgrade to the new version of gconf, now gnome-terminal fails to start with following error: {{{ Failed to summon the GConf demon; exiting. 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: Command line `dbus-launch --autolaunch=537233c7d8732f36e8be01074d373c87 --binary-syntax --close- stderr' exited with non-zero exit status 1: Autolaunch requested, but X11 support not compiled in.\nCannot continue.\n) }}} -- -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gnome-terminal and gconf error -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: devans@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gnome-terminal -------------------------------------+-------------------------------------- Comment(by drowe@…): I think I am getting the same problem, this time trying to run Gnucash - this has just been updated from 2.4.0_1 to 2.4.0_2 - but it no longer starts up properly. Instead, Gnucash displays error dialogues saying: "The configuration data used to specify default values for Gnucash cannot be found in the default system locations . . . " This problem has occurred several times before when gconf has been unable to contact dbus. I noticed that gconf has just been updated from 2.28.1_0 to 2.32.0_0 (at the same time as the gnucash update, and a lot of other updates). So I tried reverting gconf to 2.28.1_0 and the new gnucash now seems to work OK -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gconf -------------------------------------+-------------------------------------- Changes (by jmr@…): * owner: devans@… => ryandesign@… * cc: devans@… (added) * port: gnome-terminal => gconf -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:7> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gconf -------------------------------------+-------------------------------------- Comment(by ryandesign@…): I guess this was assigned to me because I was the one who updated gconf, but I only did so because I noticed the update was available; I don't deliberately use or know anything about gconf. I can revert gconf to the previous version, and/or someone could report this issue to the developers of gconf and see if there is another solution. -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gconf -------------------------------------+-------------------------------------- Comment(by info@…): I am seeing the same problem. I've just installed MacPorts for the first time, on a new mac, and Gnucash is giving the same issues as above. I tried activating an earlier version of gconf (download 2.28.1_0 from svn and install), but the issue seems to remain, even after a reboot. Gnucash still asks me for configuration settings each time - as above. -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps -------------------------------------+-------------------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Keywords: | Port: gconf -------------------------------------+-------------------------------------- Comment(by dports@…): I'm hitting this too, and reverting to gconf 2.28 fixed it. Unless someone actually knows what's going on, and preferably how to fix it (I certainly don't), I say we back out the upgrade for now. -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps --------------------------------------+------------------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: Port: gconf | --------------------------------------+------------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Comment: Reverted in r75352. -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS
#28077: gconf runtime error with multiple apps -------------------------------+-------------------------- Reporter: david.w.watson@… | Owner: ryandesign@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: Port: gconf | -------------------------------+-------------------------- Comment (by devans@…): Please see proposed fix for root cause in #39145. -- Ticket URL: <https://trac.macports.org/ticket/28077#comment:13> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts