[open] old expts built on OS 10.something do not run on OS Yosemite
Hi Guys,
This is getting funny. The expts that I had built on my another macbook with OS 10.n (can't remember exactly) do not run on OS Yosemite loaded on my new macbook. Do I need any additional plugin for this? Any suggestions?
Thanks,
Comments
Hi,
Could you provide some more detail: What exactly goes wrong, what kind of error message do you get, and what version of OpenSesame do you use?
Cheers
Sebastiaan
Check out SigmundAI.eu for our OpenSesame AI assistant!
Hi there,
I am experiencing the same. Opensesame opens but when I try to run an experiment built in an earlier OS it crashes with the message "An unexpected error occurred, which was not caught by OpenSesame. This should not happen! Message: local variable 'fonts' referenced before assignment"
I tried to reinstall (both the 64 and 32 bit versions) with no effects.
I am running Yosemite 10.10.2 on a macbook pro retina.
Hope you can help?
best
Kristian
Hi Kristylen,
Could you check in your /usr/X11/lib/ folder if there is a libfreetype.6.dylib file, or a file with a similar name but a higher number than 6? If so, could you mention here what name the file(s) have?
Hi again,
I have the libfreetype.6.dylib (and one named libfreetype.dylib) but no similar file with a higher number :-(
K
Strange. Just to be sure, you are using OpenSesame 0.27.4 and this only occurs with old experiments, not with newer ones? I have not enough information to go on, to really pinpoint what causes the problem here.
I have the same problem using a fresh install of the DMG version of OpenSesame. I have updated X11 to the latest (apple provided version), there is one libfreetype.*.dylib file (version 6, in opt/X11/lib) and I get this error also with the example experiments (and with a simple File -> New -> Default Template experiment). After the error is shown in a pop-up dialog box, the pygame window remains on the screen, and can't be closed.
The traceback in the console is:
Is there any way I can be of help in trying to squash this bug? (I'll be looking for a solution myself as well, and will post here if I manage to solve it...)
Changing the backend from xpyriment to legacy solved the crash. This was slightly surprising to me as the error was raised in pygame code, called by expyriment code. If anyone has any pointers...