Stupid Adobe scripting library bug
February 9th, 2010 | by Jamie Baxter |Have you ever been plagued with a bunch of these errors in your console?
2/8/10 10:51:13 PM osascript[24251] Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:
/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapperiTunes especially likes to choke these out (as my machine did), as shown here:
2/8/10 10:51:13 PM [0x0-0xd4ed4e].com.apple.iTunes[52368] 2010-02-08 22:51:13.952 osascript[24251:607] Error loading /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: dlopen(/Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types, 262): no suitable image found. Did find:2/8/10 10:51:13 PM [0x0-0xd4ed4e].com.apple.iTunes[52368] /Library/ScriptingAdditions/Adobe Unit Types.osax/Contents/MacOS/Adobe Unit Types: no matching architecture in universal wrapperIn order to get rid of these, it’s a relatively easy fix.
In the link above, Solution 1 worked marvelously. My console is essentially scripting-error free now, so osascript can rest easily…for now.
The other two solutions are only temporary fixes, while Solution 1 should persist and stay propagated through system reboots. Bear in mind, this should only be an issue if you’re running your version of Snow Leopard with the 64-bit kernel, however it appears this also plagues 32-bit kernel users as the operating system still starts up the scripting processes in 64-bit mode since they’re available.
So, go 64-bit library Unit Types, go old-school rollback to Leopard, or just plain ol’ go home!