For posterity, the problem turned out to be that the user had the permissions on his Library/Frameworks folder set such the he himself couldn't access the folder.  Changing the permissions solved the problem.  We will see if there is anything Chimera can do to detect/sidestep the problem in the future.

--Eric

On Jan 7, 2013, at 7:02 PM, Eric Pettersen wrote:

On Jan 7, 2013, at 3:18 PM, Pat Heath wrote:

It starts to open and then quits. User was previously running 1.5 fine. Another user on the same machine can open chimera 1.7 just fine. Makes me think there is a file that needs thrown away from the other user that was generated by version 1.5. I deleted the .chimera folder, but that didn't help. Any ideas?

After a crash, are there any messages either in the "All Messages" or "Console Messages" section of Console.app (in the Utilities folder of /Applications) that appear related (e.g. a stack trace for python 2.7)?  If you start Chimera from the command line with the --debug flag, what output do you get?  [to start from the command line; open Terminal.app (also in Utilities folder) and drag the Chimera icon into the terminal window; the path to the app will appear; append "/Contents/Resources/bin/chimera --debug" to the path and hit Return].

--Eric

                        Eric Pettersen
                        UCSF Computer Graphics Lab
                        http://www.cgl.ucsf.edu