Considering that on x11vnc 
 -> You can't maintain a key for repetition
 -> Copy/Paste often doesn't work between client/server
 -> When the connection is lost, server keep feeling connected, and you cannot 
reconnect
 -> problem of setting between qwerty and azerty during few first key hits, 
sometimes
 -> if num lock is activated on the server, then somebody must physically go 
the the server to disable it (if not you cannot use numeric pad)
 -> unable to set a more than 8 characters password, unable to set symbols like 
'$' into it
 -> no encryption
 -> a completely impossible to learn default launch line : x11vnc -forever 
-rfbport 5900 -auth guess -rfbauth /var/vnc/x11vnc.pass -o /var/vnc/x11vnc.log 
-bg -display :0
 -> crashes every few seconds
 -> I probably forgot a lot of others bugs

I propose to have x11vnc retrograded as "unstable" and, at least, removed from 
any stable repository.
It's absolutely not fair, to find such shameful buggy crap available into 
operating systems like Debian, while some really good software "not tested 
enough" still aren't available trough apt-get.

I understand this second point, because that's in order to make such situations 
like x11vnc impossible anymore : such misfiring package really decrease the 
quality of users experience with Linux operating systems and those package have 
nothing to do into a "stable" operating system.


-----------------------------------------------------
I successfully used "Vino" as replacement of x11vnc, to help those who want to 
use Vino, here is some way to succeed in it (may be not the best, you can 
probably customize - but working with lxde) 
apt install vino dconf-editor

The only way to change settings for vino is to use some kind of dconf-editor. 
Inside of dconf settings :

/org/gnome/desktop/remote-access/
 -> require-encryption : false if your Viewer doesn't connect
 -> prompt-enabled : false if your desktop doesn't make you appear the prompt, 
or if you don't want it

/org/gnome/desktop/input-sources/
 -> sources : [('xkb', 'fr')] if you want azerty

/usr/share/application/vino-server.desktop should be put into your 
/home/user/.config/autostart/ directory (it works on any desktop)
In order to get the server auto-available, you should auto-login (with 
lightdm.conf or other, depending on your desktop manager)

Still haven't successfully put a password... but I'm using local and SSH 
tunnel. At least, for the first time since several month, I have a usable VNC 
system.
For virtual/punctual screen sharing, tightvncserver is working fine and easy.

Reply via email to