After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 384833 - viewOnly must be per client, not per server
viewOnly must be per client, not per server
Status: RESOLVED WONTFIX
Product: vino
Classification: Applications
Component: Server
unspecified
Other All
: Low enhancement
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-12-11 20:38 UTC by Jonh Wendell
Modified: 2020-11-12 12:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jonh Wendell 2006-12-11 20:38:30 UTC 
I think the property viewOnly must exist in ClientInfo (or somewhere) structure, allowing have mix of full control and view only clients.

Even if 'control your desktop' is enabled on the server, the client can use '-viewOnly' flag to not send mouse and keyboard events to server.
Comment 1 Jonh Wendell 2006-12-11 22:34:25 UTC 
Actually there is a variable named viewOnly in rfb_client struct. But it is always initialized with (hard-coded) FALSE. See libvncserver/rfbserver.c:rfbNewClient()

The problem will be solved when we figure out how to get that information from incoming connection and fill this variable correctly. I guess :)
Comment 2 André Klapper 2020-11-12 12:24:31 UTC 
Vino is not under active development anymore and unmaintained.

Please use gnome-remote-desktop instead.

Closing this report as WONTFIX to reflect reality.