VNC Server for real X Displays
x11vnc allows one to remotely view and interact with real X displays (i.e. a display corresponding to a physical monitor, keyboard, and mouse) with any VNC viewer. In this way it plays the role for Unix/X11 that WinVNC plays for Windows.
For Unix, the VNC implementation includes a virtual X11 server Xvnc (usually launched via the vncserver command) that is not associated with a real display, but provides a "fake" one X11 clients (xterm, mozilla, etc.) can attach to. A remote user then connects to Xvnc via the VNC client vncviewer from anywhere on the network to view and interact with the whole virtual X11 desktop.
The VNC protocol is in most cases better suited for remote connections with low bandwidth and high latency than is the X11 protocol. Also, with no state maintained the viewing-end can crash, be rebooted, or relocated and the applications and desktop continue running. Not so with X11.
- Links to X11:RemoteDesktop / x11vnc
- Has a link diff
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:frispete:RemoteDesktop/x11vnc && cd $_
- Create Badge
Source Files (show merged sources derived from linked package)
Filename | Size | Changed |
---|---|---|
_link | 0000000128 128 Bytes |
Latest Revision
- patch license to follow spdx.org standard - merge patches from openSUSE:Factory/x11vnc - dropped stack-overflow, merged upstream - update to 0.9.13: * improved support for non-X11 touchscreen devices, such as the Qtmoko Neo Freerunner * interaction with the TSLIB touchscreen library is supported * the non-X11 input injection methods on Linux are extended to potentially handle more devices * Unix sockets and raw stdio (i.e. non-TCP/socket) connections are enabled * the SSL enabled Java VNC Viewer now handles mouse wheel events * the kdm display manager is now detected when trying not to get killed by the display manager * one can now specify the maximum number of displays that can be created in -create mode via X11VNC_CREATE_MAX_DISPLAYS * the SSL enabled Java VNC Viewer Makefile has been modified so that the jar files that are built are compatible back to Java 1.4 * in -create/-unixpw mode, the environment variable FD_USERPREFS may be set to a filename in the user's home directory that includes default username:options values (so the options do not need to be typed every time at the login prompt) * web browser viewing with the SSL Java Viewer applet via HTTPS (single port mode) has been made more reliable * the stability of the "-threads" mode is greatly improved and may provide a performance enhancement for certain usage scenarios (with either a single client or multiple clients)
Comments 0