Prefer ssvncviewer over xvnc4viewer in clients
Bug #1030853 reported by
Laércio de Sousa
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Epoptes |
Fix Released
|
Wishlist
|
Alkis Georgopoulos |
Bug Description
I'm using a forked version of Epoptes with a workaround for broadcasting to work properly in a multiseat environment (lp:~oiteam/epoptes/workaround-broadcasting-multiseat), as suggested in LP #978050.
The broadcasts work fine when the clients have xvnc4viewer installed. However, when I switch to ssvncviewer, the broadcasts stop working. I can get no error message to find out why ssvncviewer fails to start in clients.
Nevertheless, when I launch ssvncviewer locally in client, passing the VNC server port and password, it does work.
I don't know if this is bug affects other non-multiseat environments.
To post a comment you must log in.
I just tried with X -query :2, to emulate somewhat a multiseat system, and it worked fine for me.
How are you selecting ssvncviewer? ssvncviewer epoptes- client
One way to do so, is to put
VNCVIEWER=
in /etc/default/