RC5, regardless of machine or Mono version, installs applications that cannot be launched graphically on OS X. They simply fail to respond. From the terminal, one can launch the respective contents of Contents/MacOS and the applications do then start. RC4 has no such issues.
RC5, in general, seems to be rather broken on Mac. I’ve deployed RC4 here and it’s working fine. The fact that RC5 is ~50% of the size of RC4 (in terms of the .dmg) has me wondering if something went badly wrong in the packaging stage.
RC6 seems to restore normal operation with Mono 2.6.7, but 2.10.2 results in errors like this when trying to launch any of the DL apps by double clicking :
11/05/2011 19:08:22 /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp[13569] launch failed with error code -2857 (cfragCFragRsrcErr) for application /Applications/Deadline/DeadlineMonitor.app/Contents/MacOS/DeadlineMonitor
11/05/2011 19:08:22 [0x0-0x6ec6ec].net.deadline.DeadlineMonitor[13569] /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp[13569] Launch failed with error code -2857 (cfragCFragRsrcErr) for application /Applications/Deadline/DeadlineMonitor.app/Contents/MacOS/DeadlineMonitor
11/05/2011 19:08:22 com.apple.launchd.peruser.501[238] ([0x0-0x6ec6ec].net.deadline.DeadlineMonitor[13569]) Exited with exit code: 215
LaunchCFM seems to suggest that OS X thinks this is a PowerPC bundle. How odd. The Mono install came from MonoFramework-MRE-2.10.2_5.3.macos10.novell.x86.dmg
Also : lists.apple.com/archives/xcode-u … 00202.html
Launching, for example, DL Monitor directly from its Contents/MacOS executable script, I see this on the terminal :
sierra:MacOS phil$ ./DeadlineMonitor
./DeadlineMonitor: line 1: #!/bin/sh: No such file or directory
Gtk not found (missing LD_LIBRARY_PATH to libgtk-x11-2.0.so.0?), using built-in colorscheme
System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
System.Net.Sockets.SocketOptionName 0x1b is not supported at IPv6 level
UpdateAll (uimanager) !!
Eureka!
The issue is a set of strange characters before # in line 1 of the script (in each case). Removing these using ‘sudo nano’ is enough to fix the click-to-launch. The clue was :
./DeadlineMonitor: line 1: #!/bin/sh: No such file or directory
Wow, good timing! We just discovered this as well. It turned out to be an encoding issue with the sh scripts in the app bundles. Interesting that the encoding issue only occurred when Mono 2.10.x was installed (we found this problem didn’t occur with 2.6.7 installed).
We’ve fixed the encoding issue on our end, so it will be deployed in the next release (either an RC7 release or the actual release).
Cheers,
I’m so relieved. I thought I was going nuts 