#22 PyRx won't start on all computer accounts- new download

[John Means]

I just downloaded 0.9.7 to fix the MacOS High Sierra issue. I first installed PyRx from the Administrator account on the computer, and PyRx starts just fine. When I logged into a non-Administrator account on the same computer, I get the error that I pasted below. I tried changing the non-Administrator account to an administrator-level account, but I got the same error. I also tried to reinstall PyRx from the non-Administrator account, but I still got the same error. Meanwhile, PyRx still runs from the Administrator account with no issues. Any guidance would be welcome.

Traceback (most recent call last):
File "/Library/PyRx/0.9.7/runPyRx.py", line 89, in <module>
startPyRx()
File "/Library/PyRx/0.9.7/runPyRx.py", line 38, in startPyRx
frame = MainFrame(None, -1, size=(width, height-200))
File "/Library/PyRx/0.9.7/Python.framework/Versions/2.6/lib/python2.6/site-packages/PyRx/wxMainFrame.py", line 161, in init
from vtkAdaptor import vtkAdaptor
File "/Library/PyRx/0.9.7/Python.framework/Versions/2.6/lib/python2.6/site-packages/PyRx/vtkAdaptor.py", line 7, in <module>
from ePMV.epmvAdaptor import epmvAdaptor, loadMoleculeInHost
ImportError: No module named ePMV.epmvAdaptor</module></module>

Problem starting PyRx. Please submit a bug report to fix this: http://pyrx.sourceforge.net/faq

[Sarkis Dallakian]

Thank you for ordering PyRx 0.9.7. Can you please run the following from Administrator account terminal:

sudo chmod -R 766 /Library/PyRx

This will give read and execute privileges to all files under /Library/PyRx. I think some files in there might not be readable by others and that's what is causing this.

Thank you.

[John Means]

Thank you for the reply. I issued that command, and it seemed to have taken care of the initial error I got from the non-Administrator account. However, I ended up then getting an error telling me that I did not have permission to run /Library/PyRx/0.9.7/run.sh. I changed the permissions to 777, instead of 766, and it's running fine now.

[Sarkis Dallakian]

Great, glad it's working now. Changing permissions to 777 sounds good. Sorry, I didn't realize that 766 gives others read and write but not execute permissions.

Thank you.