Unfortunately tigervnc is lacking feature for multiple connect to the same listen port. So if epoptes can use new port for every connection the above patch works only for the first connection, then epoptes has to be restarted.
https://github.com/TigerVNC/tigervnc/issues/227 In the mean time, we use tightvnc, the attached patch is needed to avoid epoptes launching the default tigervnc's vncviewer. ** Patch added: "epoptes-support-tightvnc.patch" https://bugs.launchpad.net/epoptes/+bug/1501747/+attachment/4579930/+files/epoptes-support-tightvnc.patch -- You received this bug notification because you are a member of Epoptes Developers, which is subscribed to Epoptes. https://bugs.launchpad.net/bugs/1501747 Title: unble to launch Assist/Monitor when using vncviewer from tigervnc Status in Epoptes: Fix Released Bug description: vncviewer from tigervnc requires launching like xvnc4viewer, so may be test to find out which vncviewer binary is used before launching it would be better. On openSUSE there is /usr/bin/vncviewer-tigervnc actual binary and /usr/bin/vncviewer is link to /etc/alternatives/vncviewer. On suse the attached patch would work, however it does not solve issue with other distributions that install vncviewer binary which is from tigervnc. For example on CentOS /usr/bin/vncviewer is actual binary provided by tigervnc. Only way I could discover if the binary comes from tigervnc is like this:: if grep TigerVNC /usr/bin/vncviewer; then echo "this is vncviewer-tigervnc, using vnc4viewer parameters" elif grep TightVNC /usr/bin/vncviewer; then echo "this is TightVNC vncviewer, using old school parameters to launch" else echo "unknown vncviewer, using .... parameters to launch" fi Don't know python equal of this. To manage notifications about this bug go to: https://bugs.launchpad.net/epoptes/+bug/1501747/+subscriptions -- Mailing list: https://launchpad.net/~epoptes Post to : [email protected] Unsubscribe : https://launchpad.net/~epoptes More help : https://help.launchpad.net/ListHelp
