diff options
| author | runge <runge> | 2005-04-11 20:49:38 +0000 |
|---|---|---|
| committer | runge <runge> | 2005-04-11 20:49:38 +0000 |
| commit | 7ed9e5b1d03837fc3e28578ee1f8dfd928b5ee17 (patch) | |
| tree | ea0b21167fd419bafb881140ea2a153832a85f0b /x11vnc | |
| parent | baee5e2b3a00993fee00dca9d4e560f904693a6c (diff) | |
| download | libtdevnc-7ed9e5b1d03837fc3e28578ee1f8dfd928b5ee17.tar.gz libtdevnc-7ed9e5b1d03837fc3e28578ee1f8dfd928b5ee17.zip | |
x11vnc: fix some -rawfb bugs, add setup:cmd
Diffstat (limited to 'x11vnc')
| -rw-r--r-- | x11vnc/ChangeLog | 4 | ||||
| -rw-r--r-- | x11vnc/README | 1133 | ||||
| -rwxr-xr-x | x11vnc/misc/slide.pl | 4 | ||||
| -rwxr-xr-x | x11vnc/tkx11vnc | 1 | ||||
| -rw-r--r-- | x11vnc/tkx11vnc.h | 1 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 68 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 294 |
7 files changed, 932 insertions, 573 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index f56ad71..2708c67 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,7 @@ +2005-04-11 Karl Runge <runge@karlrunge.com> + * fix -clip under -rawfb, fix offset bug under file lseeking. + * add -rawfb setup:cmd mode to initialize fb. + 2005-04-10 Karl Runge <runge@karlrunge.com> * -rawfb non X-polling (i.e. shm, mmap, lseek). * -pipeinput enable external user input processing command. diff --git a/x11vnc/README b/x11vnc/README index 391bdda..f2bffbd 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Sun Apr 10 00:24:10 EDT 2005 +x11vnc README file Date: Mon Apr 11 16:12:34 EDT 2005 The following information is taken from these URLs: @@ -997,7 +997,10 @@ make [136]Q-73: Can I use x11vnc to view my VMWare session remotely? - [137]Q-74: I am using x11vnc where my local machine has "popup/hidden + [137]Q-74: Can non-X devices (e.g. a raw framebuffer) be viewed and/or + controlled by x11vnc? + + [138]Q-75: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars @@ -1005,13 +1008,13 @@ make [Misc: Clipboard, Beeps, Thanks, etc.] - [138]Q-75: Does the Clipboard/Selection get transferred between the + [139]Q-76: Does the Clipboard/Selection get transferred between the vncviewer and the X display? - [139]Q-76: Why don't I hear the "Beeps" in my X session (e.g. when + [140]Q-77: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? - [140]Q-77: Thanks for your program and for your help! Can I make a + [141]Q-78: Thanks for your program and for your help! Can I make a donation? _________________________________________________________________ @@ -1024,7 +1027,7 @@ make For the former error, you need to specify the X display to connect to (it also needs to be on the same machine x11vnc is to run on). Set - your DISPLAY environment variable or use the [141]-display option to + your DISPLAY environment variable or use the [142]-display option to specify it. Nearly always the correct value will be ":0" For the latter error, you need to set up the X11 permissions @@ -1040,7 +1043,7 @@ make How to Solve: See the xauth(1), Xsecurity(7), and xhost(1) man pages for much info on X11 permissions. For example, you may need to set - your XAUTHORITY environment variable or use the [142]-auth option to + your XAUTHORITY environment variable or use the [143]-auth option to point to the correct cookie file (e.g. /home/joe/.Xauthority or /var/gdm/:0.Xauth), or simply be sure you run x11vnc as the correct user (i.e. the user who owns the X session you wish to view). Running @@ -1054,7 +1057,7 @@ make machine). The person could then type "xhost -localhost" after x11vnc has connected to go back to the default permissions. Also, for some situations the "-users lurk=" option may be of use (please read the - documentation on the [143]-users option). + documentation on the [144]-users option). To test out your X11 permissions from a remote shell, set DISPLAY and possibly XAUTHORITY (see your shell's man page, bash(1), tcsh(1), on @@ -1166,7 +1169,7 @@ h earlier and perhaps non-Solaris): First use the environment settings (CPPFLAGS, LDFLAGS, etc.) in the - above [144]Solaris build script to run the configure command. That + above [145]Solaris build script to run the configure command. That should succeed without failure. Then you have to hand edit the autogenerated rfb/rfbconfig.h file in the source tree, and just before the last #endif at the bottom of that file insert these workaround @@ -1192,7 +1195,7 @@ typedef unsigned int in_addr_t; on other older OS (Solaris, Linux, ...) releases. Here are some notes for similar steps that need to be done to build on - [145]SunOS 4.x + [146]SunOS 4.x Please let us know if you had to use the above workaround (and whether it worked or not). If there is enough demand we will try to push clean @@ -1202,19 +1205,19 @@ typedef unsigned int in_addr_t; Q-5: Where can I get a precompiled x11vnc binary for my Operating System? - Hopefully the [146]build steps above and [147]FAQ provide enough info + Hopefully the [147]build steps above and [148]FAQ provide enough info for a painless compile for most environments. Please report problems with the x11vnc configure, make, etc. on your system (if your system is known to compile other GNU packages successfully). There are precompiled x11vnc binaries built by other groups that are available at the following locations: - Debian: (.deb) [148]http://packages.debian.org/x11vnc + Debian: (.deb) [149]http://packages.debian.org/x11vnc - Slackware: (.tgz) [149]http://www.linuxpackages.net/ Redhat/Fedora: - (.rpm) [150]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) - [151]http://www.sunfreeware.com/ wwexptools: (.tgz) - [152]http://www.bell-labs.com/project/wwexptools/packages.html The + Slackware: (.tgz) [150]http://www.linuxpackages.net/ Redhat/Fedora: + (.rpm) [151]http://dag.wieers.com/packages/x11vnc/ Solaris: (pkg) + [152]http://www.sunfreeware.com/ wwexptools: (.tgz) + [153]http://www.bell-labs.com/project/wwexptools/packages.html The last one, wwexptools, provides a variety of Unix binaries (Linux, Solaris, HP-UX, IRIX, ...) with the intent of being compatible on a wide range of OS releases. Find x11vnc near the bottom of that page @@ -1226,13 +1229,13 @@ typedef unsigned int in_addr_t; this by looking at the x11vnc output and if it says the encoding for a client is "hextile" then likely the fast compression encodings are missing. If you want optimal performance on your OS, you should see - the [153]build notes above for where to download libz and libjpeg, and + the [154]build notes above for where to download libz and libjpeg, and then build everything with gcc. For Solaris, the http://www.sunfreeware.com/ packages are built with libz and libjpeg. If the above binaries don't work and building x11vnc on your OS fails (and all else fails!) you can try one of my motley collection of - [154]test binaries. Some may be old, some may have extra debugging + [155]test binaries. Some may be old, some may have extra debugging output, etc. One of them may work on your OS... As a general note, the x11vnc program is simple enough you don't @@ -1253,9 +1256,9 @@ typedef unsigned int in_addr_t; To obtain VNC viewers for the viewing side (Windows, Mac OS, or Unix) try here: - * [155]http://www.tightvnc.com/download.html - * [156]http://www.realvnc.com/download-free.html - * [157]http://sourceforge.net/projects/cotvnc/ + * [156]http://www.tightvnc.com/download.html + * [157]http://www.realvnc.com/download-free.html + * [158]http://sourceforge.net/projects/cotvnc/ Q-7: How can I see all of x11vnc's command line options and @@ -1263,7 +1266,7 @@ typedef unsigned int in_addr_t; Run: x11vnc -opts to list just the option names or run: x11vnc -help for long descriptions about each option. The output is listed - [158]here as well. + [159]here as well. Q-8: I don't like typing arcane command line options every time I @@ -1296,7 +1299,7 @@ display :0 GUI based on the remote-control functionality that was added. It's not particularly user-friendly, it just provides a point and click mode to set all the many x11vnc parameters and obtain help on them. See the - [159]-gui option for more info. Examples: "x11vnc ... -gui" and + [160]-gui option for more info. Examples: "x11vnc ... -gui" and "x11vnc ... -gui other:0" in the latter case the gui is displayed on other:0, not the X display x11vnc is polling. @@ -1304,11 +1307,11 @@ display :0 Q-9: Can I make x11vnc more quiet and also go into the background after starting up? - Use the [160]-q and [161]-bg options, respectively. (also: -quiet is + Use the [161]-q and [162]-bg options, respectively. (also: -quiet is an alias for -q) Note that under -bg the stderr messages will be lost unless you use - the "[162]-o logfile" option. + the "[163]-o logfile" option. Q-10: Sometimes when a VNC viewer dies abruptly, x11vnc also dies with @@ -1321,7 +1324,7 @@ display :0 Up until of Apr/2004 the above fix only works for BSD signal systems (Linux, FreeBSD, ...) For SYSV systems there is a workaround in my - [163]x11vnc.c file. It also has an [164]option -sigpipe exit to have + [164]x11vnc.c file. It also has an [165]option -sigpipe exit to have x11vnc clean up and exit upon receiving SIGPIPE. @@ -1330,7 +1333,7 @@ display :0 As of Mar/2004 in the libvncserver cvs there are a few such options. They are enabled by adding something like -Dxxxx=1 to the CPPFLAGS - environment variable before running configure (see the [165]build + environment variable before running configure (see the [166]build notes for general background). * -DX11VNC_SHARED=1 make -shared the default. * -DX11VNC_FOREVER=1 make -forever the default. @@ -1375,21 +1378,21 @@ display :0 dual-screen mode to pass the keystrokes and mouse motions to the X11 display? - Yes, for best response start up x11vnc with the "[166]-nofb" option + Yes, for best response start up x11vnc with the "[167]-nofb" option (disables framebuffer polling, and does other optimizations) on the secondary display (X11) machine. Then start up Win2VNC on the primary display (Windows) referring it to the secondary display. - This will also work X11 to X11 using [167]x2vnc, however you would + This will also work X11 to X11 using [168]x2vnc, however you would probably just want to avoid VNC and use x2x for that. For reference, here are some links to Win2VNC-like programs for multiple monitor setups: - * [168]Original Win2VNC - * [169]Enhanced Win2VNC and [170]sourceforge link - * [171]x2vnc - * [172]x2x also [173]here - * [174]zvnc (MorphOS) + * [169]Original Win2VNC + * [170]Enhanced Win2VNC and [171]sourceforge link + * [172]x2vnc + * [173]x2x also [174]here + * [175]zvnc (MorphOS) All of them will work with x11vnc (except x2x where it is not needed). @@ -1409,7 +1412,7 @@ display :0 on your display to be depth 24 TrueColor? Sun machines often have 8+24 overlay/multi-depth visuals, and you can make the default visual depth 24 TrueColor (see fbconfig(1) and Xsun(1)). 2) As of Feb/2004, in the - libvncserver CVS, x11vnc has the [175]-visual option to allow you to + libvncserver CVS, x11vnc has the [176]-visual option to allow you to force the framebuffer visual to whatever you want (this usually messes up the colors unless you are very clever). In this case, the option provides a convenient workaround for the Win2VNC bug: @@ -1424,7 +1427,7 @@ display :0 PseudoColor (i.e. only 256 distinct colors). The x11vnc colors may start out OK, but after a while they are incorrect in certain windows. - Use the [176]-flashcmap option to have x11vnc watch for changes in the + Use the [177]-flashcmap option to have x11vnc watch for changes in the colormap, and propagate those changes back to connected clients. This can be slow (since the whole screen must be updated over the network whenever the colormap changes). This flashing colormap behavior often @@ -1433,7 +1436,7 @@ display :0 example of this. Consider reconfiguring the system to 16 bpp or depth 24 TrueColor if at all possible. - Also note that in some rare cases the [177]-notruecolor option has + Also note that in some rare cases the [178]-notruecolor option has corrected colors on 8bpp displays. The red, green, and blue masks were non-zero in 8bpp PseudoColor on an obscure setup, and this option corrected the problems. @@ -1444,10 +1447,10 @@ display :0 different color depths: e.g. there are both depth 8 and 24 visuals available at the same time. - You may want to review the [178]previous question regarding 8 bpp + You may want to review the [179]previous question regarding 8 bpp PseudoColor. - On some hardware (Sun/SPARC, Sgi), the [179]-overlay option discussed + On some hardware (Sun/SPARC, Sgi), the [180]-overlay option discussed a couple paragraphs down may solve this for you (you may want to skip to it directly). @@ -1485,7 +1488,7 @@ TrueColor defdepth 24 The -overlay mode: Another option is if the system with overlay visuals is a Sun system running Solaris or Sgi running IRIX you can - use the [180]-overlay x11vnc option (Aug/2004) to have x11vnc use the + use the [181]-overlay x11vnc option (Aug/2004) to have x11vnc use the Solaris XReadScreen(3X11) function to poll the "true view" of the whole screen at depth 24 TrueColor. XReadDisplay(3X11) is used on IRIX. This is useful for Legacy applications (older versions of @@ -1507,7 +1510,7 @@ TrueColor defdepth 24 Colors still not working correctly? Run xwininfo on the application with the messed up colors to verify that the depth of its visual is different from the default visual depth (gotten from xdpyinfo). One - possible workaround in this case is to use the [181]-id option to + possible workaround in this case is to use the [182]-id option to point x11vnc at the application window itself. If the application is complicated (lots of toplevel windows and popup menus) this may not be acceptable, and may even crash x11vnc (but not the application). @@ -1515,7 +1518,7 @@ TrueColor defdepth 24 It is theoretically possible to solve this problem in general (see xwd(1) for example), but it does not seem trivial or sufficiently fast for x11vnc to be able to do so in real time. Fortunately the - [182]-overlay option works for Solaris machines with overlay visuals + [183]-overlay option works for Solaris machines with overlay visuals where most of this problem occurs. @@ -1526,13 +1529,13 @@ TrueColor defdepth 24 the desired application window. After clicking, it will print out much information, including the window id (e.g. 0x6000010). Also, the visual and depth of the window printed out is often useful in - debugging x11vnc [183]problems. + debugging x11vnc [184]problems. When using -id windowid, note that some VNC viewers will have problems rendering screens that have a width that is not a multiple of 4. Try to manually adjust the window width before starting x11vnc -id .... - Also, as of Dec/2004 libvncserver CVS you can use "[184]-id pick" to + Also, as of Dec/2004 libvncserver CVS you can use "[185]-id pick" to have x11vnc run xwininfo(1) for you and after you click the window it extracts the windowid. Besides "pick" there is also "id:root" to allow you to go back to root window when doing remote-control. @@ -1550,7 +1553,7 @@ TrueColor defdepth 24 be able to see these transient windows. If things are not working and you still want to do the single window - polling, try the [185]-sid windowid option ("shifted" windowid). + polling, try the [186]-sid windowid option ("shifted" windowid). x11vnc is known to crash under both -id and -sid, so both modes are still experimental. Please report any reproducible bugs. @@ -1603,15 +1606,15 @@ TrueColor defdepth 24 since you will be polling the X display over the network as opposed to over the local hardware. To do this, run x11vnc on a UNIX machine as close as possible network-wise (e.g. same switch) to the Xterminal - machine. Use the [186]-display option to point the display to that of + machine. Use the [187]-display option to point the display to that of the Xterminal (you'll of course need basic X11 permission to do that) - and also supply the [187]-noshm option (this enables the polling over + and also supply the [188]-noshm option (this enables the polling over the network). The response will likely be sluggish (maybe only one "frame" per second). This mode is not recommended except for "quick checks" of hard to get to X servers. Use something like -wait 150 to cut down on - the polling rate. You may also need [188]-flipbyteorder if the colors + the polling rate. You may also need [189]-flipbyteorder if the colors get messed up due to endian byte order differences. Q-20: How do I get my X permissions (MIT-MAGIC-COOKIE) correct for a @@ -1635,7 +1638,7 @@ TrueColor defdepth 24 copied to the Xterminal. If $HOME/.Xauthority is exported via NFS (this is insecure of course, but has been going on for decades), then x11vnc can simply pick it up via NFS (you may need to use the - [189]-auth option to point to the correct file). Other options include + [190]-auth option to point to the correct file). Other options include copying the auth file using scp, or something like: central-server> xauth nextract - xterm123:0 | ssh xterm123 xauth nmerge - @@ -1647,7 +1650,7 @@ TrueColor defdepth 24 details. If the display name in the cookie file needs to be changed between the - two hosts, see [190]this note on the "xauth add ..." command. + two hosts, see [191]this note on the "xauth add ..." command. A less secure option is to run something like "xhost +127.0.0.1" while sitting at the Xterminal box to allow cookie-free local access for @@ -1661,7 +1664,7 @@ TrueColor defdepth 24 occasional app more efficiently locally on the Xterminal box (e.g. realplayer). - Not recommended, but as a last resort, you could have x11vnc [191]poll + Not recommended, but as a last resort, you could have x11vnc [192]poll the Xterminal Display over the network. For this you would run a "x11vnc -noshm ..." process on the central-server (and hope the network admin doesn't get angry...) @@ -1692,17 +1695,17 @@ TrueColor defdepth 24 As of Dec/2004 in the libvncserver CVS there is a remote control feature. It can change a huge amount of things on the fly: see the - [192]-remote and [193]-query options. To shut down the running x11vnc + [193]-remote and [194]-query options. To shut down the running x11vnc server just type "x11vnc -R stop". To disconnect all clients do "x11vnc -R disconnect:all", etc. - For older versions: If the [194]-forever option has not been supplied, + For older versions: If the [195]-forever option has not been supplied, x11vnc will automatically exit after the first client disconnects. In general you will have to kill the x11vnc process This can be done via: "kill NNNNN" (where NNNNN is the x11vnc process id number found from ps(1)), or "pkill x11vnc", or "killall x11vnc" (Linux only). - If you have not put x11vnc in the background via the [195]-bg option + If you have not put x11vnc in the background via the [196]-bg option or shell & operator, then simply press Ctrl-C in the shell where x11vnc is running to stop it. Potential Gotcha: If somehow your Keypress of Ctrl-C went through x11vnc to the Xserver that then @@ -1711,14 +1714,14 @@ TrueColor defdepth 24 Tapping the stuck key (either via a new x11vnc or at the physical console) will release it from the stuck state. If the keyboard seems to be acting strangely it is often fixed by tapping Ctrl, Shift, and - Alt. Alternatively, the [196]-clear_mods option and [197]-clear_keys + Alt. Alternatively, the [197]-clear_mods option and [198]-clear_keys option can be used to release pressed keys at startup and exit. Q-22: Can I change settings in x11vnc without having to restart it? Can I remote control it? - Look at the [198]-remote (same as -R) and [199]-query (same as -Q) + Look at the [199]-remote (same as -R) and [200]-query (same as -Q) options added in the Dec/2004 libvncserver CVS. They allow nearly everything to be changed dynamically and settings to be queried. Examples: "x11vnc -R shared", "x11vnc -R forever", "x11vnc -R @@ -1730,7 +1733,7 @@ TrueColor defdepth 24 be possible. There is also a simple tcl/tk gui based on this remote control - mechanism. See the [200]-gui option for more info. + mechanism. See the [201]-gui option for more info. [Security and Permissions] @@ -1742,12 +1745,12 @@ TrueColor defdepth 24 vncpasswd(1) program from those packages. The libvncserver package also comes with a simple program: storepasswd in the examples directory. And as of Jun/2004 in the libvncserver CVS x11vnc supports - the -storepasswd "pass" "file" [201]option, which is the the same + the -storepasswd "pass" "file" [202]option, which is the the same functionality of storepasswd. Be sure to quote the "pass" if it contains shell meta characters, spaces, etc. Example: x11vnc -storepasswd 'sword*fish' $HOME/myvncpasswd - You then use the password via the x11vnc option: [202]-rfbauth + You then use the password via the x11vnc option: [203]-rfbauth $HOME/myvncpasswd Compared to vncpasswd(1) the latter two methods are a somewhat unsafe @@ -1756,7 +1759,7 @@ TrueColor defdepth 24 out for the command winding up in your shell's history file (history -c is often a way to clear it). - x11vnc also has the [203]-passwdfile and -passwd/-viewpasswd plain + x11vnc also has the [204]-passwdfile and -passwd/-viewpasswd plain text (i.e. not obscured like the -rfbauth VNC passwords) password options. @@ -1765,13 +1768,13 @@ TrueColor defdepth 24 and the other for view-only access to the display? Yes, as of May/2004 in the libvncserver CVS there is the - [204]-viewpasswd option to supply the view-only password. Note the - full-access password option [205]-passwd must be supplied at the same + [205]-viewpasswd option to supply the view-only password. Note the + full-access password option [206]-passwd must be supplied at the same time. E.g.: -passwd sword -viewpasswd fish. To avoid specifying the passwords on the command line (where they could be observed via the ps(1) command by any user) you can use the - [206]-passwdfile option to specify a file containing plain text + [207]-passwdfile option to specify a file containing plain text passwords. Presumably this file is readable only by you, and ideally it is located on the machine x11vnc is run on (to avoid being snooped on over the network). The first line of this file is the full-access @@ -1779,7 +1782,7 @@ TrueColor defdepth 24 it is taken as the view-only password. (use "__EMPTY__" to supply an empty one). - View-only passwords currently do not work for the [207]-rfbauth + View-only passwords currently do not work for the [208]-rfbauth password option (standard VNC password storing mechanism). FWIW, note that although the output (usually placed in $HOME/.vnc/passwd) by the vncpasswd or storepasswd programs (or from x11vnc -storepasswd) looks @@ -1793,7 +1796,7 @@ TrueColor defdepth 24 some users just be able to move the mouse, but not click or type anything? - As of Feb/2005, the [208]-input option allows you to do this. "K", + As of Feb/2005, the [209]-input option allows you to do this. "K", "M", and "B" stand for Keystroke, Mouse-motion, and Button-clicks, respectively. The setting: "-input M" makes attached viewers only able to move the mouse. "-input KMB,M" lets normal clients do everything @@ -1809,15 +1812,15 @@ TrueColor defdepth 24 These defaults are simple safety measures to avoid someone unknowingly leaving his X11 desktop exposed (to the internet, say) for long - periods of time. Use the [209]-forever option (aka -many) to have + periods of time. Use the [210]-forever option (aka -many) to have x11vnc wait for more connections after the first client disconnects. - Use the [210]-shared option to have x11vnc allow multiple clients to + Use the [211]-shared option to have x11vnc allow multiple clients to connect simultaneously. - Recommended additional safety measures include using ssh ([211]see + Recommended additional safety measures include using ssh ([212]see above), stunnel, or a VPN to authenticate and encrypt the viewer - connections or to at least use the -rfbauth passwd-file [212]option to - use VNC password protection (or [213]-passwdfile) It is up to you to + connections or to at least use the -rfbauth passwd-file [213]option to + use VNC password protection (or [214]-passwdfile) It is up to you to apply these security measures, they will not be done for you automatically. @@ -1825,7 +1828,7 @@ TrueColor defdepth 24 Q-27: Can I limit which machines incoming VNC clients can connect from? - Yes, look at the [214]-allow and [215]-localhost options to limit + Yes, look at the [215]-allow and [216]-localhost options to limit connections by hostname or IP address. E.g. x11vnc -allow 192.168.0.1,192.168.0.2 @@ -1837,7 +1840,7 @@ TrueColor defdepth 24 Note that -localhost is the same as "-allow 127.0.0.1" For more control, build libvncserver with libwrap support - [216](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) + [217](tcp_wrappers) and then use /etc/hosts.allow See hosts_access(5) for complete details. @@ -1857,7 +1860,7 @@ TrueColor defdepth 24 is "vnc", e.g.: vnc: 192.168.100.3 .example.com - Note that if you run x11vnc out of [217]inetd you do not need to build + Note that if you run x11vnc out of [218]inetd you do not need to build x11vnc with libwrap support because the /usr/sbin/tcpd reference in /etc/inetd.conf handles the tcp_wrappers stuff. @@ -1866,16 +1869,16 @@ TrueColor defdepth 24 internal LAN) rather than having it listen on all network interfaces and relying on -allow to filter unwanted connections out? - As of Mar/2005 in the libvncserver CVS, there is the "[218]-listen + As of Mar/2005 in the libvncserver CVS, there is the "[219]-listen ipaddr" option that enables this. For ipaddr either supply the desired network interface's IP address (or use a hostname that resolves to it) or use the string "localhost". For additional filtering simultaneously - use the "[219]-allow host1,..." option to allow only specific hosts + use the "[220]-allow host1,..." option to allow only specific hosts in. This option is useful if you want insure that no one can even begin a dialog with x11vnc from untrusted network interfaces (e.g. ppp0). The - option [220]-localhost now implies "-listen localhost" since that is + option [221]-localhost now implies "-listen localhost" since that is what most people expect it to do. @@ -1883,24 +1886,24 @@ TrueColor defdepth 24 interface, how I can occasionally allow in a non-localhost via the allowonce remote control command? - To do this specify "[221]-allow localhost". Unlike [222]-localhost + To do this specify "[222]-allow localhost". Unlike [223]-localhost this will leave x11vnc listening on all interfaces (but of course only allowing in local connections, e.g. ssh redirs). Then you can later run "x11vnc -R allowonce:somehost" or use to gui to permit a one-shot connection from a remote host. Note that if you do a lot of changing of the listening interface - ([223]-listen option) via remote control or gui, you may need to also - manually adjust the [224]-allow list if you unexpectedly get into a + ([224]-listen option) via remote control or gui, you may need to also + manually adjust the [225]-allow list if you unexpectedly get into a state where the allow list cannot match any hosts that would be coming - in on the listening interface. If you just toggle [225]-localhost on + in on the listening interface. If you just toggle [226]-localhost on and off x11vnc should see to it that you never get into such a state. Q-31: How can I tunnel my connection to x11vnc via an encrypted SSH channel between two Unix machines? - See the description earlier on this page on [226]how to tunnel VNC via + See the description earlier on this page on [227]how to tunnel VNC via SSH from Unix to Unix. A number of ways are described along with some issues you may encounter. @@ -1911,7 +1914,7 @@ TrueColor defdepth 24 Q-32: How can I tunnel my connection to x11vnc via an encrypted SSH channel from Windows using an SSH client like Putty? - [227]Above we described how to tunnel VNC via SSH from Unix to Unix, + [228]Above we described how to tunnel VNC via SSH from Unix to Unix, you may want to review it. To do this from Windows using Putty it would go something like this: * In the Putty dialog window under 'Session' enter the hostname or @@ -1934,8 +1937,8 @@ TrueColor defdepth 24 process in a BAT file including launching the VNC viewer by using the plink Putty utility. Send us the script if you get that working. - For extra protection feel free to run x11vnc with the [228]-localhost - and [229]-rfbauth/[230]-passwdfile options. + For extra protection feel free to run x11vnc with the [229]-localhost + and [230]-rfbauth/[231]-passwdfile options. If the machine you SSH into via Putty is not the same machine with the X display you wish to view (e.g. your company provides incoming SSH @@ -1944,9 +1947,9 @@ TrueColor defdepth 24 you'll need to do a second login (ssh or rsh) to the workstation machine 'otherhost' and then start up x11vnc on it. - As discussed [231]above another option is to first start the VNC + As discussed [232]above another option is to first start the VNC viewer in "listen" mode, and then launch x11vnc with the - "[232]-connect localhost" option to establish the reverse connection. + "[233]-connect localhost" option to establish the reverse connection. In this case a Remote port redirection (not Local) is needed for port 5500 instead of 5900 (i.e. 'Source port: 5500' and 'Destination: localhost:5500' for a Remote connection). @@ -1957,7 +1960,7 @@ TrueColor defdepth 24 some clients view-only? How about running an arbitrary program to make the decisions? - Yes, look at the "[233]-accept command" option, it allows you to + Yes, look at the "[234]-accept command" option, it allows you to specify an external command that is run for each new client. (use quotes around the command if it contains spaces, etc.). If the external command returns 0 the client is accepted, otherwise the @@ -1976,7 +1979,7 @@ TrueColor defdepth 24 own simple popup window. To accept the client press "y" or click mouse on the "Yes" button. To reject the client press "n" or click mouse on the "No" button. To accept the client View-only, press "v" or click - mouse on the "View" button. If the [234]-viewonly option has been + mouse on the "View" button. If the [235]-viewonly option has been supplied, the "View" action will not be present: the whole display is view only in that case. @@ -1992,7 +1995,7 @@ TrueColor defdepth 24 program to prompt the user whether the client should be accepted or not. This requires that you have xmessage installed and available via PATH. In case it is not already on your system, the xmessage program - is available at [235]ftp://ftp.x.org/ + is available at [236]ftp://ftp.x.org/ To include view-only decisions for the external commands, prefix the command something like this: "yes:0,no:*,view:3 mycommand ..." This @@ -2031,7 +2034,7 @@ elif [ $rc = 4 ]; then fi exit 1 - Stefan Radman has written a nice dtksh script [236]dtVncPopup for use + Stefan Radman has written a nice dtksh script [237]dtVncPopup for use in CDE environments to do the same sort of thing. Information on how to use it is found at the top of the file. He encourages you to provide feedback to him to help improve the script. @@ -2040,7 +2043,7 @@ exit 1 popup is being run, so attached clients will not receive screen updates, etc during this period. - To run a command when a client disconnects, use the "[237]-gone + To run a command when a client disconnects, use the "[238]-gone command" option. This is for the user's convenience only: the return code of the command is not interpreted by x11vnc. The same environment variables are set as in "-accept command" (except that RFB_MODE will @@ -2055,13 +2058,13 @@ exit 1 such support. One approximate method involves starting x11vnc with the - [238]-localhost option. This basically requires the viewer user to log + [239]-localhost option. This basically requires the viewer user to log into the workstation where x11vnc is running via their Unix username and password, and then somehow set up a port redirection of his vncviewer connection to make it appear to emanate from the local machine. As discussed above, ssh is useful for this: ssh -l username -L 5900:localhost:5900 hostname ... See the ssh wrapper scripts - mentioned [239]elsewhere on this page. Of course a malicious user + mentioned [240]elsewhere on this page. Of course a malicious user could allow other users to get in through his channel, but that is a problem with every method. Another thing to watch out for is a malicious user on the viewer side (where ssh is running) trying to @@ -2070,7 +2073,7 @@ exit 1 Regarding limiting the set of Unix usernames who can connect, the traditional way would be to further require a VNC password to supplied (-rfbauth, -passwd, etc). A scheme that avoids a second password - involves using the [240]-accept option that runs a program to examine + involves using the [241]-accept option that runs a program to examine the connection information to determine which user is connecting from the local machine. For example, the program could use the ident service on the local machine (normally ident should not be trusted @@ -2103,7 +2106,7 @@ exit 1 # reject it display manager like gdm(1). Can I have x11vnc later switch to a different user? - As of Feb/2005 x11vnc has the [241]-users option that allows things + As of Feb/2005 x11vnc has the [242]-users option that allows things like this. Please read the documentation on it (in the x11vnc -help output) carefully for features and caveats. It's use can often decrease security unless care is taken. A nice use of it is "-users @@ -2124,7 +2127,7 @@ exit 1 # reject it In any event, as of Jun/2004 there is an experimental utility to make it more difficult for nosey people to see your x11vnc activities. The - source for it is [242]blockdpy.c The idea behind it is simple (but + source for it is [243]blockdpy.c The idea behind it is simple (but obviously not bulletproof): when a VNC client attaches to x11vnc put the display monitor in the DPMS "off" state, if the DPMS state ever changes immediately start up the screen-lock program. The x11vnc user @@ -2140,8 +2143,8 @@ exit 1 # reject it bulletproof. A really robust solution would likely require X server and perhaps even video hardware support. - The blockdpy utility is launched by the [243]-accept option and told - to exit via the [244]-gone option (the vnc client user should + The blockdpy utility is launched by the [244]-accept option and told + to exit via the [245]-gone option (the vnc client user should obviously re-lock the screen before disconnecting!). Instructions can be found in the source code for the utility at the above link. @@ -2149,7 +2152,7 @@ exit 1 # reject it Q-37: Can I have x11vnc automatically lock the screen when I disconnect the VNC viewer? - Yes, a user mentions he uses the [245]-gone option under CDE to run a + Yes, a user mentions he uses the [246]-gone option under CDE to run a screen lock program: x11vnc -display :0 -forever -gone 'dtaction LockDisplay' @@ -2172,11 +2175,11 @@ exit 1 # reject it permissions to connect to the X display. Here are some ideas: - * Use the description under "Continuously" in the [246]FAQ on x11vnc + * Use the description under "Continuously" in the [247]FAQ on x11vnc and Display Managers - * Use the description in the [247]FAQ on x11vnc and inetd(1) + * Use the description in the [248]FAQ on x11vnc and inetd(1) * Start x11vnc from your $HOME/.xsession (or $HOME/.xinitrc) - * Although less reliable, see the [248]x11vnc_loop rc.local hack + * Although less reliable, see the [249]x11vnc_loop rc.local hack below. The display manager scheme will not be specific to which user has the @@ -2207,7 +2210,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg while running x11vnc as root, e.g. for the gnome display manager, gdm: x11vnc -auth /var/gdm/:0.Xauth -display :0 - (the [249]-auth option sets the XAUTHORITY variable for you). + (the [250]-auth option sets the XAUTHORITY variable for you). There will be a similar thing for xdm using however a different auth directory path (perhaps something like @@ -2232,7 +2235,7 @@ x11vnc -logfile $HOME/.x11vnc.log -rfbauth $HOME/.vnc/passwd -forever -bg auth file should be in /var/dt), you'll also need to add something like Dtlogin*grabServer:False to the Xconfig file (/etc/dt/config/Xconfig or /usr/dt/config/Xconfig on Solaris, see - [250]the example at the end of this FAQ). Then restart dtlogin, e.g.: + [251]the example at the end of this FAQ). Then restart dtlogin, e.g.: /etc/init.d/dtlogin stop; /etc/init.d/dtlogin start or reboot. Continuously. Have x11vnc reattach each time the X server is @@ -2286,7 +2289,7 @@ rever -bg Then restart: /usr/sbin/gdm-restart (or reboot). The KillInitClients=false setting is important: without it x11vnc will be - killed immediately after the user logs in. Here are [251]full details + killed immediately after the user logs in. Here are [252]full details on how to configure gdm _________________________________________________________________ @@ -2328,13 +2331,13 @@ rever -bg If you do not want to deal with any display manager startup scripts, here is a kludgey script that can be run manually or out of a boot - file like rc.local: [252]x11vnc_loop It will need some local + file like rc.local: [253]x11vnc_loop It will need some local customization before running. Because the XAUTHORITY auth file must be guessed by this script, use of the display manager script method described above is greatly preferred. If the machine is a traditional Xterminal you may want to read - [253]this FAQ. + [254]this FAQ. Q-40: Can I run x11vnc out of inetd(1)? How about xinetd(1)? @@ -2344,7 +2347,7 @@ rever -bg 5900 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/x11vnc_sh - where the shell script /usr/local/bin/x11vnc_sh uses the [254]-inetd + where the shell script /usr/local/bin/x11vnc_sh uses the [255]-inetd option and looks something like (you'll need to customize to your settings). #!/bin/sh @@ -2356,13 +2359,13 @@ rever -bg (otherwise the standard error also goes to the VNC vncviewer, and that confuses it greatly). If you do not use a wrapper script as above but rather call x11vnc directly in /etc/inetd.conf and do not redirect - stderr to a file, then you must specify the -q (aka [255]-quiet) + stderr to a file, then you must specify the -q (aka [256]-quiet) option: "/usr/local/bin/x11vnc -q -inetd ..." or use "-o logfile" to collect the output in a file. The wrapper script with redirection to a log file is the recommended method because the errors and warnings printed out are very useful in troubleshooting problems. - Note also the need to set XAUTHORITY via [256]-auth to point to the + Note also the need to set XAUTHORITY via [257]-auth to point to the MIT-COOKIE auth file to get permission to connect to the X display (setting and exporting the XAUTHORITY variable accomplishes the same thing). See the x11vnc_loop file in the previous question for more @@ -2410,7 +2413,7 @@ service x11vncservice web browser? To have x11vnc serve up a Java VNC viewer applet to any web browsers - that connect to it, run x11vnc with this [257]option: + that connect to it, run x11vnc with this [258]option: -httpdir /path/to/the/java/classes/dir (this directory will contain the files index.vnc and, for example, @@ -2440,7 +2443,7 @@ service x11vncservice As of Mar/2004 in the libvncserver CVS x11vnc supports reverse connections. On Unix one starts the VNC viewer in listen mode: vncviewer -listen (see your documentation for Windows, etc), and then - starts up x11vnc with the [258]-connect option. To connect immediately + starts up x11vnc with the [259]-connect option. To connect immediately at x11vnc startup time use the "-connect host:port" option (use commas for a list of hosts to connect to). The ":port" is optional (default is 5500). If a file is specified instead: -connect /path/to/some/file @@ -2448,7 +2451,7 @@ service x11vncservice hosts to connect to. To use the vncconnect(1) program (from the core VNC package at - www.realvnc.com) specify the [259]-vncconnect option to x11vnc (Note: + www.realvnc.com) specify the [260]-vncconnect option to x11vnc (Note: as of Dec/2004 -vncconnect is now the default). vncconnect(1) must be pointed to the same X11 DISPLAY as x11vnc (since it uses X properties to communicate with x11vnc). If you do not have or do not want to get @@ -2490,7 +2493,7 @@ xprop -root -f VNC_CONNECT 8s -set VNC_CONNECT "$1" There are some annoyances WRT Xvfb though. The default keyboard mapping seems to be very poor. One should run x11vnc with - [260]-add_keysyms option to have keysyms added automatically. Also, to + [261]-add_keysyms option to have keysyms added automatically. Also, to add the Shift_R and Control_R modifiers something like this is needed: #!/bin/sh xmodmap -e "keycode any = Shift_R" @@ -2517,7 +2520,7 @@ xmodmap -e "add Control = Control_L Control_R" An X server can be started on the headless machine (sometimes this requires configuring the X server to not fail if it cannot detect a keyboard or mouse, see the next paragraph). Then you can export that X - display via x11vnc (e.g. see [261]this FAQ) and access it from + display via x11vnc (e.g. see [262]this FAQ) and access it from anywhere on the network via a VNC viewer. Some tips on getting X servers to start on machines without keyboard @@ -2560,7 +2563,7 @@ xmodmap -e "add Control = Control_L Control_R" 19/03/2004 10:10:58 error creating tile-row shm for len=4 19/03/2004 10:10:58 reverting to single_copytile mode - Here is a shell script [262]shm_clear to list and prompt for removal + Here is a shell script [263]shm_clear to list and prompt for removal of your unattached shm segments (attached ones are skipped). I use it while debugging x11vnc (I use "shm_clear -y" to assume "yes" for each prompt). If x11vnc is regularly not cleaning up its shm segments, @@ -2594,35 +2597,35 @@ ied) in /etc/system. See the next paragraph for more workarounds. To minimize the number of shm segments used by x11vnc try using the - [263]-onetile option (corresponds to only 3 shm segments used, and + [264]-onetile option (corresponds to only 3 shm segments used, and adding -fs 1.0 knocks it down to 2). If you are having much trouble with shm segments, consider disabling shm completely via the - [264]-noshm option. Performance will be somewhat degraded but when + [265]-noshm option. Performance will be somewhat degraded but when done over local machine sockets it should be acceptable (see an - [265]earlier question discussing -noshm). + [266]earlier question discussing -noshm). Q-46: How can I make x11vnc use less system resources? - The [266]-nap and "[267]-wait n" (where n is the sleep between polls + The [267]-nap and "[268]-wait n" (where n is the sleep between polls in milliseconds, the default is 30 or so) option are good places to start. Reducing the X server bits per pixel depth (e.g. to 16bpp or even 8bpp) will further decrease memory I/O and network I/O. Using the - [268]-onetile option will use less memory and use fewer shared memory - slots (add [269]-fs 1.0 for one less slot). + [269]-onetile option will use less memory and use fewer shared memory + slots (add [270]-fs 1.0 for one less slot). Q-47: How can I make x11vnc use MORE system resources? - You can try [270]-threads and dial down the wait time (e.g. -wait 1) - and possibly dial down [271]-defer as well. Note that if you try to + You can try [271]-threads and dial down the wait time (e.g. -wait 1) + and possibly dial down [272]-defer as well. Note that if you try to increase the "frame rate" too much you can bog down the server end with the extra work it needs to do compressing the framebuffer data, etc. That said, it is possible to "stream" video via x11vnc if the video window is small enough. E.g. a 256x192 xawtv TV capture window (using - the x11vnc [272]-id option) can be streamed over a LAN or wireless at + the x11vnc [273]-id option) can be streamed over a LAN or wireless at a reasonable frame rate. @@ -2638,7 +2641,7 @@ ied) * Use a smaller desktop size (e.g. 1024x768 instead of 1280x1024) * Make sure the desktop background is a solid color (the background is resent every time it is re-exposed). Consider using the - [273]-solid [color] option. + [274]-solid [color] option. * Configure your window manager or desktop "theme" to not use fancy images, shading, and gradients for the window decorations, etc. Disable Opaque moves, resizes, and animations. @@ -2654,7 +2657,7 @@ ied) worth it, but could be of use in some situations. VNC viewer parameters: - * Use a [274]TightVNC enabled viewer! + * Use a [275]TightVNC enabled viewer! * Make sure the tight encoding is being used (look at vncviewer and x11vnc outputs) * Request 8 bits per pixel using -bgr233 (up to 4X speedup over @@ -2672,19 +2675,19 @@ ied) vncviewer to be very slow) x11vnc parameters: - * Try using [275]-nodragging (no screen updates when dragging mouse, + * Try using [276]-nodragging (no screen updates when dragging mouse, but sometimes you miss visual feedback) - * Try the [276]-progressive pixelheight mode with the block + * Try the [277]-progressive pixelheight mode with the block pixelheight 100 or so (delays sending vertical blocks since they may change while viewer is receiving earlier ones) - * Set [277]-fs 1.0 (disables fullscreen updates) - * Try increasing [278]-wait or [279]-defer (reduces the maximum + * Set [278]-fs 1.0 (disables fullscreen updates) + * Try increasing [279]-wait or [280]-defer (reduces the maximum "frame rate", but won't help much for large screen changes) - * If you just want to watch one (simple) window use [280]-id (cuts + * If you just want to watch one (simple) window use [281]-id (cuts down extraneous polling and updates, but can be buggy or insufficient) - * Set [281]-nosel (disables all clipboard selection exchange) - * Use [282]-nocursor and [283]-nocursorpos (repainting the remote + * Set [282]-nosel (disables all clipboard selection exchange) + * Use [283]-nocursor and [284]-nocursorpos (repainting the remote cursor position and shape takes resources and round trips) @@ -2696,19 +2699,19 @@ ied) tree. The default should now be much better than before and dragging small windows around should no longer be a huge pain. If for some reason these changes make matters worse, you can go back to the old - way via the "[284]-pointer_mode 1" option. + way via the "[285]-pointer_mode 1" option. - Also added was the [285]-nodragging option that disables all screen + Also added was the [286]-nodragging option that disables all screen updates while dragging with the mouse (i.e. mouse motion with a button held down). This gives the snappiest response, but might be undesired in some circumstances when you want to see the visual feedback while dragging (e.g. menu traversal or text selection). - As of Dec/2004 in the libvncserver CVS the [286]-pointer_mode n option + As of Dec/2004 in the libvncserver CVS the [287]-pointer_mode n option was introduced. n=1 is the original mose, n=2 and improvement, etc.. See the -pointer_mode n help for more info. - Also, in some circumstances the [287]-threads option can improve + Also, in some circumstances the [288]-threads option can improve response considerably. Be forewarned that if more than one vncviewer is connected at the same time then libvncserver may not be thread safe (try to get the viewers to use different VNC encodings, e.g. tight and @@ -2749,13 +2752,13 @@ ied) DAMAGE rectangles to contain real damage. The larger rectangles are only used as hints to direct the traditional scanline polling (i.e. if a scanline doesn't intersect a recent DAMAGE rectangle, the scan is - skipped). You can use the "[288]-xd_area A" option to adjust the size + skipped). You can use the "[289]-xd_area A" option to adjust the size of the trusted DAMAGE rectangles. The default is 20000 pixels (e.g. a 140x140 square, etc). Use "-xd_area 0" to disable the cutoff and trust all DAMAGE rectangles. - The option "[289]-xd_mem f" may also be of use in tuning the - algorithm. To disable using DAMAGE entirely use "[290]-noxdamage". + The option "[290]-xd_mem f" may also be of use in tuning the + algorithm. To disable using DAMAGE entirely use "[291]-noxdamage". [Mouse Cursor Shapes] @@ -2773,16 +2776,16 @@ ied) this is because the cursor shape is often downloaded to the graphics hardware (video card), but I could be mistaken. - A simple kludge is provided by the "[291]-cursor X" option that + A simple kludge is provided by the "[292]-cursor X" option that changes the cursor when the mouse is on the root background (or any window has the same cursor as the root background). Note that desktops like GNOME or KDE often cover up the root background, so this won't - work for those cases. Also see the "[292]-cursor some" option for + work for those cases. Also see the "[293]-cursor some" option for additional kludges. Note that as of Aug/2004 in the libvncserver CVS, on Solaris using the SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse - cursor when the [293]-overlay option is supplied. See [294]this FAQ + cursor when the [294]-overlay option is supplied. See [295]this FAQ for more info. Also as of Dec/2004 in the libvncserver CVS XFIXES X extension support @@ -2790,7 +2793,7 @@ ied) XFIXES fixes the problem of the cursor-shape being write-only: x11vnc can now query the X server for the current shape and send it back to the connected viewers. XFIXES is available on recent Linux Xorg based - distros and [295]Solaris 10. + distros and [296]Solaris 10. The only XFIXES issue is the handling of alpha channel transparency in cursors. If a cursor has any translucency then in general it must be @@ -2798,7 +2801,7 @@ ied) cursor transparency can also handled exactly: when the VNC Viewer requires the cursor shape be drawn into the VNC framebuffer or if you apply a patch to your VNC Viewer to extract hidden alpha channel data - under 32bpp. [296]Details can be found here. + under 32bpp. [297]Details can be found here. Q-52: When using XFIXES cursorshape mode, some of the cursors look @@ -2831,17 +2834,17 @@ ied) for most cursor themes and you don't have to worry about it. In case it still looks bad for your cursor theme, there are (of - course!) some tunable parameters. The "[297]-alphacut n" option lets + course!) some tunable parameters. The "[298]-alphacut n" option lets you set the threshold "n" (between 0 and 255): cursor pixels with alpha values below n will be considered completely transparent while values equal to or above n will be completely opaque. The default is - 240. The "[298]-alphafrac f" option tries to correct individual + 240. The "[299]-alphafrac f" option tries to correct individual cursors that did not fare well with the default -alphacut value: if a cursor has less than fraction f (between 0.0 and 1.0) of its pixels selected by the default -alphacut, the threshold is lowered until f of its pixels are selected. The default fraction is 0.33. - Finally, there is an option [299]-alpharemove that is useful for + Finally, there is an option [300]-alpharemove that is useful for themes where many cursors are light colored (e.g. "whiteglass"). XFIXES returns the cursor data with the RGB values pre-multiplied by the alpha value. If the white cursors look too grey, specify @@ -2857,11 +2860,11 @@ ied) send the alpha channel data to libvncserver. However, this data will only be used for VNC clients that do not support the CursorShapeUpdates VNC extension (or have disabled it). It can be - disabled for all clients with the [300]-nocursorshape x11vnc option. + disabled for all clients with the [301]-nocursorshape x11vnc option. In this case the cursor is drawn, correctly blended with the background, into the VNC framebuffer before being sent out to the client. So the alpha blending is done on the x11vnc side. Use the - [301]-noalphablend option to disable this behavior (always approximate + [302]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). The CursorShapeUpdates VNC extension complicates matters because the @@ -2889,9 +2892,9 @@ ied) Q-54: Why does the mouse arrow just stay in one corner in my vncviewer, whereas my cursor (that does move) is just a dot? - This default takes advantage of a [302]tightvnc extension + This default takes advantage of a [303]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [303]-nocursor + the local VNC viewer. You may disable it with the [304]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 in the libvncserver CVS this should be fixed: the @@ -2905,18 +2908,18 @@ ied) clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [304]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [305]-cursorpos option when starting x11vnc. A VNC viewer must support the Cursor Positions Updates for the user to see the mouse motions (the TightVNC viewers support this). As of Aug/2004 in the - libvncserver CVS -cursorpos is the default. See also [305]-nocursorpos - and [306]-nocursorshape. + libvncserver CVS -cursorpos is the default. See also [306]-nocursorpos + and [307]-nocursorshape. Q-56: Is it possible to swap the mouse buttons (e.g. left-handed operation), or arbitrarily remap them? How about mapping button clicks to keystrokes, e.g. to partially emulate Mouse wheel scrolling? - You can remap the mouse buttons via something like: [307]-buttonmap + You can remap the mouse buttons via something like: [308]-buttonmap 13-31 (or perhaps 12-21). Also, note that xmodmap(1) lets you directly adjust the X server's button mappings, but in some circumstances it might be more desirable to have x11vnc do it. @@ -2924,7 +2927,7 @@ ied) One user had an X server with only one mouse button(!) and was able to map all of the VNC client mouse buttons to it via: -buttonmap 123-111. - Note that the [308]-debug_pointer option prints out much info for + Note that the [309]-debug_pointer option prints out much info for every mouse/pointer event and is handy in solving problems. To map mouse button clicks to keystrokes you can use the alternate @@ -2946,7 +2949,7 @@ ied) Exactly what keystroke "scrolling" events they should be bound to depends on one's taste. If this method is too approximate, one could - consider not using [309]-buttonmap but rather configuring the X server + consider not using [310]-buttonmap but rather configuring the X server to think it has a mouse with 5 buttons even though the physical mouse does not. @@ -2967,7 +2970,7 @@ ied) Q-57: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [310]-modtweak should be of some use for this. It is a mode + The option [311]-modtweak should be of some use for this. It is a mode that monitors the state of the Shift and AltGr Modifiers and tries to deduce the correct keycode to send, possibly by sending fake modifier key presses and releases in addition to the actual keystroke. @@ -2976,17 +2979,17 @@ ied) default (use -nomodtweak to get the old behavior). This was done because it was noticed on newer XFree86 setups even on bland "us" keyboards like "pc104 us" XFree86 included a "ghost" key with both "<" - and ">" it. This key does not exist on the keyboard (see [311]this FAQ + and ">" it. This key does not exist on the keyboard (see [312]this FAQ for more info). Without -modtweak there was then an ambiguity in the reverse map keysym => keycode, making it so the "<" symbol could not be typed. - Also see the [312]FAQ about the -xkb option for a more powerful method + Also see the [313]FAQ about the -xkb option for a more powerful method of modifier tweaking for use on X servers with the XKEYBOARD extension. When trying to resolve keyboard mapping problems, note that the - [313]-debug_keyboard option prints out much info for every keystroke + [314]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. @@ -3037,17 +3040,17 @@ ied) -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([314]-modtweak) is a mode that monitors the + settings. The former ([315]-modtweak) is a mode that monitors the state of the Shift and AltGr modifiers and tries to deduce the correct keycode sequence to send. Since Jul/2004 -modtweak is now the default. - The latter ([315]-remap less-comma) is an immediate remapping of the + The latter ([316]-remap less-comma) is an immediate remapping of the keysym less to the keysym comma when it comes in from a client (so when Shift is down the comma press will yield "<"). - See also the [316]FAQ about the -xkb option as a possible workaround + See also the [317]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [317]-debug_keyboard option prints out much info for + Note that the [318]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. @@ -3072,7 +3075,7 @@ ied) In both cases no AltGr is sent to the VNC server, but we know AltGr is needed on the physical international keyboard to type a "@". - This all worked fine with x11vnc running with the [318]-modtweak + This all worked fine with x11vnc running with the [319]-modtweak option (it figures out how to adjust the Modifier keys (Shift or AltGr) to get the "@"). However it fails under recent versions of XFree86 (and the X.org fork). These run the XKEYBOARD extension by @@ -3090,7 +3093,7 @@ ied) * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [319]-xkb option seems to fix all of the missing keys: "@", "<", + The [320]-xkb option seems to fix all of the missing keys: "@", "<", ">", etc.: it is recommended that you try it if you have this sort of problem. Let us know if there are any remaining problems (see the next paragraph for some known problems). If you specify the -debug_keyboard @@ -3108,7 +3111,7 @@ ied) was attached to keycode 93 (no physical key generates this keycode) while ISO_Level3_Shift was attached to keycode 113. The keycode skipping option was used to disable the ghost key: - [320]-skip_keycodes 93 + [321]-skip_keycodes 93 * In implementing -xkb we noticed that some characters were still not getting through, e.g. "~" and "^". This is not really an XKEYBOARD problem. What was happening was the VNC viewer was @@ -3125,14 +3128,14 @@ ied) What to do? In general the VNC protocol has not really solved this problem: what should be done if the VNC viewer sends a keysym not recognized by the VNC server side? Workarounds can possibly be - created using the [321]-remap x11vnc option: + created using the [322]-remap x11vnc option: -remap asciitilde-dead_tilde,asciicircum-dead_circumflex etc. Use -remap filename if the list is long. Please send us your workarounds for this problem on your keyboard. Perhaps we can have x11vnc adjust automatically at some point. Also see the - [322]-add_keysyms option in the next paragraph. - * To complement the above workaround using the [323]-remap, an - option [324]-add_keysyms was added. This option instructs x11vnc + [323]-add_keysyms option in the next paragraph. + * To complement the above workaround using the [324]-remap, an + option [325]-add_keysyms was added. This option instructs x11vnc to bind any unknown Keysyms coming in from VNC viewers to unused Keycodes in the X server. This modifies the global state of the X server. When x11vnc exits it removes the extra keymappings it @@ -3149,7 +3152,7 @@ ied) Short answer: disable key autorepeating by running the command "xset r off" on the Xserver where x11vnc is run (restore via "xset r on") or - use the new (Jul/2004) [325]-norepeat x11vnc option. You will still + use the new (Jul/2004) [326]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. Update: as of Dec/2004 -norepeat is now the default. Use -repeat to disable it. @@ -3171,7 +3174,7 @@ ied) off", does the problem go away? The workaround is to manually apply "xset r off" and "xset r on" as - needed, or to use the [326]-norepeat (which has since Dec/2004 been + needed, or to use the [327]-norepeat (which has since Dec/2004 been made the default). Note that with X server autorepeat turned off the VNC viewer side of the connection will (nearly always) do its own autorepeating so there is no big loss here, unless someone is also @@ -3182,7 +3185,7 @@ ied) keystrokes!! Are you using x11vnc to log in to an X session? (as described in - [327]this FAQ) If so, x11vnc is starting before your session and it + [328]this FAQ) If so, x11vnc is starting before your session and it disables autorepeat when you connect, but then after you log in your session startup (GNOME, KDE, ...) could be resetting the autorepeat to be on. Or it could be something inside your desktop trying to be @@ -3206,7 +3209,7 @@ ied) machine where I run the VNC viewer does not. Is there a way I can map a local unused key to send an AltGr? How about a Compose key as well? - Something like "[328]-remap Super_R-Mode_switch" x11vnc option may + Something like "[329]-remap Super_R-Mode_switch" x11vnc option may work. Note that Super_R is the "Right Windoze(tm) Flaggie" key; you may want to choose another. The -debug_keyboard option comes in handy in finding keysym names (so does xev(1)). @@ -3229,7 +3232,7 @@ ied) Since xmodmap(1) modifies the X server mappings you may not want to do this (because it affects local work on that machine). Something like - the [329]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [330]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones needs, and does not modify the X server environment. Note that you cannot send Alt_L in this case, maybe -remap Super_L-Meta_L would be a better choice if the Super_L key is typically unused. @@ -3240,7 +3243,7 @@ ied) This can be done directly in some X servers using AccessX and Pointer_EnableKeys, but is a bit awkward. It may be more convenient to - have x11vnc do the remapping. This can be done via the [330]-remap + have x11vnc do the remapping. This can be done via the [331]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -3248,7 +3251,7 @@ ied) a touchpad with only two buttons. It is difficult to do a middle button "paste" because (using XFree86 Emulate3Buttons) you have to click both buttons on the touch pad at the same time. This remapping: - [331]-remap Super_R-Button2 + [332]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -3277,7 +3280,7 @@ ied) There may also be scaling viewers out there (e.g. TightVNC on Windows) that automatically shrink or expand the remote framebuffer to fit the - local display. Especially for hand-held devices. See also [332]this + local display. Especially for hand-held devices. See also [333]this FAQ on x11vnc scaling. @@ -3286,7 +3289,7 @@ ied) As of Jun/2004 in the libvncserver CVS x11vnc provides basic server-side scaling. It is a global scaling of the desktop, not a - per-client setting. To enable it use the "[333]-scale fraction" + per-client setting. To enable it use the "[334]-scale fraction" option. "fraction" can either be a floating point number (e.g. -scale 0.5) or the alternative m/n fraction notation (e.g. -scale 2/3). Note that if fraction is greater than one the display is magnified. @@ -3306,7 +3309,7 @@ ied) One can also use the ":nb" with an integer scale factor (say "-scale 2:nb") to use x11vnc as a screen magnifier for vision impaired - [334]applications. Since with integer scale factors the framebuffers + [335]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -3332,12 +3335,12 @@ ied) If one desires per-client scaling for something like 1:1 from a workstation and 1:2 from a smaller device (e.g. handheld), currently the only option is to run two (or more) x11vnc processes with - different scalings listening on separate ports ([335]-rfbport option, + different scalings listening on separate ports ([336]-rfbport option, etc.). As of Mar/2005 in the libvncserver CVS x11vnc now scales the mouse cursor with the same scale factor as the screen. If you don't want - that, use the [336]"-scale_cursor frac" option to set the cursor + that, use the [337]"-scale_cursor frac" option to set the cursor scaling to a different factor (e.g. use "-scale_cursor 1" to keep the cursor at its natural unscaled size). @@ -3354,16 +3357,16 @@ ied) rectangular (e.g. 1280x1024 and 1024x768 monitors joined together), then there will be "non-existent" areas on the screen. The X server will return "garbage" image data for these areas and so they may be - distracting to the viewer. The [337]-blackout x11vnc option allows you + distracting to the viewer. The [338]-blackout x11vnc option allows you to blacken-out rectangles by specifying their WxH+X+Y geometries. If - your system has the libXinerama library, the [338]-xinerama x11vnc + your system has the libXinerama library, the [339]-xinerama x11vnc option can be used to have it automatically determine the rectangles to be blackened out. (Note on 8bpp PseudoColor displays the fill color may not be black). Some users have reported that the mouse does not behave properly for their Xinerama display: i.e. the mouse cannot be moved to all regions - of the large display. If this happens try using the [339]-xwarppointer + of the large display. If this happens try using the [340]-xwarppointer option. This instructs x11vnc to fake mouse pointer motions using the XWarpPointer function instead of the XTestFakeMotionEvent XTEST function. (This may be due to a bug in the X server for XTEST when @@ -3388,22 +3391,22 @@ ied) Note: if you are running on Solaris 8 or earlier you can easily hit up against the maximum of 6 shm segments per process (for Xsun in this case) from running multiple x11vnc processes. You should modify - /etc/system as mentioned in another [340]FAQ to increase the limit. It - is probably also a good idea to run with the [341]-onetile option in + /etc/system as mentioned in another [341]FAQ to increase the limit. It + is probably also a good idea to run with the [342]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [342]-noshm to use no shm segments. + [343]-noshm to use no shm segments. Q-69: Can x11vnc show only a portion of the display? (E.g. for a special purpose rfb application). - As of Mar/2005 in the libvncserver CVS x11vnc has the "[343]-clip + As of Mar/2005 in the libvncserver CVS x11vnc has the "[344]-clip WxH+X+Y" option to select a rectangle of width W, height H and offset (X, Y). Thus the VNC screen will be the clipped sub-region of the display and be only WxH in size. This also works to view a sub-region of a single application window if - the [344]-id or [345]-sid options are used. The offset is measured + the [345]-id or [346]-sid options are used. The offset is measured from the upper left corner of the selected window. @@ -3412,7 +3415,7 @@ ied) crash. As of Dec/2004 in the libvncserver CVS x11vnc supports XRANDR. You - enable it with the [346]-xrandr option to make x11vnc monitor XRANDR + enable it with the [347]-xrandr option to make x11vnc monitor XRANDR events and also trap X server errors if the screen change occurred in the middle of an X call like XGetImage. Once it traps the screen change it will create a new framebuffer using the new screen. If the @@ -3421,7 +3424,7 @@ ied) viewer will automatically resize. Otherwise, the new framebuffer is fit as best as possible into the original viewer size (portions of the screen may be clipped, unused, etc). For these viewers you can try the - [347]-padgeom option to make the region big enough to hold all resizes + [348]-padgeom option to make the region big enough to hold all resizes and rotations. If you specify "-xrandr newfbsize" then vnc viewers that do not @@ -3475,9 +3478,10 @@ ied) * Fullscreen mode The way VMWare does Fullscreen mode on Linux is to display the Guest - desktop in a separate Virtual Console (e.g. VC 8) (see [348]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [349]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X - server. So x11vnc cannot access it. x11vnc works fine with "Normal X + server. So x11vnc cannot access it (however, [350]see this for a + possible partial workaround). x11vnc works fine with "Normal X application window" and "Quick-Switch mode" because these use X. One user reports he left his machine with VMWare in the Fullscreen @@ -3493,13 +3497,13 @@ ied) response. One can also cut the display depth (e.g. to 16bpp) in this 2nd X session to improve video performance. This 2nd X session emulates Fullscreen mode to some degree and can be viewed via x11vnc - as long as the VMWare X session [349]is in the active VC. + as long as the VMWare X session [351]is in the active VC. Also note that with a little bit of playing with "xwininfo -all -children" output one can extract the (non-toplevel) windowid of the of the Guest desktop only when VMWare is running as a normal X application. Then one can export just the guest desktop (i.e. without - the VMWare menu buttons) by use of the [350]-id windowid option. The + the VMWare menu buttons) by use of the [352]-id windowid option. The caveats are the X session VMWare is in must be in the active VC and the window must be fully visible, so this mode is not terribly convenient, but could be useful in some circumstances (e.g. running @@ -3508,7 +3512,152 @@ ied) mouse)). - Q-74: I am using x11vnc where my local machine has "popup/hidden + Q-74: Can non-X devices (e.g. a raw framebuffer) be viewed and/or + controlled by x11vnc? + + As of Apr/2005 in the libvncserver CVS there is rudimentary support + for this. Two options were added: "-rawfb string" (to indicate the raw + framembuffer and its parameters) and "-pipeinput cmd" (to provide an + external program that will inject or otherwise process mouse and + keystroke input). + + This non-X mode for x11vnc is experimental because it is so removed in + scope from the intended usage of the tool. No attempt is made to make + all of the other options consistent with non-X framebuffer polling. So + all of the X-related options (e.g. -add_keysyms, -xkb) are just + ignored or in the worst case will cause a crash. Be careful applying + such an option via the command line or remote control. + + The format for the -rawfb string is: + <type>:<object>@<W>x<H>x<bpp>[:<R>/<G>/<B>][+<offset>] + + Some examples: + -rawfb shm:210337933@800x600x32:ff/ff00/ff0000 + + -rawfb map:/dev/fb0@1024x768x16 + + -rawfb map:/tmp/Xvfb_screen0@640x480x8+3232 + + -rawfb file:/tmp/my.pnm@250x200x24+37 + + So the type can be "shm" for shared memory objects, and "map" or + "file" for file objects. "map" uses mmap(2) to map the file into + memory and is preferred over "file" (that uses the slower lseek(2) + access method). Only use file if map isn't working. BTW, "mmap" is an + alias for "map". + + Also, if the string is of the form "setup:cmd" then cmd is run and the + first line of its output retrieved and used as the rawfb string. This + allows initializing the device, determining WxHxB, etc. + + The object will be the numerical shared memory id for the case of shm. + The idea here is some other program has created this shared memory + segment and periodically updates it with new framebuffer data. x11vnc + polls the area for changes. See shmat(2) and ipcs(8) for more info. + The ipcs command will list current shared memory segments on the + system. + + The object will be the path to the regular or character special file + for the cases of map and file. The idea here is that in the case of a + regular file some other program is writing/updating framebuffer image + data to it. In the case of a character special (e.g. /dev/fb0) it is + the kernel that is "updating" the framebuffer data. + + In all cases x11vnc needs to be told the width, height, and number of + bits per pixel (bpp) of the framebuffer. This is the @WxHxB field. For + the case of the Linux framebuffer device, /dev/fb0, the fbset(8) may + be of use (but may not always be accurate for what is currently + viewable). In general some guessing may be required, especially for + the bpp. + + Based on the bpp x11vnc will try to guess the red, green, and blue + masks (these indicate which bits correspond to each color). It if gets + it wrong you can specify them manually via the optional ":R/G/B" + field. E.g. ":0xff000/0x00ff00/0x0000ff" (this is the default for + 32bpp). + + Finally, the framebuffer may not begin at the beginning of the memory + object, so use the optional "+offset" parameter to indicate where the + framebuffer information starts. So as an example, the Xvfb virtual + framebuffer has options -shmem and -fbdir for exporting its virtual + screen to either shm or a mapped file. The format of these is XWD and + so the initial header should be skipped. BTW, since XWD is not + strictly RGB the view will only be approximate. Of course for the case + of Xvfb x11vnc can poll it much better via the [353]X API, but you get + the idea. + + By default in -rawfb mode x11vnc will actually close any X display it + happened to open. This is basically to shake out bugs (e.g it will + crash rather than mysteriously interacting with the X display). If you + want x11vnc to keep the X display open while polling the raw + framebuffer capitalize the type (i.e. "SHM:", "MAP:", or "FILE:"). + This could be convenient for keeping the remote control channel active + (it uses X properties). The "-connect /path/to/file" mechanism could + also be used for remote control to avoid the X property channel. + + + All of the above was just for viewing the raw framebuffer. That may be + enough for certain applications of this feature (e.g. suppose a video + camera mapped its framebuffer into memory). To handle the pointer and + keyboard input from the viewer users the "-pipeinput cmd" option was + added to indicate a helper program to process the user input. The + input is streamed to it and looks something like this: + Pointer 1 205 257 0 None + Pointer 1 198 253 0 None + Pointer 1 198 253 1 ButtonPress-1 + Pointer 1 198 253 0 ButtonRelease-1 + Pointer 1 198 252 0 None + Keysym 1 1 119 w KeyPress + Keysym 1 0 119 w KeyRelease + Keysym 1 1 65288 BackSpace KeyPress + Keysym 1 0 65288 BackSpace KeyRelease + Keysym 1 1 112 p KeyPress + Keysym 1 0 112 p KeyRelease + + Run "-pipeinput tee:/bin/cat" to get a description of the format. Note + that the -pipeinput option is independent of -rawfb mode and so may + have some other interesting uses. BTW, the "tee:" prefix means x11vnc + will both process the user input and pipe it to the command. The + default is to just pipe it to the -pipeinput command. + + Note the -pipeinput helper program could actually control the raw + framebuffer. In the libvncserver CVS a simple example program + x11vnc/misc/slide.pl is provided that demonstrates a simple jpeg + "slideshow" application. + + The -pipeinput program is run with these environment variables set: + X11VNC_PID, X11VNC_PROG, X11VNC_CMDLINE, X11VNC_RAWFB_STR to aid its + knowing what is up. + + Another example provided in libvncserver CVS is a script to inject + keystrokes into the Linux console (e.g. the virtual consoles: + /dev/tty1, /dev/tty2, etc) in x11vnc/misc/vcinject.pl. It is based on + the vncterm/LinuxVNC.c program also in the libvncserver CVS. So to + view and interact with VC #2 (assuming it is the [354]active VC) one + can run something like: + x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' + + This assumes your Linux framebuffer device (/dev/fb0) is properly + configured. See fbset(8) and other documentation. Try + "file:/dev/fb0@WxHxB" as a last resort. + + The above is just an example of what can be done. If you really want + to view and interact with the Linux console it is better to use the + more accurate and faster LinuxVNC program. The only advantage x11vnc + -rawfb might have is that it can presumably allow interaction with a + non-text application, e.g. one based on svgalib. For example the + [355]VMWare Fullscreen mode is actually viewable under -rawfb. But + this isn't much use until one figures out how to inject keystrokes and + mouse events. + + The -rawfb and -pipeinput features are intended to help one creatively + "get out of a jam" (say on a legacy or embedded device) where X is + absent or doesn't work properly. Feedback and bug reports are welcome. + For more control and less overhead use libvncserver in your own C + program that passes the framebuffer to libvncserver. + + + Q-75: I am using x11vnc where my local machine has "popup/hidden taskbars" (e.g. GNOME or MacOS X) and the remote display where x11vnc runs also has "popup/hidden taskbars" (e.g. GNOME). When I move the mouse to the edge of the screen where the popups happen, the taskbars @@ -3522,22 +3671,22 @@ ied) [Misc: Clipboard, Beeps, Thanks, etc.] - Q-75: Does the Clipboard/Selection get transferred between the + Q-76: Does the Clipboard/Selection get transferred between the vncviewer and the X display? As of Jan/2004 in the libvncserver CVS x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY selection (Xvnc does not seem to do this). If you don't want - the Clipboard/Selection exchanged use the [351]-nosel option. If you + the Clipboard/Selection exchanged use the [356]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [352]-noprimary option. + [357]-noprimary option. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and cutbuffers. - Q-76: Why don't I hear the "Beeps" in my X session (e.g. when typing + Q-77: Why don't I hear the "Beeps" in my X session (e.g. when typing tput bel in an xterm)? As of Dec/2003 in the libvncserver CVS "Beep" XBell events are tracked @@ -3545,21 +3694,21 @@ ied) not on by default in Solaris, see Xserver(1) for how to turn it on via +kb), and so you won't hear them if the extension is not present. - If you don't want to hear the beeps use the [353]-nobell option. If + If you don't want to hear the beeps use the [358]-nobell option. If you want to hear the audio from the remote applications, consider trying a redirector such as esd. Contributions: - Q-77: Thanks for your program and for your help! Can I make a + Q-78: Thanks for your program and for your help! Can I make a donation? Please do (any amount is appreciated) and thank you for your support! Click on the PayPal button below for more info. Also, in general I always enjoy hearing from x11vnc users, how they use it, what new features they would like, etc. Please send me an - [354]email! + [359]email! [PayPal] @@ -3701,224 +3850,229 @@ References 134. http://www.karlrunge.com/x11vnc/index.html#faq-black-screen 135. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc 136. http://www.karlrunge.com/x11vnc/index.html#faq-vmware - 137. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars - 138. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard - 139. http://www.karlrunge.com/x11vnc/index.html#faq-beeps - 140. http://www.karlrunge.com/x11vnc/index.html#faq-thanks - 141. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 144. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 145. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html - 146. http://www.karlrunge.com/x11vnc/index.html#building - 147. http://www.karlrunge.com/x11vnc/index.html#faq-build - 148. http://packages.debian.org/x11vnc - 149. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc - 150. http://dag.wieers.com/packages/x11vnc/ - 151. http://www.sunfreeware.com/ - 152. http://www.bell-labs.com/project/wwexptools/packages.html - 153. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 154. http://www.karlrunge.com/x11vnc/bins - 155. http://www.tightvnc.com/download.html - 156. http://www.realvnc.com/download-free.html - 157. http://sourceforge.net/projects/cotvnc/ - 158. http://www.karlrunge.com/x11vnc/x11vnc_opts.html - 159. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o - 163. http://www.karlrunge.com/x11vnc/x11vnc.c - 164. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe - 165. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding - 166. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb - 167. http://fredrik.hubbe.net/x2vnc.html - 168. http://www.hubbe.net/~hubbe/win2vnc.html - 169. http://www.deboer.gmxhome.de/ - 170. http://sourceforge.net/projects/win2vnc/ - 171. http://fredrik.hubbe.net/x2vnc.html - 172. http://freshmeat.net/projects/x2x/ - 173. http://ftp.digital.com/pub/Digital/SRC/x2x/ - 174. http://zapek.com/software/zvnc/ - 175. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual - 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap - 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor - 178. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp - 179. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 137. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 138. http://www.karlrunge.com/x11vnc/index.html#faq-hidden-taskbars + 139. http://www.karlrunge.com/x11vnc/index.html#faq-clipboard + 140. http://www.karlrunge.com/x11vnc/index.html#faq-beeps + 141. http://www.karlrunge.com/x11vnc/index.html#faq-thanks + 142. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 143. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 144. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 145. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 146. http://www.karlrunge.com/x11vnc/x11vnc_sunos4.html + 147. http://www.karlrunge.com/x11vnc/index.html#building + 148. http://www.karlrunge.com/x11vnc/index.html#faq-build + 149. http://packages.debian.org/x11vnc + 150. http://www.linuxpackages.net/search_view.php?by=name&name=x11vnc + 151. http://dag.wieers.com/packages/x11vnc/ + 152. http://www.sunfreeware.com/ + 153. http://www.bell-labs.com/project/wwexptools/packages.html + 154. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 155. http://www.karlrunge.com/x11vnc/bins + 156. http://www.tightvnc.com/download.html + 157. http://www.realvnc.com/download-free.html + 158. http://sourceforge.net/projects/cotvnc/ + 159. http://www.karlrunge.com/x11vnc/x11vnc_opts.html + 160. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 161. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 162. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 163. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-o + 164. http://www.karlrunge.com/x11vnc/x11vnc.c + 165. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sigpipe + 166. http://www.karlrunge.com/x11vnc/index.html#solarisbuilding + 167. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nofb + 168. http://fredrik.hubbe.net/x2vnc.html + 169. http://www.hubbe.net/~hubbe/win2vnc.html + 170. http://www.deboer.gmxhome.de/ + 171. http://sourceforge.net/projects/win2vnc/ + 172. http://fredrik.hubbe.net/x2vnc.html + 173. http://freshmeat.net/projects/x2x/ + 174. http://ftp.digital.com/pub/Digital/SRC/x2x/ + 175. http://zapek.com/software/zvnc/ + 176. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-visual + 177. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flashcmap + 178. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-notruecolor + 179. http://www.karlrunge.com/x11vnc/index.html#faq-8bpp 180. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 183. http://www.karlrunge.com/x11vnc/index.html#faq-overlays - 184. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid - 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display - 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder - 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 190. http://www.karlrunge.com/x11vnc/index.html#xauth_pain - 191. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 192. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg - 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys - 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote - 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query - 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd - 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 203. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 204. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd - 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd - 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever - 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared - 211. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 212. http://www.karlrunge.com/x11vnc/index.html#faq-passwd - 213. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile - 214. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 216. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers - 217. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 218. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen - 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow - 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 226. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 181. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 182. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 183. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 184. http://www.karlrunge.com/x11vnc/index.html#faq-overlays + 185. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 186. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sid + 187. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-display + 188. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 189. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-flipbyteorder + 190. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 191. http://www.karlrunge.com/x11vnc/index.html#xauth_pain + 192. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 193. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 194. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 195. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 196. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-bg + 197. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 198. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_keys + 199. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remote + 200. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-query + 201. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 202. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-storepasswd + 203. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 204. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 205. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewpasswd + 206. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwd + 207. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 208. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 209. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 210. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-forever + 211. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-shared + 212. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 213. http://www.karlrunge.com/x11vnc/index.html#faq-passwd + 214. http://www.karlrunge.com/x11vnc/index.html#faq-passwdfile + 215. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 216. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 217. http://www.karlrunge.com/x11vnc/index.html#faq-tcp_wrappers + 218. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 219. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 220. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 221. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 222. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 223. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 224. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-listen + 225. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-allow + 226. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost 227. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 228. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth - 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile - 231. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 232. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly - 235. ftp://ftp.x.org/ - 236. http://www.karlrunge.com/x11vnc/dtVncPopup - 237. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost - 239. http://www.karlrunge.com/x11vnc/index.html#tunnelling - 240. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 242. http://www.karlrunge.com/x11vnc/blockdpy.c - 243. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept - 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 228. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 229. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 230. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbauth + 231. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-passwdfile + 232. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 233. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 234. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 235. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-viewonly + 236. ftp://ftp.x.org/ + 237. http://www.karlrunge.com/x11vnc/dtVncPopup + 238. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 239. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-localhost + 240. http://www.karlrunge.com/x11vnc/index.html#tunnelling + 241. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept + 242. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 243. http://www.karlrunge.com/x11vnc/blockdpy.c + 244. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-accept 245. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone - 246. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 247. http://www.karlrunge.com/x11vnc/index.html#faq-inetd - 248. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop - 249. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 250. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris - 251. http://www.jirka.org/gdm-documentation/x241.html - 252. http://www.karlrunge.com/x11vnc/x11vnc_loop - 253. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth - 254. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd - 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q - 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth - 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir - 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect - 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 261. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously - 262. http://www.karlrunge.com/x11vnc/shm_clear - 263. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 265. http://www.karlrunge.com/x11vnc/index.html#faq-noshm - 266. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap - 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid - 274. http://www.tightvnc.com/ - 275. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive - 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs - 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode - 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads - 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area - 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem - 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 246. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gone + 247. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 248. http://www.karlrunge.com/x11vnc/index.html#faq-inetd + 249. http://www.karlrunge.com/x11vnc/index.html#x11vnc_loop + 250. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 251. http://www.karlrunge.com/x11vnc/index.html#dtlogin_solaris + 252. http://www.jirka.org/gdm-documentation/x241.html + 253. http://www.karlrunge.com/x11vnc/x11vnc_loop + 254. http://www.karlrunge.com/x11vnc/index.html#faq-xterminal-xauth + 255. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-inetd + 256. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-q + 257. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-auth + 258. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-httpdir + 259. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 260. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-vncconnect + 261. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 262. http://www.karlrunge.com/x11vnc/index.html#display-manager-continuously + 263. http://www.karlrunge.com/x11vnc/shm_clear + 264. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 265. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 266. http://www.karlrunge.com/x11vnc/index.html#faq-noshm + 267. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nap + 268. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 269. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 270. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 271. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 272. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 273. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 274. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-solid + 275. http://www.tightvnc.com/ + 276. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 277. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-progressive + 278. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-fs + 279. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 280. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 281. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 282. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 283. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 284. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 285. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 286. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 287. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pointer_mode + 288. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-threads + 289. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_area + 290. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xd_mem + 291. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage 292. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 294. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode - 295. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 296. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks - 297. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 302. http://www.tightvnc.com/ - 303. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer - 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 311. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless - 312. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 313. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 316. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak - 317. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 293. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 294. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 295. http://www.karlrunge.com/x11vnc/index.html#the-overlay-mode + 296. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 297. http://www.karlrunge.com/x11vnc/index.html#faq-xfixes-alpha-hacks + 298. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 299. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 300. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 301. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 302. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 303. http://www.tightvnc.com/ + 304. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 305. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 306. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 307. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 308. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 309. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 310. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 311. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 312. http://www.karlrunge.com/x11vnc/index.html#faq-greaterless + 313. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 314. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 315. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 316. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 317. http://www.karlrunge.com/x11vnc/index.html#faq-xkbmodtweak + 318. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 319. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 320. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 321. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes + 322. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 323. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 324. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 325. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms 326. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 327. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager - 328. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 327. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 328. http://www.karlrunge.com/x11vnc/index.html#faq-display-manager 329. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 330. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 331. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 332. http://www.karlrunge.com/x11vnc/index.html#faq-scaling - 333. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 334. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html - 335. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 340. http://www.karlrunge.com/x11vnc/index.html#faq-solshm - 341. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 332. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 333. http://www.karlrunge.com/x11vnc/index.html#faq-scaling + 334. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 335. http://www.cus.cam.ac.uk/~ssb22/source/vnc-magnification.html + 336. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 337. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 338. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 339. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 340. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 341. http://www.karlrunge.com/x11vnc/index.html#faq-solshm + 342. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 343. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 344. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip 345. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 348. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 346. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 347. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 348. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom 349. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc - 350. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 351. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 353. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 354. mailto:xvml@karlrunge.com + 350. http://www.karlrunge.com/x11vnc/index.html#faq-rawfb + 351. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 352. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 353. http://www.karlrunge.com/x11vnc/index.html#faq-xvfb + 354. http://www.karlrunge.com/x11vnc/index.html#faq-linuxvc + 355. http://www.karlrunge.com/x11vnc/index.html#faq-vmware + 356. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 357. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 358. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 359. mailto:xvml@karlrunge.com ======================================================================= @@ -3931,8 +4085,7 @@ x11vnc: a VNC server for real X displays Here are all of x11vnc command line options: % x11vnc -opts (see below for -help long descriptions) -x11vnc: allow VNC connections to real X11 displays. 0.7.2pre lastmod: 2005-04-0 -3 +x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-04-11 x11vnc options: -display disp -auth file @@ -3954,8 +4107,9 @@ x11vnc options: -users list -noshm -flipbyteorder -onetile -solid [color] -blackout string - -xinerama -xrandr [mode] - -padgeom WxH -o logfile + -xinerama -xtrap + -xrandr [mode] -padgeom WxH + -o logfile -flag file -rc filename -norc -h, -help -?, -opts -V, -version -q @@ -3984,6 +4138,7 @@ x11vnc options: -nothreads -fs f -gaps n -grow n -fuzz n -snapfb + -rawfb string -pipeinput cmd -gui [gui-opts] -remote command -query variable -sync -noremote -unsafe @@ -4014,8 +4169,7 @@ libvncserver options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.7.2pre lastmod: 2005-04-0 -3 +x11vnc: allow VNC connections to real X11 displays. 0.7.2 lastmod: 2005-04-11 Typical usage is: @@ -4147,16 +4301,18 @@ Options: the notation "m/n" may be used to denote fractions exactly, e.g. -scale 2/3 - Scaling Options: can be added after "fraction" via - ":", to supply multiple ":" options use commas. - If you just want a quick, rough scaling without - blending, append ":nb" to "fraction" (e.g. -scale - 1/3:nb). For compatibility with vncviewers the scaled - width is adjusted to be a multiple of 4: to disable - this use ":n4". More esoteric options: ":in" use - interpolation scheme even when shrinking, ":pad", - pad scaled width and height to be multiples of scaling - denominator (e.g. 3 for 2/3). + Scaling Options: can be added after "fraction" + via ":", to supply multiple ":" options use + commas. If you just want a quick, rough scaling + without blending, append ":nb" to "fraction" + (e.g. -scale 1/3:nb). No blending is the default + for 8bpp indexed color, to force blending for this + case use ":fb". For compatibility with vncviewers + the scaled width is adjusted to be a multiple of 4: + to disable this use ":n4". More esoteric options: + ":in" use interpolation scheme even when shrinking, + ":pad", pad scaled width and height to be multiples + of scaling denominator (e.g. 3 for 2/3). -scale_cursor frac By default if -scale is supplied the cursor shape is scaled by the same factor. Depending on your usage, @@ -4429,6 +4585,13 @@ Options: In general on XINERAMA displays you may need to use the -xwarppointer option if the mouse pointer misbehaves. +-xtrap Use the DEC-XTRAP extension for keystroke and mouse + input insertion. For use on legacy systems, e.g. X11R5, + running an incomplete or missing XTEST extension. + By default DEC-XTRAP will be used if XTEST server grab + control is missing, use -xtrap to do the keystroke and + mouse insertion via DEC-XTRAP as well. + -xrandr [mode] If the display supports the XRANDR (X Resize, Rotate and Reflection) extension, and you expect XRANDR events to occur to the display while x11vnc is running, this @@ -4468,9 +4631,13 @@ Options: -o logfile Write stderr messages to file "logfile" instead of to the terminal. Same as "-logfile file". To append to the file use "-oa file" or "-logappend file". --rc filename Use "filename" instead of $HOME/.x11vncrc for rc file. +-flag file Write the "PORT=NNNN" (e.g. PORT=5900) string to + "file" in addition to stdout. This option could be + useful by wrapper script to detect when x11vnc is ready. +-rc filename Use "filename" instead of $HOME/.x11vncrc for rc file. -norc Do not process any .x11vncrc file for options. + -h, -help Print this help text. -?, -opts Only list the x11vnc options. -V, -version Print program version and last modification date. @@ -4839,6 +5006,7 @@ Options: by checking the tile near the boundary. Default: 3 -fuzz n Tolerance in pixels to mark a tiles edges as changed. Default: 2 + -snapfb Instead of polling the X display framebuffer (fb) for changes, periodically copy all of X display fb into main memory and examine that copy for changes. Under some @@ -4853,6 +5021,59 @@ Options: It may be of use in video capture-like applications, or where window tearing is a problem. +-rawfb string Experimental option, instead of polling X, poll the + memory object specified in "string". For shared + memory segments it is of the form: "shm:N@WxHxB" + which specifies a shmid N and framebuffer Width, Height, + and Bits per pixel. To memory map mmap(2) a file use: + "map:/path/to/a/file@WxHxB". If there is trouble + with mmap, use "file:/..." for slower lseek(2) based + reading. + + If string is "setup:cmd", then the command "cmd" + is run and the first line from it is read and used + as "string". This allows initializing the device, + determining WxHxB, etc. These are often done as root + so take care. + + Optional suffixes are ":R/G/B" and "+O" to specify + red, green, and blue masks and an offset into the + memory object. If the masks are not provided x11vnc + guesses them based on the bpp. + + Examples: + -rawfb shm:210337933@800x600x32:ff/ff00/ff0000 + -rawfb map:/dev/fb0@1024x768x32 + -rawfb map:/tmp/Xvfb_screen0@640x480x8+3232 + -rawfb file:/tmp/my.pnm@250x200x24+37 + + (see ipcs(1) and fbset(1) for the first two examples) + + All user input is discarded. Most of the X11 (screen, + keyboard, mouse) options do not make sense and many + will cause this mode to crash, so please think twice + before setting/changing them. If you don't want x11vnc + to close the DISPLAY in rawfb mode, then capitalize + the prefix, SHM:, MAP: etc. Keeping the display open + enables default remote-control channel. + +-pipeinput cmd Another experimental option: it lets you supply + an extern command in "cmd" that x11vnc will pipe + all of the user input events to in a simple format. + In -pipeinput mode by default x11vnc will not process + any of the user input events. If you prefix "cmd" + with "tee:" it will both send them to the pipe + command and process them. For a description of the + format run "-pipeinput tee:/bin/cat". Another prefix + is "reopen" which means to reopen pipe if it exits. + Separate multiple prefixes with commas. + + In combination with -rawfb one might be able to + do amusing things (e.g. control non-X devices). + To facilitate this, if -rawfb is in effect then the + value is stored in X11VNC_RAWFB_STR for the pipe command + to use if it wants. Do 'env | grep X11VNC' for more. + -gui [gui-opts] Start up a simple tcl/tk gui based on the the remote control options -remote/-query described below. Requires the "wish" program to be installed on the @@ -5021,6 +5242,8 @@ Options: rectangle use "-WxH+X+Y" to delete one xinerama enable -xinerama mode. (if applicable) noxinerama disable -xinerama mode. + xtrap enable -xtrap input mode. + noxtrap disable -xtrap input mode. xrandr enable -xrandr mode. (if applicable) noxrandr disable -xrandr mode. xrandr_mode:mode set the -xrandr mode to "mode". @@ -5101,6 +5324,7 @@ Options: fuzz:n set -fuzz to n. snapfb enable -snapfb mode. nosnapfb disable -snapfb mode. + rawfb:str set -rawfb mode to "str". progressive:n set libvncserver -progressive slice height parameter to n. desktop:str set -desktop name to str for new clients @@ -5168,33 +5392,34 @@ Options: forever noforever once timeout deny lock nodeny unlock connect allowonce allow localhost nolocalhost listen lookup nolookup accept gone shm noshm flipbyteorder - noflipbyteorder onetile noonetile solid_color solid - nosolid blackout xinerama noxinerama xrandr noxrandr - xrandr_mode padgeom quiet q noquiet modtweak nomodtweak - xkb noxkb skip_keycodes add_keysyms noadd_keysyms - clear_mods noclear_mods clear_keys noclear_keys - remap repeat norepeat fb nofb bell nobell sel nosel - primary noprimary cursorshape nocursorshape cursorpos - nocursorpos cursor show_cursor noshow_cursor nocursor - arrow xfixes noxfixes xdamage noxdamage xd_area - xd_mem alphacut alphafrac alpharemove noalpharemove - alphablend noalphablend xwarp xwarppointer noxwarp - noxwarppointer buttonmap dragging nodragging + noflipbyteorder onetile noonetile solid_color + solid nosolid blackout xinerama noxinerama xtrap + noxtrap xrandr noxrandr xrandr_mode padgeom quiet q + noquiet modtweak nomodtweak xkb noxkb skip_keycodes + add_keysyms noadd_keysyms clear_mods noclear_mods + clear_keys noclear_keys remap repeat norepeat fb nofb + bell nobell sel nosel primary noprimary cursorshape + nocursorshape cursorpos nocursorpos cursor show_cursor + noshow_cursor nocursor arrow xfixes noxfixes xdamage + noxdamage xd_area xd_mem alphacut alphafrac alpharemove + noalpharemove alphablend noalphablend xwarp xwarppointer + noxwarp noxwarppointer buttonmap dragging nodragging pointer_mode pm input_skip input client_input speeds debug_pointer dp nodebug_pointer nodp debug_keyboard dk - nodebug_keyboard nodk deferupdate defer wait rfbwait - nap nonap sb screen_blank fs gaps grow fuzz snapfb - nosnapfb progressive rfbport http nohttp httpport + nodebug_keyboard nodk deferupdate defer wait rfbwait nap + nonap sb screen_blank fs gaps grow fuzz snapfb nosnapfb + rawfb setup: progressive rfbport http nohttp httpport httpdir enablehttpproxy noenablehttpproxy alwaysshared noalwaysshared nevershared noalwaysshared dontdisconnect nodontdisconnect desktop noremote - aro= display vncdisplay desktopname http_url auth - users rootshift clipshift scale_str scaled_x scaled_y - scale_numer scale_denom scale_fac scaling_noblend - scaling_nomult4 scaling_pad scaling_interpolate inetd - safer unsafe passwdfile using_shm logfile o rc norc - h help V version lastmod bg sigpipe threads clients + aro= debug_xevents: display vncdisplay desktopname + http_url auth users rootshift clipshift scale_str + scaled_x scaled_y scale_numer scale_denom + scale_fac scaling_blend scaling_nomult4 scaling_pad + scaling_interpolate inetd safer unsafe passwdfile + using_shm logfile o flag rc norc h help V version + lastmod bg sigpipe threads pipeinput clients client_count pid ext_xtest ext_xtrap ext_xkb ext_xshm ext_xinerama ext_overlay ext_xfixes ext_xdamage ext_xrandr rootwin num_buttons button_mask mouse_x diff --git a/x11vnc/misc/slide.pl b/x11vnc/misc/slide.pl index 0c90d0e..b8f284e 100755 --- a/x11vnc/misc/slide.pl +++ b/x11vnc/misc/slide.pl @@ -75,7 +75,7 @@ $I = 0; while (<>) { # read the next user input event, watch for button press or spacebar: - last if /^Keysym.* [qQ] /; + ###last if /^Keysym.* [qQ] /; next unless /^(Pointer.*ButtonPress|Keysym.*space.*KeyPress)/; $I = ($I + 1) % $N; showpic($I); @@ -108,5 +108,5 @@ sub showpic { } close(FB); -#unlink($fb); # this (probably) won't kill x11vnc +###unlink($fb); # this (probably) won't kill x11vnc print STDERR "$0 done.\n"; diff --git a/x11vnc/tkx11vnc b/x11vnc/tkx11vnc index d3fea5d..6f16085 100755 --- a/x11vnc/tkx11vnc +++ b/x11vnc/tkx11vnc @@ -176,6 +176,7 @@ Misc =-C:ignore,exit sigpipe: =0 inetd rfbwait: + pipeinput: -- =RA remote-cmd: =GA all-settings diff --git a/x11vnc/tkx11vnc.h b/x11vnc/tkx11vnc.h index c3642e6..66b7398 100644 --- a/x11vnc/tkx11vnc.h +++ b/x11vnc/tkx11vnc.h @@ -182,6 +182,7 @@ " =-C:ignore,exit sigpipe:\n" " =0 inetd\n" " rfbwait:\n" +" pipeinput:\n" " --\n" " =RA remote-cmd:\n" " =GA all-settings\n" diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index 08f253e..7bc9f6e 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "April 2005" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.7.2pre, lastmod: 2005-04-10 + version: 0.7.2, lastmod: 2005-04-11 .SH SYNOPSIS .B x11vnc [OPTION]... @@ -1164,8 +1164,8 @@ or where window tearing is a problem. Experimental option, instead of polling X, poll the memory object specified in \fIstring\fR. For shared memory segments it is of the form: "shm:N@WxHxB" -which specifies a shmid N and framebuffer width, height, -and bits per pixel. To memory map +which specifies a shmid N and framebuffer Width, Height, +and Bits per pixel. To memory map .IR mmap (2) a file use: "map:/path/to/a/file@WxHxB". If there is trouble @@ -1174,15 +1174,25 @@ with mmap, use "file:/..." for slower based reading. .IP +If string is "setup:cmd", then the command "cmd" +is run and the first line from it is read and used +as \fIstring\fR. This allows initializing the device, +determining WxHxB, etc. These are often done as root +so take care. +.IP Optional suffixes are ":R/G/B" and "+O" to specify red, green, and blue masks and an offset into the memory object. If the masks are not provided x11vnc guesses them based on the bpp. .IP Examples: +.IP \fB-rawfb\fR shm:210337933@800x600x32:ff/ff00/ff0000 +.IP \fB-rawfb\fR map:/dev/fb0@1024x768x32 +.IP \fB-rawfb\fR map:/tmp/Xvfb_screen0@640x480x8+3232 +.IP \fB-rawfb\fR file:/tmp/my.pnm@250x200x24+37 .IP (see @@ -1197,19 +1207,20 @@ will cause this mode to crash, so please think twice before setting/changing them. If you don't want x11vnc to close the DISPLAY in rawfb mode, then capitalize the prefix, SHM:, MAP: etc. Keeping the display open -enables defautl remote control channel. +enables default remote-control channel. .PP \fB-pipeinput\fR \fIcmd\fR .IP -Another experimental option: it lets you supply an -extern command in \fIcmd\fR that x11vnc will pipe all of -the user input events to in a simple format. By default -x11vnc will not process any of the user input events. -If you prefix \fIcmd\fR with "tee:" it will both send -them to the pipe command and process them. For a -description of the format run "\fB-pipeinput\fR \fItee:cat\fR". -Another prefix is "reopen" which means to reopen pipe -if it exits. Separate multiple prefixes with commas. +Another experimental option: it lets you supply +an extern command in \fIcmd\fR that x11vnc will pipe +all of the user input events to in a simple format. +In \fB-pipeinput\fR mode by default x11vnc will not process +any of the user input events. If you prefix \fIcmd\fR +with "tee:" it will both send them to the pipe +command and process them. For a description of the +format run "\fB-pipeinput\fR \fItee:/bin/cat\fR". Another prefix +is "reopen" which means to reopen pipe if it exits. +Separate multiple prefixes with commas. .IP In combination with \fB-rawfb\fR one might be able to do amusing things (e.g. control non-X devices). @@ -1717,25 +1728,26 @@ noalpharemove alphablend noalphablend xwarp xwarppointer noxwarp noxwarppointer buttonmap dragging nodragging pointer_mode pm input_skip input client_input speeds debug_pointer dp nodebug_pointer nodp debug_keyboard dk -nodebug_keyboard nodk deferupdate defer wait rfbwait -nap nonap sb screen_blank fs gaps grow fuzz snapfb -nosnapfb rawfb progressive rfbport http nohttp httpport +nodebug_keyboard nodk deferupdate defer wait rfbwait nap +nonap sb screen_blank fs gaps grow fuzz snapfb nosnapfb +rawfb setup: progressive rfbport http nohttp httpport httpdir enablehttpproxy noenablehttpproxy alwaysshared noalwaysshared nevershared noalwaysshared dontdisconnect nodontdisconnect desktop noremote .IP -aro= display vncdisplay desktopname http_url auth -users rootshift clipshift scale_str scaled_x scaled_y -scale_numer scale_denom scale_fac scaling_blend -scaling_nomult4 scaling_pad scaling_interpolate -inetd safer unsafe passwdfile using_shm logfile o -flag rc norc h help V version lastmod bg sigpipe -threads clients client_count pid ext_xtest ext_xtrap -ext_xkb ext_xshm ext_xinerama ext_overlay ext_xfixes -ext_xdamage ext_xrandr rootwin num_buttons button_mask -mouse_x mouse_y bpp depth indexed_color dpy_x dpy_y -wdpy_x wdpy_y off_x off_y cdpy_x cdpy_y coff_x coff_y -rfbauth passwd +aro= debug_xevents: display vncdisplay desktopname +http_url auth users rootshift clipshift scale_str +scaled_x scaled_y scale_numer scale_denom +scale_fac scaling_blend scaling_nomult4 scaling_pad +scaling_interpolate inetd safer unsafe passwdfile +using_shm logfile o flag rc norc h help V version +lastmod bg sigpipe threads pipeinput clients +client_count pid ext_xtest ext_xtrap ext_xkb ext_xshm +ext_xinerama ext_overlay ext_xfixes ext_xdamage +ext_xrandr rootwin num_buttons button_mask mouse_x +mouse_y bpp depth indexed_color dpy_x dpy_y wdpy_x +wdpy_y off_x off_y cdpy_x cdpy_y coff_x coff_y rfbauth +passwd .PP \fB-sync\fR .IP diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index ef3faf4..bd06c44 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -405,7 +405,7 @@ int overlay_present = 0; #if LIBVNCSERVER_HAVE_LIBXRANDR #include <X11/extensions/Xrandr.h> #endif -static int xrandr_base_event_type = 0; +int xrandr_base_event_type = 0; int xfixes_present = 0; @@ -419,8 +419,8 @@ int alt_arrow = 1; #if LIBVNCSERVER_HAVE_LIBXFIXES #include <X11/extensions/Xfixes.h> -static int xfixes_base_event_type = 0; #endif +int xfixes_base_event_type = 0; int xdamage_present = 0; @@ -428,15 +428,15 @@ int use_xdamage = 1; /* just use the xdamage rects. for scanline hints */ #if LIBVNCSERVER_HAVE_LIBXDAMAGE #include <X11/extensions/Xdamage.h> Damage xdamage = 0; -static int xdamage_base_event_type = 0; #endif +int xdamage_base_event_type = 0; int xdamage_max_area = 20000; /* pixels */ double xdamage_memory = 1.0; /* in units of NSCAN */ int xdamage_tile_count; /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.7.2pre lastmod: 2005-04-10"; +char lastmod[] = "0.7.2 lastmod: 2005-04-11"; int hack_val = 0; /* X display info */ @@ -559,7 +559,6 @@ unsigned char *tile_has_xdamage_diff, *tile_row_has_xdamage_diff; /* times of recent events */ time_t last_event, last_input, last_client = 0; -time_t last_sendevent = 0; /* last client to move pointer */ rfbClientPtr last_pointer_client = NULL; @@ -820,6 +819,8 @@ int pipeinput_tee = 0; unsigned long subwin = 0x0; /* -id, -sid */ int subwin_wait_mapped = 0; +int debug_xevents = 0; /* -R debug_xevents:1 */ + int xtrap_input = 0; /* -xtrap for user input insertion */ int xinerama = 0; /* -xinerama */ int xrandr = 0; /* -xrandr */ @@ -2315,20 +2316,23 @@ XImage *XCreateImage_wr(Display *disp, Visual *visual, unsigned int depth, void copy_raw_fb(XImage *dest, int x, int y, unsigned int w, unsigned int h) { char *src, *dst; int line, pixelsize = bpp/8; + int bpl = wdpy_x * pixelsize; + if (clipshift) { + x += coff_x; + y += coff_y; + } if (! raw_fb_seek) { - src = (raw_fb_addr + raw_fb_offset) - + raw_fb_image->bytes_per_line*y + pixelsize*x; + src = raw_fb_addr + raw_fb_offset + bpl*y + pixelsize*x; dst = dest->data; for (line = 0; line < h; line++) { memcpy(dst, src, w * pixelsize); - src += raw_fb_image->bytes_per_line; + src += bpl; dst += dest->bytes_per_line; } } else{ int n, len, del, sz = w * pixelsize; - int bpl = raw_fb_image->bytes_per_line; off_t off = (off_t) (raw_fb_offset + bpl*y + pixelsize*x); lseek(raw_fb_fd, off, SEEK_SET); @@ -2352,6 +2356,10 @@ void copy_raw_fb(XImage *dest, int x, int y, unsigned int w, unsigned int h) { } } } + if (bpl > sz) { + off = (off_t) (bpl - sz); + lseek(raw_fb_fd, off, SEEK_CUR); + } dst += dest->bytes_per_line; } } @@ -3187,6 +3195,25 @@ void set_client_input(char *str) { free(cl_list); } +void set_child_info(void) { + char pid[16]; + /* set up useful environment for child process */ + sprintf(pid, "%d", (int) getpid()); + set_env("X11VNC_PID", pid); + if (program_name) { + /* e.g. for remote control -R */ + set_env("X11VNC_PROG", program_name); + } + if (program_cmdline) { + set_env("X11VNC_CMDLINE", program_cmdline); + } + if (raw_fb_str) { + set_env("X11VNC_RAWFB_STR", raw_fb_str); + } else { + set_env("X11VNC_RAWFB_STR", ""); + } +} + /* * utility to run a user supplied command setting some RFB_ env vars. * used by, e.g., accept_client() and client_gone() @@ -6751,7 +6778,6 @@ int check_pipeinput(void) { void initialize_pipeinput(void) { char *p; - char pid[16]; if (pipeinput_fh != NULL) { rfbLog("closing pipeinput stream: %p\n", pipeinput_fh); @@ -6803,20 +6829,7 @@ void initialize_pipeinput(void) { p = pipeinput_str; } - /* set up useful environment for child process */ - sprintf(pid, "%d", (int) getpid()); - set_env("X11VNC_PID", pid); - if (program_name) { - /* e.g. for remote control -R */ - set_env("X11VNC_PROG", program_name); - } - if (program_cmdline) { - set_env("X11VNC_CMDLINE", program_cmdline); - } - if (raw_fb_str) { - set_env("X11VNC_RAWFB_STR", raw_fb_str); - } - + set_child_info(); rfbLog("pipeinput: starting: \"%s\"...\n", p); pipeinput_fh = popen(p, "w"); @@ -6862,7 +6875,7 @@ void initialize_pipeinput(void) { "# if two more more buttons change state in one event they are listed\n" "# separated by commas.\n" "#\n" -"# One might parse a Pointer like with:\n" +"# One might parse a Pointer line with:\n" "#\n" "# int client, x, y, mask; char *hint;\n" "# sscanf(line, \"Pointer %d %d %d %s\", &client, &x, &y, &mask, &hint);\n" @@ -6887,7 +6900,7 @@ void initialize_pipeinput(void) { "# You basically remove the leading 'XK_' prefix from the macro name in\n" "# that file to get the Keysym name.\n" "#\n" -"# One might parse a Pointer like with:\n" +"# One might parse a Keysym line with:\n" "#\n" "# int client, down, keysym; char *name, *hint;\n" "# sscanf(line, \"Keysym %d %d %s %s\", &client, &down, &keysym, &name, &hint);\n" @@ -6907,7 +6920,8 @@ void initialize_pipeinput(void) { "# info will be enough for most purposes (having identical keyboards on\n" "# both sides helps).\n" "#\n" -"# Here comes yours stream:\n" +"# Here comes your stream. The following token will always indicate the\n" +"# end of this informational text:\n" "# END_OF_TOP\n" ); fflush(pipeinput_fh); @@ -6921,10 +6935,9 @@ void initialize_pipeinput(void) { /* * Bell event handling. Requires XKEYBOARD extension. */ -#if LIBVNCSERVER_HAVE_XKEYBOARD - -static int xkb_base_event_type = 0; +int xkb_base_event_type = 0; +#if LIBVNCSERVER_HAVE_XKEYBOARD /* * check for XKEYBOARD, set up xkb_base_event_type */ @@ -7374,7 +7387,6 @@ static void selection_request(XEvent *ev) { if (! trapped_xerror) { XSendEvent(req_event->display, req_event->requestor, False, 0, (XEvent *)¬ify_event); - last_sendevent = time(0); } if (trapped_xerror) { rfbLog("selection_request: ignored XError while sending " @@ -7586,6 +7598,18 @@ void initialize_xevents(void) { } } +void print_xevent_bases(void) { + fprintf(stderr, "X event bases: xkb=%d, xtest=%d, xrandr=%d, " + "xfixes=%d, xdamage=%d, xtrap=%d\n", xkb_base_event_type, + xtest_base_event_type, xrandr_base_event_type, + xfixes_base_event_type, xdamage_base_event_type, + xtrap_base_event_type); + fprintf(stderr, " MapNotify=%d, ClientMsg=%d PropNotify=%d " + "SelNotify=%d, SelRequest=%d\n", MappingNotify, ClientMessage, + PropertyNotify, SelectionNotify, SelectionRequest); + fprintf(stderr, " SelClear=%d, Expose=%d\n", SelectionClear, Expose); +} + /* * This routine is periodically called to check for selection related * and other X11 events and respond to them as needed. @@ -7685,9 +7709,6 @@ void check_xevents(void) { ; } } - } - - if (last_sendevent && (now > last_sendevent+1 || now % 10 == 0)) { /* * we can get ClientMessage from our XSendEvent() call in * selection_request(). @@ -7695,7 +7716,6 @@ void check_xevents(void) { while (XCheckTypedEvent(dpy, ClientMessage, &xev)) { ; } - last_sendevent = 0; } /* check for CUT_BUFFER0 and VNC_CONNECT changes: */ @@ -7804,28 +7824,44 @@ void check_xevents(void) { #define DEBUG_XEVENTS 1 #endif #if DEBUG_XEVENTS - if (hack_val) { + if (debug_xevents) { static time_t last_check = 0; + static time_t reminder = 0; + static int freq = 0; + + if (! freq) { + if (getenv("X11VNC_REMINDER_RATE")) { + freq = atoi(getenv("X11VNC_REMINDER_RATE")); + } else { + freq = 300; + } + } if (now > last_check + 1) { + int ev_max = 300, ev_size = 400; XEvent xevs[400]; int i, tot = XEventsQueued(dpy, QueuedAlready); + if (reminder == 0 || (tot && now > reminder + freq)) { + print_xevent_bases(); + reminder = now; + } last_check = now; + if (tot) { fprintf(stderr, "Total events queued: %d\n", tot); } - for (i=1; i<300; i++) { + for (i=1; i<ev_max; i++) { int k, n = 0; while (XCheckTypedEvent(dpy, i, xevs+n)) { - if (++n >= 400) { + if (++n >= ev_size) { break; } } if (n) { - fprintf(stderr, "%d events of type %d " - "queued\n", n, i); + fprintf(stderr, " %d events of type %d" + " queued\n", n, i); } for (k=n-1; k >= 0; k--) { XPutBackEvent(dpy, xevs+k); @@ -7843,6 +7879,8 @@ void check_xevents(void) { if (qlen >= bugout) { rfbLog("event leak: %d queued, " " calling XSync(dpy, True)\n", qlen); + rfbLog(" for diagnostics run: 'x11vnc -R" + " debug_xevents:1'\n"); XSync(dpy, True); } } @@ -10344,6 +10382,11 @@ char *process_remote_cmd(char *cmd, int stringonly) { p += strlen("rawfb:"); if (raw_fb_str) free(raw_fb_str); raw_fb_str = strdup(p); + if (safe_remote_only && strstr(p, "setup:") == p) { + /* n.b. we still allow filename, shm, of rawfb */ + fprintf(stderr, "unsafe rawfb setup: %s\n", p); + exit(1); + } rfbLog("process_remote_cmd: setting -rawfb to:\n" "\t'%s'\n", p); @@ -10538,6 +10581,16 @@ char *process_remote_cmd(char *cmd, int stringonly) { rfbLog("process_remote_cmd: disabling remote commands.\n"); accept_remote_cmds = 0; /* cannot be turned back on. */ + } else if (strstr(p, "debug_xevents:") == p) { + COLON_CHECK("debug_xevents:") + if (query) { + snprintf(buf, bufn, "ans=%s%s%d", p, co, debug_xevents); + goto qry; + } + p += strlen("debug_xevents:"); + debug_xevents = atoi(p); + rfbLog("set debug_xevents to: %d\n", debug_xevents); + } else if (strstr(p, "hack:") == p) { /* skip-cmd-list */ COLON_CHECK("hack:") if (query) { @@ -10640,6 +10693,9 @@ char *process_remote_cmd(char *cmd, int stringonly) { snprintf(buf, bufn, "aro=%s:%s", p, NONUL(sigpipe)); } else if (!strcmp(p, "threads")) { snprintf(buf, bufn, "aro=%s:%d", p, use_threads); + } else if (!strcmp(p, "pipeinput")) { + snprintf(buf, bufn, "aro=%s:%s", p, + NONUL(pipeinput_str)); } else if (!strcmp(p, "clients")) { char *str = list_clients(); snprintf(buf, bufn, "aro=%s:%s", p, str); @@ -11064,7 +11120,7 @@ void check_xdamage_state(void) { * Create or destroy the Damage object as needed, we don't want * one if no clients are connected. */ - if (client_count) { + if (client_count && use_xdamage) { create_xdamage_if_needed(); } else { destroy_xdamage_if_needed(); @@ -13391,7 +13447,7 @@ XImage *initialize_raw_fb(void) { int w, h, b, shmid = 0; unsigned long rm = 0, gm = 0, bm = 0; static XImage ximage_struct; /* n.b.: not (XImage *) */ - int closedpy = 1; + int closedpy = 1, i, m; if (raw_fb_addr || raw_fb_seek) { if (raw_fb_shm) { @@ -13415,7 +13471,38 @@ XImage *initialize_raw_fb(void) { } - str = strdup(raw_fb_str); + if ( (q = strstr(raw_fb_str, "setup:")) == raw_fb_str) { + FILE *pipe; + char line[1024], *t; + + set_child_info(); + q += strlen("setup:"); + rfbLog("running command to setup rawfb: %s\n", q); + pipe = popen(q, "r"); + if (! pipe) { + rfbLog("popen of setup command failed.\n"); + rfbLogPerror("popen"); + clean_up_exit(1); + } + line[0] = '\0'; + if (fgets(line, 1024, pipe) == NULL) { + rfbLog("read of setup command failed.\n"); + clean_up_exit(1); + } + pclose(pipe); + str = strdup(line); + t = str; + while (*t != '\0') { + if (*t == '\n') { + *t = '\0'; + } + t++; + } + rfbLog("setup command returned: %s\n", str); + + } else { + str = strdup(raw_fb_str); + } /* * uppercase means do not close the display (e.g. for remote control) @@ -13480,12 +13567,12 @@ XImage *initialize_raw_fb(void) { } } if ((q = strrchr(str, '@')) == NULL) { - rfbLog("invalid rawfb str: %s\n", raw_fb_str); + rfbLog("invalid rawfb str: %s\n", str); clean_up_exit(1); } /* @WxHxB */ if (sscanf(q, "@%dx%dx%d", &w, &h, &b) != 3) { - rfbLog("invalid rawfb str: %s\n", raw_fb_str); + rfbLog("invalid rawfb str: %s\n", str); clean_up_exit(1); } @@ -13505,8 +13592,7 @@ XImage *initialize_raw_fb(void) { /* shm:N */ raw_fb_addr = (char *) shmat(shmid, 0, SHM_RDONLY); if (! raw_fb_addr) { - rfbLog("failed to attach to shm: %d, %s\n", shmid, - raw_fb_str); + rfbLog("failed to attach to shm: %d, %s\n", shmid, str); rfbLogPerror("shmat"); clean_up_exit(1); } @@ -13528,7 +13614,7 @@ XImage *initialize_raw_fb(void) { fd = open(q, O_RDONLY); if (fd < 0) { - rfbLog("failed to open file: %s, %s\n", q, raw_fb_str); + rfbLog("failed to open file: %s, %s\n", q, str); rfbLogPerror("open"); clean_up_exit(1); } @@ -13549,8 +13635,7 @@ XImage *initialize_raw_fb(void) { fd, 0); if (raw_fb_addr == MAP_FAILED || raw_fb_addr == NULL) { - rfbLog("failed to mmap file: %s, %s\n", - q, raw_fb_str); + rfbLog("failed to mmap file: %s, %s\n", q, str); rfbLog(" raw_fb_addr: %p\n", raw_fb_addr); rfbLogPerror("mmap"); clean_up_exit(1); @@ -13572,7 +13657,7 @@ XImage *initialize_raw_fb(void) { rfbLog(" W: %d H: %d B: %d sz: %d\n", w, h, b, size); } } else { - rfbLog("invalid rawfb str: %s\n", raw_fb_str); + rfbLog("invalid rawfb str: %s\n", str); clean_up_exit(1); } @@ -13580,14 +13665,15 @@ XImage *initialize_raw_fb(void) { raw_fb_image = &ximage_struct; } - raw_fb = (char *) malloc(w*h*b/8); + initialize_clipshift(); + + raw_fb = (char *) malloc(dpy_x * dpy_y * b/8); raw_fb_image->data = raw_fb; raw_fb_image->format = ZPixmap; - raw_fb_image->width = w; - raw_fb_image->height = h; + raw_fb_image->width = dpy_x; + raw_fb_image->height = dpy_y; raw_fb_image->bits_per_pixel = b; - raw_fb_image->depth = (b == 32) ? 24 : b; - raw_fb_image->bytes_per_line = w*b/8; + raw_fb_image->bytes_per_line = dpy_x*b/8; if (rm == 0 && gm == 0 && bm == 0) { /* guess masks... */ @@ -13610,18 +13696,36 @@ XImage *initialize_raw_fb(void) { raw_fb_image->green_mask = gm; raw_fb_image->blue_mask = bm; - if (raw_fb_addr) { - memcpy(raw_fb, raw_fb_addr + raw_fb_offset, w*h*(b/8)); + raw_fb_image->depth = 0; + m = 1; + for (i=0; i<32; i++) { + if (rm & m) { + raw_fb_image->depth++; + } + if (gm & m) { + raw_fb_image->depth++; + } + if (bm & m) { + raw_fb_image->depth++; + } + m = m << 1; + } + if (! raw_fb_image->depth) { + raw_fb_image->depth = (b == 32) ? 24 : b; + } + + if (clipshift) { + memset(raw_fb, 0xff, dpy_x * dpy_y * b/8); + } else if (raw_fb_addr) { + memcpy(raw_fb, raw_fb_addr + raw_fb_offset, dpy_x*dpy_y*b/8); } else { - memset(raw_fb, 0xff, w*h*(b/8)); + memset(raw_fb, 0xff, dpy_x * dpy_y * b/8); } rfbLog("rawfb: raw_fb %p\n", raw_fb); free(str); - initialize_clipshift(); - return raw_fb_image; } @@ -16614,7 +16718,7 @@ void mark_rect_as_modified(int x1, int y1, int x2, int y2, int force) { if (damage_time != 0) { /* * This is not XDAMAGE, rather a hack for testing - * were we allow the framebuffer to be corrupted for + * where we allow the framebuffer to be corrupted for * damage_delay seconds. */ int debug = 0; @@ -20204,12 +20308,18 @@ static void print_help(int mode) { "-rawfb string Experimental option, instead of polling X, poll the\n" " memory object specified in \"string\". For shared\n" " memory segments it is of the form: \"shm:N@WxHxB\"\n" -" which specifies a shmid N and framebuffer width, height,\n" -" and bits per pixel. To memory map mmap(2) a file use:\n" +" which specifies a shmid N and framebuffer Width, Height,\n" +" and Bits per pixel. To memory map mmap(2) a file use:\n" " \"map:/path/to/a/file@WxHxB\". If there is trouble\n" " with mmap, use \"file:/...\" for slower lseek(2) based\n" " reading.\n" "\n" +" If string is \"setup:cmd\", then the command \"cmd\"\n" +" is run and the first line from it is read and used\n" +" as \"string\". This allows initializing the device,\n" +" determining WxHxB, etc. These are often done as root\n" +" so take care.\n" +"\n" " Optional suffixes are \":R/G/B\" and \"+O\" to specify\n" " red, green, and blue masks and an offset into the\n" " memory object. If the masks are not provided x11vnc\n" @@ -20229,17 +20339,18 @@ static void print_help(int mode) { " before setting/changing them. If you don't want x11vnc\n" " to close the DISPLAY in rawfb mode, then capitalize\n" " the prefix, SHM:, MAP: etc. Keeping the display open\n" -" enables defautl remote control channel.\n" +" enables default remote-control channel.\n" "\n" -"-pipeinput cmd Another experimental option: it lets you supply an\n" -" extern command in \"cmd\" that x11vnc will pipe all of\n" -" the user input events to in a simple format. By default\n" -" x11vnc will not process any of the user input events.\n" -" If you prefix \"cmd\" with \"tee:\" it will both send\n" -" them to the pipe command and process them. For a\n" -" description of the format run \"-pipeinput tee:cat\".\n" -" Another prefix is \"reopen\" which means to reopen pipe\n" -" if it exits. Separate multiple prefixes with commas.\n" +"-pipeinput cmd Another experimental option: it lets you supply\n" +" an extern command in \"cmd\" that x11vnc will pipe\n" +" all of the user input events to in a simple format.\n" +" In -pipeinput mode by default x11vnc will not process\n" +" any of the user input events. If you prefix \"cmd\"\n" +" with \"tee:\" it will both send them to the pipe\n" +" command and process them. For a description of the\n" +" format run \"-pipeinput tee:/bin/cat\". Another prefix\n" +" is \"reopen\" which means to reopen pipe if it exits.\n" +" Separate multiple prefixes with commas.\n" "\n" " In combination with -rawfb one might be able to\n" " do amusing things (e.g. control non-X devices).\n" @@ -20588,25 +20699,26 @@ static void print_help(int mode) { " noxwarp noxwarppointer buttonmap dragging nodragging\n" " pointer_mode pm input_skip input client_input speeds\n" " debug_pointer dp nodebug_pointer nodp debug_keyboard dk\n" -" nodebug_keyboard nodk deferupdate defer wait rfbwait\n" -" nap nonap sb screen_blank fs gaps grow fuzz snapfb\n" -" nosnapfb rawfb progressive rfbport http nohttp httpport\n" +" nodebug_keyboard nodk deferupdate defer wait rfbwait nap\n" +" nonap sb screen_blank fs gaps grow fuzz snapfb nosnapfb\n" +" rawfb setup: progressive rfbport http nohttp httpport\n" " httpdir enablehttpproxy noenablehttpproxy alwaysshared\n" " noalwaysshared nevershared noalwaysshared dontdisconnect\n" " nodontdisconnect desktop noremote\n" "\n" -" aro= display vncdisplay desktopname http_url auth\n" -" users rootshift clipshift scale_str scaled_x scaled_y\n" -" scale_numer scale_denom scale_fac scaling_blend\n" -" scaling_nomult4 scaling_pad scaling_interpolate\n" -" inetd safer unsafe passwdfile using_shm logfile o\n" -" flag rc norc h help V version lastmod bg sigpipe\n" -" threads clients client_count pid ext_xtest ext_xtrap\n" -" ext_xkb ext_xshm ext_xinerama ext_overlay ext_xfixes\n" -" ext_xdamage ext_xrandr rootwin num_buttons button_mask\n" -" mouse_x mouse_y bpp depth indexed_color dpy_x dpy_y\n" -" wdpy_x wdpy_y off_x off_y cdpy_x cdpy_y coff_x coff_y\n" -" rfbauth passwd\n" +" aro= debug_xevents: display vncdisplay desktopname\n" +" http_url auth users rootshift clipshift scale_str\n" +" scaled_x scaled_y scale_numer scale_denom\n" +" scale_fac scaling_blend scaling_nomult4 scaling_pad\n" +" scaling_interpolate inetd safer unsafe passwdfile\n" +" using_shm logfile o flag rc norc h help V version\n" +" lastmod bg sigpipe threads pipeinput clients\n" +" client_count pid ext_xtest ext_xtrap ext_xkb ext_xshm\n" +" ext_xinerama ext_overlay ext_xfixes ext_xdamage\n" +" ext_xrandr rootwin num_buttons button_mask mouse_x\n" +" mouse_y bpp depth indexed_color dpy_x dpy_y wdpy_x\n" +" wdpy_y off_x off_y cdpy_x cdpy_y coff_x coff_y rfbauth\n" +" passwd\n" "\n" "-sync By default -remote commands are run asynchronously, that\n" " is, the request is posted and the program immediately\n" @@ -22215,6 +22327,10 @@ int main(int argc, char* argv[]) { } else { xtest_present = 1; xtest_base_event_type = ev; + if (maj <= 1 || (maj == 2 && min <= 2)) { + /* no events defined as of 2.2 */ + xtest_base_event_type = 0; + } } if (! XETrapQueryExtension_wr(dpy, &ev, &er, &maj)) { |