For some reason, your DAS registry setting might have become corrupted. Here's how to fix it:
If Jalview won't run, or the Installer won't launch on your Mac, then you may need to temporarily disable the 'Gatekeeper' in your system settings to allow programs to be run from 'Anywhere'.
The OSX InstallAnywhere version of Jalview is downloaded as a ZIP archive (install.zip) which is normally unpacked automatically to create an application called 'install' that you can run. If nothing happens when you double click the application, then there are a few things that could go wrong.
Installer doesn't launch because it was unpacked with a third-party archive tool
This error (and others like it) is raised when an old version of the Jalview Webstart JNLP is being used to launch the latest version of the application (for instance, because you have created your own JNLP file in order to increase the memory available to Jalview).
To fix, first make sure that you are using the latest version of the Jalview JNLP file (right-click or apple-click to save this link to a file) to launch jalview.
Some latest versions of Linux fail to install with InstallAnywhere and will generate error messages such as "error while loading shared libraries: libm.so.6: cannot open". The problem can be fixed by modifying the install.bin script, and also the Jalview script.
cp install.bin install.bak
cat install.bak | sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" > install.bin
cp Jalview Jalview.bak
cat Jalview.bak | sed "s/export LD_ASSUME_KERNEL/#xport LD_ASSUME_KERNEL/" > Jalview
Yes! Just remember to include the '-nodisplay' flag on the command line (and if in doubt, also include java -Djava.awt.headless=true to tell Java not to attempt to use the graphics environment)
java -Djava.awt.headless=true .. jalview.bin.Jalview -nodisplay -open ...
The latest version of Jalview should run fine on a server without a graphics environment, but some operations may fail. If you encounter problems, submit a bug report.
Firstly, see if you can reproduce the bug. Check Jalview's memory settings (Desktop->Tools->Show Memory usage) to make sure you have at least 50% memory free when testing this. If not, the problem might be because you ran out of memory when using Jalview.
Then, follow the instructions below to gather essential information regarding the bug: