Discussion:
Meld fails to start; complains about launchd not providing socket path
Garth Dahlstrom
2009-05-19 14:58:22 UTC
Permalink
Hi everyone,

I'm a bit of a mac ports noob, I searched around, but haven't found
anything specifically relating to meld and this issue.

I'm wondering if there is some Gnome base dependency (this is the first
gnome based app I've tried), KDiff3 built, so I know at least the base X11
is okay.

Any suggestions as to how to fix the error below, or even what terms I
should be googling for would be appreciated.

Thanks,

-G

[797] ***@garth-dahlstroms-macbook:~$ meld
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Traceback (most recent call last):
File "/opt/local/bin/meld", line 109, in <module>
meldapp.main()
File "/opt/local/lib/meld/meldapp.py", line 855, in main
app = MeldApp()
File "/opt/local/lib/meld/meldapp.py", line 528, in __init__
self.prefs = MeldPreferences()
File "/opt/local/lib/meld/meldapp.py", line 465, in __init__
prefs.Preferences.__init__(self, "/apps/meld", self.defaults)
File "/opt/local/lib/meld/prefs.py", line 91, 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: Not enough
memory)

[797] ***@garth-dahlstroms-macbook:~$ meld
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Traceback (most recent call last):
File "/opt/local/bin/meld", line 109, in <module>
meldapp.main()
File "/opt/local/lib/meld/meldapp.py", line 855, in main
app = MeldApp()
File "/opt/local/lib/meld/meldapp.py", line 528, in __init__
self.prefs = MeldPreferences()
File "/opt/local/lib/meld/meldapp.py", line 465, in __init__
prefs.Preferences.__init__(self, "/apps/meld", self.defaults)
File "/opt/local/lib/meld/prefs.py", line 91, 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: Not enough
memory)

[801] ***@garth-dahlstroms-macbook:~$ sudo port installed | grep -i orbit
orbit2 @2.14.17_0 (active)
py25-orbit @2.24.0_0+darwin_9 (active)
[802] ***@garth-dahlstroms-macbook:~$ sudo port installed | grep -i launch
commons-launcher @1.1_0 (active)
Ryan Schmidt
2009-05-20 07:15:18 UTC
Permalink
Post by Garth Dahlstrom
I'm a bit of a mac ports noob, I searched around, but haven't
found anything specifically relating to meld and this issue.
Welcome to MacPorts!
Post by Garth Dahlstrom
I'm wondering if there is some Gnome base dependency (this is the
first gnome based app I've tried), KDiff3 built, so I know at least
the base X11 is okay.
Any suggestions as to how to fix the error below, or even what
terms I should be googling for would be appreciated.
Thanks,
-G
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not
provide a socket path, verify that org.freedesktop.dbus-
session.plist is loaded!
Did you load org.freedesktop.dbus-session.plist? If not, someone more
familiar with this software should be able to tell you how, though I
expect one of the dbus ports would have printed a message for you
during installation explaining how to do so.
Garth Dahlstrom
2009-05-21 01:32:02 UTC
Permalink
Post by Garth Dahlstrom
I'm wondering if there is some Gnome base dependency (this is the first
Post by Garth Dahlstrom
gnome based app I've tried), KDiff3 built, so I know at least the base X11
is okay.
Any suggestions as to how to fix the error below, or even what terms I
should be googling for would be appreciated.
Thanks,
-G
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Did you load org.freedesktop.dbus-session.plist? If not, someone more
familiar with this software should be able to tell you how, though I expect
one of the dbus ports would have printed a message for you during
installation explaining how to do so.
Hi Ryan,

I haven't because I don't have an idea how one would go about loading it, I
presume its part of gnome (being that it dbus is part of its name)...

Here's the gnome stuff that's been sucked in from meld and the other
packages I've built from ports so far, maybe the meld package is missing a
dep?

[558] ***@garth-dahlstroms-macbook:~/Documents/workspace/ums-code/A/trunk$
sudo port installed | grep -i gnome
gnome-common @2.26.0_0 (active)
gnome-doc-utils @0.16.1_0 (active)
gnome-icon-theme @2.26.0_0 (active)
gnome-keyring @2.26.1_0 (active)
gnome-mime-data @2.18.0_3 (active)
gnome-vfs @2.24.1_0 (active)
libgnome @2.26.0_0 (active)
libgnomecanvas @2.26.0_0 (active)
libgnomeui @2.24.1_0 (active)
py25-gnome @2.26.1_0+darwin_9 (active)
Ryan Schmidt
2009-05-21 02:51:15 UTC
Permalink
Post by Garth Dahlstrom
Post by Ryan Schmidt
Post by Garth Dahlstrom
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not
provide a socket path, verify that org.freedesktop.dbus-
session.plist is loaded!
Did you load org.freedesktop.dbus-session.plist? If not, someone
more familiar with this software should be able to tell you how,
though I expect one of the dbus ports would have printed a message
for you during installation explaining how to do so.
I haven't because I don't have an idea how one would go about
loading it, I presume its part of gnome (being that it dbus is
part of its name)...
Here's the gnome stuff that's been sucked in from meld and the
other packages I've built from ports so far, maybe the meld package
is missing a dep?
trunk$ sudo port installed | grep -i gnome
org.freedesktop.dbus-session.plist is provided by the dbus port,
which you should have because gnome-vfs depends on it. The dbus port
should have printed this message when it was installed:

########################################################################
#########################
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following command to start them,
# and to cause it to launch at startup:
#
# sudo launchctl load -w ${startup_root}/Library/LaunchDaemons/
org.freedesktop.dbus-system.plist
# sudo launchctl load -w ${startup_root}/Library/LaunchAgents/
org.freedesktop.dbus-session.plist
########################################################################
##########################

If you used the +no_root variant of dbus, then the command "sudo"
would have been omitted in these instructions.
Garth Dahlstrom
2009-05-21 04:13:44 UTC
Permalink
I missed totally that, serves me right for not reviewing the build
output.... Thanks to both William and yourself for the magic lines...
Having rebooted, I now have meld going.

Cheers,

-G
__
--- == __/ t.O ==--
http://stacktrace.org/
Post by Garth Dahlstrom
Post by Ryan Schmidt
Post by Garth Dahlstrom
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not provide a
socket path, verify that org.freedesktop.dbus-session.plist is loaded!
Did you load org.freedesktop.dbus-session.plist? If not, someone more
familiar with this software should be able to tell you how, though I expect
one of the dbus ports would have printed a message for you during
installation explaining how to do so.
I haven't because I don't have an idea how one would go about loading it,
I presume its part of gnome (being that it dbus is part of its name)...
Here's the gnome stuff that's been sucked in from meld and the other
packages I've built from ports so far, maybe the meld package is missing a
dep?
sudo port installed | grep -i gnome
org.freedesktop.dbus-session.plist is provided by the dbus port, which you
should have because gnome-vfs depends on it. The dbus port should have
#################################################################################################
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following command to start them,
#
# sudo launchctl load -w
${startup_root}/Library/LaunchDaemons/org.freedesktop.dbus-system.plist
# sudo launchctl load -w
${startup_root}/Library/LaunchAgents/org.freedesktop.dbus-session.plist
##################################################################################################
If you used the +no_root variant of dbus, then the command "sudo" would
have been omitted in these instructions.
Mike Alexander
2009-05-22 05:16:47 UTC
Permalink
--On May 20, 2009 9:51:15 PM -0500 Ryan Schmidt
Post by Ryan Schmidt
org.freedesktop.dbus-session.plist is provided by the dbus port,
which you should have because gnome-vfs depends on it. The dbus port
#####################################################################
############################
# Startup items have been generated that will aid in
# starting dbus with launchd. They are disabled
# by default. Execute the following command to start them,
#
# sudo launchctl load -w
${startup_root}/Library/LaunchDaemons/org.freedesktop.dbus-system.plist
Post by Ryan Schmidt
# sudo launchctl load -w
${startup_root}/Library/LaunchAgents/org.freedesktop.dbus-session.plist
Post by Ryan Schmidt
#####################################################################
#############################
If you used the +no_root variant of dbus, then the command "sudo"
would have been omitted in these instructions.
This message is slightly wrong in the current version of the dbus
Portfile. I think a more nearly correct version would be

#################################################################################################
# Startup items have been generated that will aid in
# starting ${portname} with launchd. They are disabled
# by default. Execute the following command to start the system bus,
# and to cause it to launch at startup:
#
# ${sudo}launchctl load -w ${startup_root}/Library/LaunchDaemons/[file
tail ${plistFl}]
#
# Execute the following command for each user using dbus to cause the
session bus to
# be started automatically when needed (you do not want sudo on this
command):
#
# launchctl load
${startup_root}/Library/LaunchAgents/org.freedesktop.dbus-session.plist
##################################################################################################

This assumes you installed dbus without +no_root
Rainer Müller
2009-05-25 02:15:22 UTC
Permalink
Post by Mike Alexander
This message is slightly wrong in the current version of the dbus
Portfile. I think a more nearly correct version would be
#################################################################################################
# Startup items have been generated that will aid in
# starting ${portname} with launchd. They are disabled
# by default. Execute the following command to start the system bus,
#
# ${sudo}launchctl load -w ${startup_root}/Library/LaunchDaemons/[file
tail ${plistFl}]
#
# Execute the following command for each user using dbus to cause the
session bus to
# be started automatically when needed (you do not want sudo on this
#
# launchctl load
${startup_root}/Library/LaunchAgents/org.freedesktop.dbus-session.plist
##################################################################################################
You are right, the org.freedesktop.dbus-session.plist is intended to be
loaded by a user, not system-wide by root.

The message has been changed by mcalhoun in r49300. The old message was:

##############################################################################
# It is absolutely necessary for dbus enabled programs to work to execute
#
# launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist
#
# once for every user. Don't use 'sudo', else it will work only for root!
# You also have to unload it before deactivating/uninstalling this software!
##############################################################################

This was more correct and it should be changed to read like this again
in my opinion.

Rainer
Marcus Calhoun-Lopez
2009-05-26 22:02:57 UTC
Permalink
Post by Rainer Müller
You are right, the org.freedesktop.dbus-session.plist is intended to be
loaded by a user, not system-wide by root.
The message has been changed by mcalhoun in r49300.
#########################################################
# It is absolutely necessary for dbus enabled programs to work to execute
#
# launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist
#
# once for every user. Don't use 'sudo', else it will work only for root!
# You also have to unload it before deactivating/uninstalling this software!
#########################################################
This was more correct and it should be changed to read like this again
in my opinion.
Rainer
Sorry for joining this discussion late.
Here is the current situation on the dbus startup files:

* The system-level daemon installed in /Library/LaunchDaemons is disabled
by default to mimic the MacPorts startup mechanism.

* Since the system-level daemon is disabled, the per-user agents installed in
/Library/LaunchAgents is also disabled by default.

* Without first enabling, them I do not think
launchctl load /Library/LaunchAgents/org.freedesktop.dbus-session.plist
does anything unless the -F flag is used.

* Only root has permission to permanently enable the files, hence the sudo in
sudo launchctl load -w /Library/LaunchDaemons/...
and
sudo launchctl load -w /Library/LaunchAgents/...

* The "-w" is intentional in both commands because that is what
permanently enables the file.

* After this, at least on my machine, there was no reason for each user to run
launchctl.
Everything worked for me.

Please let me know if I have something incorrect here.
I am aware of a problem of
/Library/LaunchAgents/org.freedesktop.dbus-session.plist
being a broken link:
http://permalink.gmane.org/gmane.os.apple.macports.user/14831
and
http://trac.macports.org/ticket/19510
but I do not think that is the problem here.

-Marcus

William Davis
2009-05-21 03:08:02 UTC
Permalink
###########################################################
# A startup item has been generated that will aid in
# starting dbus with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo launchctl load -w /Library/LaunchDaemons/org.macports.dbus.plist
###########################################################
good luck
WSD
On Wed, May 20, 2009 at 3:15 AM, Ryan Schmidt
I'm wondering if there is some Gnome base dependency (this is the
first gnome based app I've tried), KDiff3 built, so I know at least
the base X11 is okay.
Any suggestions as to how to fix the error below, or even what terms
I should be googling for would be appreciated.
Thanks,
-G
Xlib: extension "RANDR" missing on display "/tmp/launch-Y4N79L/:0".
Dynamic session lookup supported but failed: launchd did not provide
a socket path, verify that org.freedesktop.dbus-session.plist is
loaded!
Did you load org.freedesktop.dbus-session.plist? If not, someone
more familiar with this software should be able to tell you how,
though I expect one of the dbus ports would have printed a message
for you during installation explaining how to do so.
Hi Ryan,
I haven't because I don't have an idea how one would go about
loading it, I presume its part of gnome (being that it dbus is part
of its name)...
Here's the gnome stuff that's been sucked in from meld and the other
packages I've built from ports so far, maybe the meld package is
missing a dep?
trunk$ sudo port installed | grep -i gnome
_______________________________________________
macports-users mailing list
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.3.3.2 (xorg-server 1.4.2-apple42)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non
Loading...