epoptes team mailing list archive

[Alkis Georgopoulos <1655795@xxxxxxxxxxxxxxxxxx>]

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?

** Bug watch added: github.com/TigerVNC/tigervnc/issues #400
   https://github.com/TigerVNC/tigervnc/issues/400

-- 
You received this bug notification because you are a member of Epoptes
Developers, which is subscribed to Epoptes.
https://bugs.launchpad.net/bugs/1655795

Title:
  improve support for tigervnc

Status in Epoptes:
  New

Bug description:
  Debian is dropping support for xvnc4viewer (and xtightvnc) in the
  upcoming stretch release, and tigervnc-viewer appears to be *nearly*
  compatible with it as a replacement.

  The attached patch gets this mostly working, but the xtigervncviewer
  processes don't response to the kill signal passed in stopTerminal
  (e.g. client -> broadcasts -> stop broadcasts). They also don't
  respond to manually killing the pid as root, even with "kill -9"...

  the first monitor/assist work fine, but subsequent attempts require
  exiting the epoptes gui.

  Broadcast windowed mode works, but broadcast fullscreen doesn't appear
  to work.

  Using ssvnc might be an alternate option, but has a recommends on
  "default-jre | java5-runtime" packages, which pulls in quite a few
  packages, at least in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epoptes/+bug/1655795/+subscriptions