Hi @stephan, thanks for the tip, that’s a good one and I’ll use in the future! I see the cryosparcm commands are documented here in management and monitoring but it would be really helpful if when executing cryosparcm without inputs or with -h the available commands were reported to the terminal to quickly spot options like this one.
Regarding this error, I found a solution of sorts, at least in my local environment. When installing CryoSPARC I was dropping into a TTY (Ctrl-Alt-F2) to avoid any environment issues upsetting CryoSPARC. This has worked in the past and avoided system anaconda problems (see: Can't start after update to 2.8). For the version 2.12.0, using this method results in the above reported error when starting cryosparm in a terminal. When I installed 2.12.0 in a standard interactive terminal the install proceeds and then cryosparcm starts normally.