Hi Rohan, The short answer is: You are using Python 3.
The crash issue has been reported last week and we've found the cause, I will push the fix to the SVN repo later today. Regarding session files: This is tricky. PyMOL session files are Python pickle containers, and fundamental type changes between Python 2 and 3 make Python 3 pickles largely incompatible with Python 2. What we can handle so far: - loading old session files into Python 3 builds - limited support for loading Python 3 session files into new builds with Python 2 We can add a warning message if pse_export_version is used with a Python 3 build of PyMOL, because that's currently unsupported (given that all older versions use Python 2). Cheers, Thomas > On Oct 18, 2017, at 5:07 PM, Rohan Eapen <rs...@cam.ac.uk> wrote: > > Dear all, > > I am currently using PyMOL 1.8.7.0 and have noticed a couple of issues, which > I have been unable to solve so far. > > If I highlight over the "copy to object" line on the action bar in PyMOL > viewer it crashes the program. This occurs on both selections and objects. I > have attempted to work my way through the source code, and see nothing > immediately in fault comparing it to codes found on > https://sourceforge.net/p/pymol/code/4177/ > > I am also attempting to export .pse files to be compatible with earlier > versions of PyMOL. I am able to save them (supposedly in their compatible > forms), but no one with any earlier versions of PyMOL are able to open them. > This is the error that is seen when attempting to open the .pse file. > > Detected OpenGL version 2.0 or greater. Shaders available. > Detected GLSL version 1.30. > OpenGL graphics engine: > GL_VENDOR: Intel Open Source Technology Center > GL_RENDERER: Mesa DRI Intel(R) Haswell Mobile > GL_VERSION: 3.0 Mesa 17.0.7 > Adjusting settings to improve performance for Intel cards. > Detected 4 CPU cores. Enabled multithreaded rendering. > > Warning: This session was created with a newer version of PyMOL (1.870). > Warning: Some content may not load completely. > ExectiveSetSession-Error: after settings. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > Executive: skipping unrecognized object "" of type 0. > ExectiveSetSession-Error: after names. > ExectiveSetSession-Warning: restore may be incomplete. > > > Any help would be greatly appreciated! > > Many thanks, > Rohan > -- > Rohan Eapen > Itzhaki group - PhD student > Department of Pharmacology > University of Cambridge > Tennis Court Road > CB2 1PD > rs...@cam.ac.uk -- Thomas Holder PyMOL Principal Developer Schrödinger, Inc. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net) Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
