Ticket #22272 (closed defect: worksforme)
dbus default of --without-x cause errors like "GConf error Failed to contact configuration server"
| Reported by: | fernasser@… | Owned by: | mcalhoun@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.1 |
| Keywords: | GConf | Cc: | |
| Port: | dbus |
Description (last modified by macsforever2000@…) (diff)
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:
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).
Change History
comment:1 Changed 4 years ago by macsforever2000@…
- Owner changed from macports-tickets@… to mcalhoun@…
- Description modified (diff)
comment:2 Changed 2 years ago by jmr@…
- Status changed from new to closed
- Resolution set to worksforme
Can't reproduce with current versions.
comment:3 Changed 2 years ago 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.