osascript console messages

Question

Level 2

251 points

osascript console messages

I am getting the following errors / warnings / messages in my console very frequently....

10/13/09 12:02:00 PM osascript[18847] 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 wrapper

Any ideas what that is? I am not running any Adobe programs at the moment.

MacBook Pro '09 15", MacMini '09, iPhone 3G[S], Mac OS X (10.6.1)

Posted on Oct 13, 2009 9:11 AM

Reply

Answer 1

V.K.

Level 9

56,174 points

Oct 13, 2009 9:53 AM in response to Joshua

Any ideas what that is? I am not running any Adobe programs at the moment.

I suspect you still do have some adobe programs automatically running in the background. they are responsible for these messages. what Adobe products have you used in the past? you likely did not uninstall them correctly.
also, this link provides a SL compatible version of the Adobe Scripting Additions
http://kb2.adobe.com/cps/516/cpsid_51615.html
but if you are not using any adobe products anymore you should uninstall them all cleanly rather than using that link.

Reply

Answer 2

Joshua Author

Level 2

251 points

Oct 13, 2009 9:59 AM in response to V.K.

I am still using CS4 products... none of them are launched at the moment and it was done w/a clean adobe install (w/ their removal tool) first before installing CS4.

Just not sure what this Adobe Unit Types thing is and why it keeps coming up.

Reply

Answer 3

V.K.

Level 9

56,174 points

Oct 13, 2009 10:09 AM in response to Joshua

the fact that CS4 is not launched at the moment does not mean much. It probably installed some helper programs that run all the time in the background. that's very common and many apps do that. try the link I gave you.

Reply

Answer 4

jdien

Level 1

5 points

Dec 17, 2009 6:05 PM in response to Joshua

I got a similar message when I tried to use an entirely different Applescript library that stopped working when I upgraded to Snow Leopard (segmentation error). When I tried removing the Adobe library I still got the segmentation error but nothing more about the Adobe library. My guess is that for some reason when there is a problem loading an addition from another Applescript library it is defaulting to looking in the Adobe library and then giving you this message. So your problem has nothing to do with the Adobe library but is rather due to failed attempts to load in an Applescript command from a different library.

Reply