On Fri, Jan 21, 2011 at 3:36 AM, Jeremy Huddleston <[email protected]> wrote: > > On Jan 20, 2011, at 01:58, iulian dragos wrote: > > > Then I tried to run meld, and here's the output: > > > > $ meld > > > > (process:78120): Gtk-WARNING **: Locale not supported by C library. > > Using the fallback 'C' locale. > > Xlib: extension "RANDR" missing on display "/tmp/launch-hVOIj6/org.x:0". > > Traceback (most recent call last): > > File "/opt/local/bin/meld", line 123, in <module> > > main() > > File "/opt/local/bin/meld", line 115, in main > > app = meld.meldapp.MeldApp() > > File "/opt/local/lib/meld/meld/meldapp.py", line 136, in __init__ > > self.prefs = preferences.MeldPreferences() > > File "/opt/local/lib/meld/meld/preferences.py", line 289, in __init__ > > super(MeldPreferences, self).__init__("/apps/meld", self.defaults) > > File "/opt/local/lib/meld/meld/util/prefs.py", line 92, in __init__ > > self._gconf.add_dir(rootkey, gconf.CLIENT_PRELOAD_NONE) > > glib.GError: 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=8b3f1f14a2f770b7442e2c414d3803b3 --binary-syntax > > --close-stderr' exited with non-zero exit status 1: Autolaunch > > requested, but X11 support not compiled in.\nCannot continue.\n) > > > > I didn't find any information about X11 support in dbus on the net (at > > least, nothing useful). > > dbus doesn't really have anything to do with X11.
I don't doubt that, but then what do you make of the error message? Here it is again: > Command line `dbus-launch > --autolaunch=8b3f1f14a2f770b7442e2c414d3803b3 --binary-syntax > --close-stderr' exited with non-zero exit status 1: Autolaunch > requested, but X11 support not compiled in.\nCannot continue.\n) > > > Can anyone help me? Even just to say that they > > could successfully install and run meld (I'd know at least that my > > quest is possible). > > As mentioned, just load the LaunchAgent. Don't use sudo or you'll be loading > it for root (not your user). Unfortunately, that's what I tried first. It didn't work. Here it is again. $ launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist launchctl: CFURLWriteDataAndPropertiesToResource(/var/db/launchd.db/com.apple.launchd.peruser.501/overrides.plist) failed: -10 The file in /var/db/... is not writeable: $ ll /var/db/launchd.db/com.apple.launchd.peruser.501/overrides.plist -rw-r--r-- 1 root wheel 0 Jan 21 09:51 /var/db/launchd.db/com.apple.launchd.peruser.501/overrides.plist without '-w' the error is even more interesting. $ launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist nothing found to load I found traces of crashes in the system log: 1/20/11 10:43:17 AM com.apple.launchd.peruser.501[208] (org.freedesktop.dbus-session[69379]) Job appears to have crashed: Segmentation fault After I manually changed permissions on /var/db/launchd.db/com.apple.launchd.peruser.501/overrides.plist I could launch dbus-session without root privileges. This has not solved my problem, I still get the previous error message when running meld. thanks everyone for helping, iulian -- « Je déteste la montagne, ça cache le paysage » Alphonse Allais _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
