Details
-
Type:
Bug
-
Status: Ready for testing
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.11.5.0
-
Fix Version/s: None
-
Component/s: getdown
-
Labels:None
-
Environment:University of Dundee managed Windows 10 Enterprise desktop
-
Urgency:Urgent
Description
[Updated name] - [~soares] confirmed this also happens on Windows and Linux native install as well as the AppsAnywhere distribution.
When launching Jalview 2.11.5.0 for the first time in AppsAnywhere (2.11.4.0) it seems to work.
Subsequent launches open getdown, which loads up to 100%, disappears (after its own timeout) but then the Jalview desktop window either doesn't appear or takes an inordinately long time to appear with lots of loading file progress bars.
The .jalview.log seems to suggest why this might be happening as it has malformed the Java launch command to have a large number of repeated
"C:\Users\bsoares\AppData\Local\Jalview-Desktop\Jalview\f0275e26\app" \
"jalview" \
arguments on the end of the correct command.
Jalview log file attached.
When launching Jalview 2.11.5.0 for the first time in AppsAnywhere (2.11.4.0) it seems to work.
Subsequent launches open getdown, which loads up to 100%, disappears (after its own timeout) but then the Jalview desktop window either doesn't appear or takes an inordinately long time to appear with lots of loading file progress bars.
The .jalview.log seems to suggest why this might be happening as it has malformed the Java launch command to have a large number of repeated
"C:\Users\bsoares\AppData\Local\Jalview-Desktop\Jalview\f0275e26\app" \
"jalview" \
arguments on the end of the correct command.
Jalview log file attached.
Attachments
Issue Links
- related with
-
JAL-4615 Add unit tests for getdown / install4j launching
-
- In Progress
-
- mentioned on
(5 mentioned on)