[MacPorts] #22272: dbus default of --without-x cause errors like "GConf error Failed to contact configuration server"
#22272: dbus default of --without-x cause errors like "GConf error Failed to contact configuration server" ------------------------------+--------------------------------------------- Reporter: fernasser@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: GConf | Port: dbus ------------------------------+--------------------------------------------- This affects several applications, like file-roller (on Snow Leopard). My version of dbus is: @1.2.16, Revision 1 (devel) It has also been reported in the past and people have been rebuilding it with x but it is hard for the less savvy. Here is a good reference to a similar problem and a proposed fix: http://trac.macports.org/ticket/16755 May I suggest you change the default? I am not sure if one could get all applications affected to specify a variant (with-x) instead. I am not sure why the default is without X). -- Ticket URL: <http://trac.macports.org/ticket/22272> MacPorts <http://www.macports.org/> Ports system for Mac OS
#22272: dbus default of --without-x cause errors like "GConf error Failed to contact configuration server" ------------------------------+--------------------------------------------- Reporter: fernasser@… | Owner: mcalhoun@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Keywords: GConf | Port: dbus ------------------------------+--------------------------------------------- Changes (by macsforever2000@…): * owner: macports-tickets@… => mcalhoun@… Old description:
This affects several applications, like file-roller (on Snow Leopard).
My version of dbus is: @1.2.16, Revision 1 (devel)
It has also been reported in the past and people have been rebuilding it with x but it is hard for the less savvy.
Here is a good reference to a similar problem and a proposed fix:
http://trac.macports.org/ticket/16755
May I suggest you change the default?
I am not sure if one could get all applications affected to specify a variant (with-x) instead. I am not sure why the default is without X).
New description: This affects several applications, like file-roller (on Snow Leopard). My version of dbus is: @1.2.16, Revision 1 (devel) It has also been reported in the past and people have been rebuilding it with x but it is hard for the less savvy. Here is a good reference to a similar problem and a proposed fix: ticket:16755 May I suggest you change the default? I am not sure if one could get all applications affected to specify a variant (with-x) instead. I am not sure why the default is without X). -- -- Ticket URL: <http://trac.macports.org/ticket/22272#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#22272: dbus default of --without-x cause errors like "GConf error Failed to contact configuration server" -------------------------------+-------------------------------------------- Reporter: fernasser@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Resolution: worksforme | Keywords: GConf Port: dbus | -------------------------------+-------------------------------------------- Changes (by jmr@…): * status: new => closed * resolution: => worksforme Comment: Can't reproduce with current versions. -- Ticket URL: <https://trac.macports.org/ticket/22272#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#22272: dbus default of --without-x cause errors like "GConf error Failed to contact configuration server" -------------------------------+-------------------------------------------- Reporter: fernasser@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.8.1 Resolution: worksforme | Keywords: GConf Port: dbus | -------------------------------+-------------------------------------------- Comment(by dports@…): Not sure if that's the case for this (old) bug report, but when I see similar things now what's usually going on is that something couldn't find dbus with launchd, then tries to fall back on dbus's X support and gives an error because we don't build that. The solution is to make dbus/launchd work, not to rebuild it with X support. -- Ticket URL: <https://trac.macports.org/ticket/22272#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts