Fix Issue #2148: loadups fail on WSL1 with Xvnc server errors - fixed by adding new flag to medley script, use this flag in loadup script #2163
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes PR#2160, which should be approved and merged first.
This PR fixes Issue #2148 - loadups fail on WSL1 with Xvnc server error.
Root cause of 2148 is that certain Medley sessions in loadups run very quickly - less than 2 seconds. This causes the medley
script (called from loadup) to improperly detect an Xvnc server error. Fixed by adding a command line flag (--automation) that forces the medley script to skip the check for Xvnc server errors. Changed loadup script to call medley with this flag set.
Also add a command line flag to loadup (--forcevnc) that forces loadup to use vnc even on WSL2. This is intended for testing purposes only. So this PR can be tested on WSL2 with this flag.