After a lengthy upgrade of an outdated macports installation, firefox-x11 builds but fails to run with dbus errors. [ was firefox, orbit2, policykit and many others ]

[aszy@…]

followed commands as directed - still no joy. attached is the verbose dump. thanks, Al

[dbevans (David B. Evans)]

No verbose dump attached.

[aszy@…]

my bad.. learning this system as well.

[dbevans (David B. Evans)]

OK, check to see if port intltool (and what version) is installed

port installed intltool

I suspect you have an older version of intltool somewhere else that is being recognized first by the configure script. What does this say for instance?

find /usr -name intltool-update

[dbevans (David B. Evans)]

actually more to the point is

which intltool-update

[aszy@…]

As directed :...

Last login: Tue Jul  7 10:41:45 on ttyp1
Welcome to Darwin!
Gulliver:~ aszy$ port installed intltool
The following ports are currently installed:
  intltool @0.35.5_0 (active)
Gulliver:~ aszy$ 
Gulliver:~ aszy$ which intltool-update
/opt/local/bin/intltool-update
Gulliver:~ aszy$ 
Gulliver:~ aszy$ 
Gulliver:~ aszy$  find /usr -name intltool-update
Gulliver:~ aszy$ 

[dbevans (David B. Evans)]

OK, it looks like your ports are just not up to date since the current version of intltool is

devans% port list intltool
intltool                       @0.40.6         textproc/intltool

So do this before proceeding

sudo port selfupdate              // makes sure your Portfiles are synced up to date
port outdated                     // shows what's outdated
sudo port upgrade outdated        // upgrade all posts that are outdated
port installed intltool           // hopefully this is now 0.40.6
sudo port clean --work policykit  // make sure we are starting with a clean slate
sudo port install firefox-x11     // hopefully more progress now

Will leave the ticket open this time. Let us know how you're are doing.

[blb@…]

If your install of intltool is at 0.35.5, you will probably have quite the list of outdated ports; intltool was increased to 0.36.2 nearly two years ago in r29286 (and of course more version increases since then).

[aszy@…]

Ran the first three commands and have attached the output as "July7Run" . Clearly I need to upgrade Xcode to 2.5 at least before continuing. This I shall do over the next two days. Thanks again for working through this with me.

[blb@…]

Looks like there are some ports which do need Xcode 2.5; to fix the render/xrenderproto issues, run

sudo port -f uninstall render
sudo port activate xorg-renderproto

You'll also want to upgrade xorg-libXrandr (since it failed due to the renderproto deal):

sudo port upgrade xorg-libXrandr

[aszy@…]

As directed, I have done the following:
Downloaded and installed Xcode 2.5 with no complaints or errors noted.
run the following commands as directed by BLB
'sudo port -f uninstall render'
'sudo port activate xorg-renderproto'
'sudo port upgrade xorg-libXrandr'

I then ran
'sudo port outdated' and received the following:

gimp                           2.2.17_0 < 2.6.6_0        
gtk2                           2.10.13_0 < 2.16.4_0      
libgnomecanvas                 2.14.0_1 < 2.26.0_0       
libsdl                         1.2.11_0 < 1.2.13_6       
pkgconfig                      0.22_0 < 0.23_1           
xrender                        0.9.0_0 < 0.9.4_5   

Next I ran 'sudo port upgrade outdated ' the run for this is attached as "July6run".

Once all the processes were installed, I then ran firefox-x11 and received the following:

Gulliver:/opt/local/bin aszy$ ./firefox-x11
Xlib:  extension "RANDR" missing on display ":0.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!
Xlib:  extension "RANDR" missing on display ":0.0".
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!
^C
Gulliver:/opt/local/bin aszy$ 

Awaiting the wisdom to come.. :)

[dbevans (David B. Evans)]

Not much wisdom -- just initialization for dbus

sudo launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist

Only need to do this once to get things going. The message

Xlib: extension "RANDR" missing on display ":0.0"

Is normal and harmless (no support for extension RANDR on X server).

Looks like you've made a lot of progress.

[aszy@…]

Tried the first command, received the following:

Last login: Wed Jul  8 17:27:10 on ttyp2
Gulliver:~ aszy$ sudo launchctl load -w /Library/LaunchAgent/org.freedesktop.dbus-session.plists
Password:
nothing found to load
Gulliver:~ aszy$ 

looks like the .plist is not even there. yes?

[dbevans (David B. Evans)]

well, it should be there.

devans% port installed dbus
The following ports are currently installed:
  dbus @1.2.14_0 (active)
devans% port contents dbus
Port dbus contains:
  /Library/LaunchAgents/org.freedesktop.dbus-session.plist
  /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
  /opt/local/bin/dbus-cleanup-sockets
  /opt/local/bin/dbus-daemon
  /opt/local/bin/dbus-launch
  /opt/local/bin/dbus-monitor
  /opt/local/bin/dbus-send
  /opt/local/bin/dbus-uuidgen

I see the problem its

sudo launchctl load -w /Library/LaunchAgent/org.freedesktop.dbus-session.plist

not

sudo launchctl load -w /Library/LaunchAgent/org.freedesktop.dbus-session.plists

[aszy@…]

No Joy. .. following dump

Last login: Wed Jul  8 19:33:13 on ttyp1
Welcome to Darwin!
Gulliver:~ aszy$ port installed dbus
The following ports are currently installed:
  dbus @1.2.14_0 (active)
Gulliver:~ aszy$ port contents dbus
Port dbus contains:
  /Library/LaunchAgents/org.freedesktop.dbus-session.plist
  /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
  /opt/local/bin/dbus-cleanup-sockets
  /opt/local/bin/dbus-daemon
  /opt/local/bin/dbus-launch
  /opt/local/bin/dbus-monitor
  /opt/local/bin/dbus-send
  /opt/local/bin/dbus-uuidgen
  /opt/local/etc/dbus-1/session.conf
  /opt/local/etc/dbus-1/session.d/.turd_dbus
  /opt/local/etc/dbus-1/system.conf
  /opt/local/etc/dbus-1/system.d/.turd_dbus
  /opt/local/include/dbus-1.0/dbus/dbus-address.h
  /opt/local/include/dbus-1.0/dbus/dbus-bus.h
  /opt/local/include/dbus-1.0/dbus/dbus-connection.h
  /opt/local/include/dbus-1.0/dbus/dbus-errors.h
  /opt/local/include/dbus-1.0/dbus/dbus-macros.h
  /opt/local/include/dbus-1.0/dbus/dbus-memory.h
  /opt/local/include/dbus-1.0/dbus/dbus-message.h
  /opt/local/include/dbus-1.0/dbus/dbus-misc.h
  /opt/local/include/dbus-1.0/dbus/dbus-pending-call.h
  /opt/local/include/dbus-1.0/dbus/dbus-protocol.h
  /opt/local/include/dbus-1.0/dbus/dbus-server.h
  /opt/local/include/dbus-1.0/dbus/dbus-shared.h
  /opt/local/include/dbus-1.0/dbus/dbus-signature.h
  /opt/local/include/dbus-1.0/dbus/dbus-threads.h
  /opt/local/include/dbus-1.0/dbus/dbus-types.h
  /opt/local/include/dbus-1.0/dbus/dbus.h
  /opt/local/lib/dbus-1.0/include/dbus/dbus-arch-deps.h
  /opt/local/lib/libdbus-1.3.4.0.dylib
  /opt/local/lib/libdbus-1.3.dylib
  /opt/local/lib/libdbus-1.a
  /opt/local/lib/libdbus-1.dylib
  /opt/local/lib/libdbus-1.la
  /opt/local/lib/pkgconfig/dbus-1.pc
  /opt/local/libexec/dbus-daemon-launch-helper
  /opt/local/Library/LaunchAgents/org.freedesktop.dbus-session.plist
  /opt/local/Library/LaunchDaemons/org.freedesktop.dbus-system.plist
  /opt/local/share/dbus-1/services/.turd_dbus
  /opt/local/share/man/man1/dbus-cleanup-sockets.1.gz
  /opt/local/share/man/man1/dbus-daemon.1.gz
  /opt/local/share/man/man1/dbus-launch.1.gz
  /opt/local/share/man/man1/dbus-monitor.1.gz
  /opt/local/share/man/man1/dbus-send.1.gz
  /opt/local/share/man/man1/dbus-uuidgen.1.gz
  /opt/local/var/lib/dbus/machine-id
  /opt/local/var/run/dbus/.turd_dbus

Gulliver:~ aszy$ sudo launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist
Gulliver:~ aszy$ 

So that worked, but when I launch firefox, I get the same complaint about the plist file and RANDR.

Xlib:  extension "RANDR" missing on display ":0.0".
Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded!

When I go through OSX to /Library/LaunchAgents/ I find a link file of the correct name and it's openable with the Property List Manager.

[dbevans (David B. Evans)]

Yes, all this looks correct except for the end result. On my system (10.4.11 ppc, XCode 2.5), when I run firefox this is what I get

devans% firefox
Xlib:  extension "RANDR" missing on display ":0.0".
Xlib:  extension "RANDR" missing on display ":0.0".

and firefox works as expected.

As I mentioned before, the

Xlib:  extension "RANDR" missing on display ":0.0".

warning error is to be expect with the current X11 installation and is not harmful. You'll see this with almost any X11 application.

The rest of the messages are symptomatic of not being able to communicate with dbus and are another thing all together. I can't reproduce the problem here.

You should also see something like

devans% ps ax | grep dbus
  256  ??  Ss     0:00.08 /opt/local/bin/dbus-daemon --nofork --session

So I'm at the end of my "wisdom" now. Am copying the maintainer of dbus as he, hopefully, knows more about the situation at hand.

Also updating the summary to reflect the current state of affairs

[MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)]

launchctl must be run twice.
Try:

sudo launchctl load -w /Library/LaunchDaemons/org.freedesktop.dbus-system.plist
sudo launchctl load -w /Library/LaunchAgents/org.freedesktop.dbus-session.plist

Then restart your machine to make sure everything is loaded properly (this may not be needed, but it couldn't hurt).

[aszy@…]

I am truly thankful for all of the participants assistance. This last note, by mcalhoun, tipped the iceberg and I now have a running copy. As earlier alluded to, I also get the RANDR errors ( three of them ) but the application works wonderfully. In your debt. Al

[aszy@…]

Ah... that was short lived.. after getting to the Gran Paradiso page, and clicking on , for example , the Add-ons link, the entire X11 system crashes. Firefox does run, but there's a kink somewhere still. Also the Gran Paradiso page suggests that the version is not up to date. al

[aszy@…]

I have attached the "Report to Apple" that came up after the crash - it took X11 , Quartz down. Crashes if I launch via command line as well as from the 'Quick Launch'. Is there somewhere else that will have a better crash report so that I can help from my end? al

[blb@…]

That crash could be related to one Ryan reported against ​cairo some months back. No idea where the actual problem may be (10.4's X11, cairo, something else) though.

[ryandesign (Ryan Carsten Schmidt)]

MacPorts should not be using Apple's X11 anymore; we have our own. If you are not already using it, you may want to use the X11.app installed in /Applications/MacPorts by the xorg-server port (and also install the quartz-wm port) instead of using the X11.app installed by Apple in /Applications/Utilities.

[aszy@…]

Replying to ryandesign@…:

MacPorts should not be using Apple's X11 anymore; we have our own. If you are not already using it, you may want to use the X11.app installed in /Applications/MacPorts by the xorg-server port (and also install the quartz-wm port) instead of using the X11.app installed by Apple in /Applications/Utilities.

Thank you for this tip - I wonder if most of the troubles have been using a different version of X11. Can I safely and securely have both Apple's X11 and the X11.app from MacPorts installed? Any known clashes? Any trouble with having the quartz-wm port for the X11.app interfering with the Apple X11.

[jmroot (Joshua Root)]

This doesn't appear to be relevant any more.