epoptes team mailing list archive

[Alkis Georgopoulos <1655795@xxxxxxxxxxxxxxxxxx>]

** Changed in: epoptes
       Status: New => Fix Released

** Changed in: epoptes
       Status: Fix Released => Unknown

** Changed in: epoptes
       Status: Unknown => New

** Changed in: epoptes
       Status: New => Fix Released

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

** Bug watch removed: Epoptes bug tracker #22
   https://github.com/epoptes/epoptes/issues/22

-- 
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:
  Fix Released

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