Hi Hugh,
Well, it’s very unlikely that “something happened” that isn’t an ID-10/T error - computers and software doesn’t just decide to “stop working”. In that vain, it would be good if you could give some more detail (see also here and here). For example,
- How did you start the VASSAL session? From a widget? From the command line? If the latter, what exactly did you write on the command line?
- How do you start the VNC viewer? From the command line? From the Android app chooser?
Again, what exactly did you do? Did you give an empty password when executing vncpasswd
? Remember, passwords are case-sensitive (it’s Unix - not MacOuze or Windoze).
Did you try to execute - on the command line - the commands
$ vncserver :1 &
$ termux-url-open vnc://localhost:5901
and if so, did it work?
You do not need root access to check the vncserver
logs. The log file is in
~/vnc/localhost:1.log
which you can view with
$ less ~/vnc/localhost\:1.log
(step through pages with Space
, move back with b
, end with q
)
Did you try
$ vncserver -clean -kill :1
Restarting the tablet shouldn’t really matter - again its Unix, not MacOuze or Windoze.
Did you follow the instructions at How to Run VASSAL on Android (X11)? What did you do exactly that lead up to the problem? Your description above (" It also has a “Not connected” screen, below which there is a Preferences button, a Help button, and an Exit button.") doesn’t help much without some context. What is it you are trying to execute? After installation according to How to Run VASSAL on Android (X11) all you should need to do is run
$ ~/.local/bin/xvassal
from the Termux command line.
It sounds like you are still trying to use your VNC viewer to view the X11 installation - you do not need that - just the stuff listed in the above page, and then the command quoted above.
MultiVNC is not a server - but a client (or viewer). Why it stopped working is hard to tell without some more information on your part. Please be exact so that we may be able to help you. Thanks.
Yours,
Christian