The other one is that sometimes it doesn't exit cleanly, preventing new viewers from launching. Unfortunately I haven't found a reliable way to reproduce it, it only happens some times.
If upstream accepts those to be bugs, I guess we can recommend tigervnc in epoptes, and leave it up to the tigervnc debian maintainer to backport the fixes to debian stretch?
I've noticed two separate issues, one is that `xtigervncviewer -listen` doesn't accept multiple incoming connections; I reported it in https:/ /github. com/TigerVNC/ tigervnc/ issues/ 400.
The other one is that sometimes it doesn't exit cleanly, preventing new viewers from launching. Unfortunately I haven't found a reliable way to reproduce it, it only happens some times.
If upstream accepts those to be bugs, I guess we can recommend tigervnc in epoptes, and leave it up to the tigervnc debian maintainer to backport the fixes to debian stretch?