diff options
| author | runge <runge> | 2009-03-13 02:06:17 +0000 |
|---|---|---|
| committer | runge <runge> | 2009-03-13 02:06:17 +0000 |
| commit | 03666d6a17d8d0a1b436d3b781eec1c53e6b65d2 (patch) | |
| tree | 6390f75671c85b848d24fb4be26cdaf31d6d6558 | |
| parent | e2874d343a58e5f5f94739d864545a9d80c4cd87 (diff) | |
| download | libvncserver-03666d6a17d8d0a1b436d3b781eec1c53e6b65d2.zip libvncserver-03666d6a17d8d0a1b436d3b781eec1c53e6b65d2.tar.gz | |
x11vnc: Fix off-screen bug for -ncache_cr copyrect.
| -rw-r--r-- | x11vnc/ChangeLog | 3 | ||||
| -rw-r--r-- | x11vnc/README | 755 | ||||
| -rw-r--r-- | x11vnc/screen.c | 2 | ||||
| -rw-r--r-- | x11vnc/userinput.c | 22 | ||||
| -rw-r--r-- | x11vnc/x11vnc.1 | 2 | ||||
| -rw-r--r-- | x11vnc/x11vnc.c | 3 | ||||
| -rw-r--r-- | x11vnc/x11vnc_defs.c | 2 |
7 files changed, 413 insertions, 376 deletions
diff --git a/x11vnc/ChangeLog b/x11vnc/ChangeLog index eec74db..622a56f 100644 --- a/x11vnc/ChangeLog +++ b/x11vnc/ChangeLog @@ -1,3 +1,6 @@ +2009-03-12 Karl Runge <runge@karlrunge.com> + * x11vnc: Fix off-screen bug for -ncache_cr copyrect. + 2009-03-07 Karl Runge <runge@karlrunge.com> * x11vnc: allow range for X11VNC_SKIP_DISPLAY, document grab Xserver issue. Add progress_client() to proceed more quickly diff --git a/x11vnc/README b/x11vnc/README index 6913206..cd152a0 100644 --- a/x11vnc/README +++ b/x11vnc/README @@ -1,5 +1,5 @@ -x11vnc README file Date: Sat Mar 7 13:17:22 EST 2009 +x11vnc README file Date: Sun Mar 8 14:51:06 EDT 2009 The following information is taken from these URLs: @@ -6164,7 +6164,7 @@ EndSection local viewer-side VNC encoding; is used to swap the pixel data in and out of the actual display area. It gives an excellent speedup for iconifying/deiconifying and moving windows and re-posting of menus - (often it doesn't feel like VNC at all; there is no delay waiting for + (often it doesn't feel like VNC at all: there is no delay waiting for the pixel data to fill in). This scheme is nice because it does all of this within the existing @@ -6175,12 +6175,15 @@ EndSection protocol, modify a viewer and then also convince users to adopt your modified VNC Viewer (or get the new features to be folded into the main VNC viewers, patches accepted, etc... likely takes years before - they are deployed in the field) + they might be deployed in the field) A drawback of the "-ncache n" method is that in the VNC Viewer you can - scroll down and actually see the cached pixel data. One will need to - try to adjust the size of the VNC Viewer window so the cache area - cannot be seen. + scroll down and actually see the cached pixel data. So it looks like + there is a bug: you can scroll down in your viewer and see a strange + "history" of windows on your desktop. This is working as intended. One + will need to try to adjust the size of his VNC Viewer window so the + cache area cannot be seen. [537]SSVNC (see below) can do this + automatically. At some point LibVNCServer may implement a "rfbFBCrop" pseudoencoding that viewers can use to learn which portion of the framebuffer to @@ -6189,14 +6192,14 @@ EndSection rendering...). The Enhanced TightVNC Viewer (SSVNC) Unix viewer has a nice - [537]-ycrop option to help hide the pixel cache area from view. It + [538]-ycrop option to help hide the pixel cache area from view. It will turn on automatically if the framebuffer appears to be very tall (height more than twice the width), or you can supply the actual value - for the height. If the screen resized by scaling, etc, the ycrop value - is scaled as well. In fullscreen mode you cannot scroll past the end - of the actual screen, and in non-fullscreen mode the window manager - frame is adjusted to fit the actual display (so you don't see the - pixel cache region) and the scrollbars are very thin to avoid + for the height. If the screen is resized by scaling, etc, the ycrop + value is scaled as well. In fullscreen mode you cannot scroll past the + end of the actual screen, and in non-fullscreen mode the window + manager frame is adjusted to fit the actual display (so you don't see + the pixel cache region) and the scrollbars are very thin to avoid distraction and trouble fitting inside your display. Use the "-sbwidth n" viewer option to make the scrollbars thicker if you like. @@ -6206,7 +6209,9 @@ EndSection be fairly large, 6-12, to achieve good response. This usually requires about 50-100MB of additional RAM on both the client and server sides. For example with n=6 a 1280x1024 display will use a framebuffer that - is 1280x7168: everything below row 1024 is the pixel buffer cache. + is 1280x7168: everything below row 1024 is the pixel buffer cache. If + you are running on low memory machines or memory is tight because of + other running applications you should not use -ncache. The reason for so much memory is because the pixel data is not compressed and so the whole window to be saved must be stored @@ -6218,7 +6223,7 @@ EndSection an additional factor of 2 in memory use. However, even in the smallest usage mode with n equal 2 and - [538]-ncache_no_rootpixmap set (this requires only 2X additional + [539]-ncache_no_rootpixmap set (this requires only 2X additional framebuffer memory) there is still a noticable improvement for many activities, although it is not as dramatic as with, say n equal 12 and rootpixmap (desktop background) caching enabled. @@ -6229,7 +6234,7 @@ EndSection be tuned to use less, or the VNC community will extend the protocol to allow caching and replaying of compressed blobs of data. - Another option to experiment with is "[539]-ncache_cr". By specifying + Another option to experiment with is "[540]-ncache_cr". By specifying it, x11vnc will try to do smooth opaque window moves instead of its wireframe. This can give a very nice effect (note: on Unix the realvnc viewer seems to be smoother than the tightvnc viewer), but can lead to @@ -6247,11 +6252,12 @@ EndSection "Alt" key) 3 times in a row to signal x11vnc to refresh the screen to all viewers. You may also need to iconify and then deiconify any damaged windows to correct their cache data as well. Note that if you - change color depth (e.g. 8bpp to full color) dynamically that will - usually lead to the entire extended framebuffer being resent which can - take a long time over very slow links: it may be better to reconnect - and reset the format right after doing so. x11vnc will try to detect - the format change and clear (make completely black) the cache region. + change color viewer depth (e.g. 8bpp to full color) dynamically that + will usually lead to the entire extended framebuffer being resent + which can take a long time over very slow links: it may be better to + reconnect and reset the format right after doing so. x11vnc will try + to detect the format change and clear (make completely black) the + cache region. Gotcha for older Unix VNC Viewers: The older Unix VNC viewers (e.g. current TightVNC Unix Viewer) require X server backingstore to keep @@ -6285,10 +6291,10 @@ EndSection As of Feb/2009 (development tarball) there is an experimental kludge to let you build x11vnc using TurboVNC's modified TightVNC encoding. - [540]TurboVNC is part of the [541]VirtualGL project. It does two main + [541]TurboVNC is part of the [542]VirtualGL project. It does two main things to speed up the TightVNC encoding: * A fast proprietary JPEG implemention is used (Intel IPP on x86) - instead of the usual libjpeg implementation. [542]TurboJPEG is an + instead of the usual libjpeg implementation. [543]TurboJPEG is an interface library, libturbojpeg, provided by the project that achieves this. * It eliminates bottlenecks, overheads, wait-times in the TightVNC @@ -6297,12 +6303,12 @@ EndSection TurboVNC works very well over LAN and fast Broadband. When using it with x11vnc in such a situation you may want to dial down the delays, - e.g. "[543]-wait 5" and "[544]-defer 5" (or even a smaller setting) to + e.g. "[544]-wait 5" and "[545]-defer 5" (or even a smaller setting) to poll and pump things out more quickly. See the instructions in "x11vnc/misc/turbovnc/README" for how to build x11vnc with TurboVNC support. You will also need to download the - [545]TurboJPEG software. + [546]TurboJPEG software. In brief the steps look like this: cd x11vnc-x.y.z/x11vnc/misc/turbovnc @@ -6312,12 +6318,17 @@ EndSection make AM_LDFLAGS='-lturbojpeg' where you replace "/DIR" with the directory containing libturbojpeg.so - you downloaded separately. If you try it, let us know how it goes. If - it works out well enough TurboVNC support will be integrated into - x11vnc and more of its tuning features will be implemented. Support in - [546]SSVNC would also be added. + you downloaded separately. If it works out well enough TurboVNC + support will be integrated into x11vnc and more of its tuning features + will be implemented. Support for TurboVNC in [547]SSVNC has been added + as an experiment as well. If you try either one, let us know how it + went. + + There also may be some Linux.i686 and Darwin.i386 x11vnc binaries in + the [548]misc. bins directory. For other platforms you will need to + compile yourself. - Potential Slowdown: As we describe [547]elsewhere, unless you use + Potential Slowdown: As we describe [549]elsewhere, unless you use x11vnc with an X server using, say, NVidia proprietary drivers (or a virtual X server like Xvfb or Xdummy, or in ShadowFB mode), then the read rate from the graphics card can rather slow (e.g. 10 MB/sec) and @@ -6357,23 +6368,23 @@ EndSection 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 "[548]-cursor X" option that + A simple kludge is provided by the "[550]-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 "[549]-cursor some" option for + work for those cases. Also see the "[551]-cursor some" option for additional kludges. Note that as of Aug/2004 on Solaris using the SUN_OVL overlay extension and IRIX, x11vnc can show the correct mouse cursor when the - [550]-overlay option is supplied. See [551]this FAQ for more info. + [552]-overlay option is supplied. See [553]this FAQ for more info. Also as of Dec/2004 XFIXES X extension support has been added to allow exact extraction of the mouse cursor shape. 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 - [552]Solaris 10. + [554]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 @@ -6381,7 +6392,7 @@ EndSection situations where the 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. [553]Details can be found here. + hidden alpha channel data under 32bpp. [555]Details can be found here. Q-80: When using XFIXES cursorshape mode, some of the cursors look @@ -6414,17 +6425,17 @@ EndSection 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 "[554]-alphacut n" option lets + course!) some tunable parameters. The "[556]-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 "[555]-alphafrac f" option tries to correct individual + 240. The "[557]-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 [556]-alpharemove that is useful for + Finally, there is an option [558]-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 @@ -6450,10 +6461,10 @@ EndSection 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 [557]-nocursorshape x11vnc option. In this case the cursor is + with the [559]-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 [558]-noalphablend option to disable this + the x11vnc side. Use the [560]-noalphablend option to disable this behavior (always approximate transparent cursors with opaque RGB values). @@ -6477,7 +6488,7 @@ EndSection example on how to change the Windows TightVNC viewer to achieve the same thing (send me the patch if you get that working). - This patch is applied to the [559]Enhanced TightVNC Viewer (SSVNC) + This patch is applied to the [561]Enhanced TightVNC Viewer (SSVNC) package we provide. [Mouse Pointer] @@ -6485,9 +6496,9 @@ EndSection Q-82: 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 [560]tightvnc extension + This default takes advantage of a [562]tightvnc extension (CursorShapeUpdates) that allows specifying a cursor image shape for - the local VNC viewer. You may disable it with the [561]-nocursor + the local VNC viewer. You may disable it with the [563]-nocursor option to x11vnc if your viewer does not have this extension. Note: as of Aug/2004 this should be fixed: the default for @@ -6501,17 +6512,17 @@ EndSection clients (i.e. passive viewers can see the mouse cursor being moved around by another viewer)? - Use the [562]-cursorpos option when starting x11vnc. A VNC viewer must + Use the [564]-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 -cursorpos - is the default. See also [563]-nocursorpos and [564]-nocursorshape. + is the default. See also [565]-nocursorpos and [566]-nocursorshape. Q-84: 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: [565]-buttonmap + You can remap the mouse buttons via something like: [567]-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. @@ -6519,7 +6530,7 @@ EndSection 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 [566]-debug_pointer option prints out much info for + Note that the [568]-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 @@ -6541,7 +6552,7 @@ EndSection 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 [567]-buttonmap but rather configuring the X server + consider not using [569]-buttonmap but rather configuring the X server to think it has a mouse with 5 buttons even though the physical mouse does not. (e.g. 'Option "ZAxisMapping" "4 5"'). @@ -6571,7 +6582,7 @@ EndSection Q-85: How can I get my AltGr and Shift modifiers to work between keyboards for different languages? - The option [568]-modtweak should help here. It is a mode that monitors + The option [570]-modtweak should help here. 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. @@ -6580,20 +6591,20 @@ EndSection 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 [569]this FAQ for more info). Without + not exist on the keyboard (see [571]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 [570]FAQ about the -xkb option for a more powerful method + Also see the [572]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 - [571]-debug_keyboard option prints out much info for every keystroke + [573]-debug_keyboard option prints out much info for every keystroke and so can be useful debugging things. Note that one user had a strange setup and none of the above helped. - His solution was to disable all of the above and use [572]-nomodtweak. + His solution was to disable all of the above and use [574]-nomodtweak. This is the simplest form of keystroke insertion and it actually solved the problem. Try it if the other options don't help. @@ -6606,9 +6617,9 @@ EndSection (e.g. pc105 in the XF86Config file when it should be something else, say pc104). - Short Cut: Try the [573]-xkb or [574]-sloppy_keys options and see if + Short Cut: Try the [575]-xkb or [576]-sloppy_keys options and see if that helps the situation. The discussion below is a bit outdated (e.g. - [575]-modtweak is now the default) but it is useful reference for + [577]-modtweak is now the default) but it is useful reference for various tricks and so is kept. @@ -6651,17 +6662,17 @@ EndSection -remap less-comma These are convenient in that they do not modify the actual X server - settings. The former ([576]-modtweak) is a mode that monitors the + settings. The former ([578]-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 ([577]-remap less-comma) is an immediate remapping of the + The latter ([579]-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 [578]FAQ about the -xkb option as a possible workaround + See also the [580]FAQ about the -xkb option as a possible workaround using the XKEYBOARD extension. - Note that the [579]-debug_keyboard option prints out much info for + Note that the [581]-debug_keyboard option prints out much info for every keystroke to aid debugging keyboard problems. @@ -6669,7 +6680,7 @@ EndSection less than) instead I get "<," (i.e. an extra comma). This is likely because you press "Shift" then "<" but then released - the Shift key before releasing the "<". Because of a [580]keymapping + the Shift key before releasing the "<". Because of a [582]keymapping ambiguity the last event "< up" is interpreted as "," because that key unshifted is the comma. @@ -6677,9 +6688,9 @@ EndSection characters: in general it can happen whenever the Shift key is released early. - This should not happen in [581]-xkb mode, because it works hard to + This should not happen in [583]-xkb mode, because it works hard to resolve the ambiguities. If you do not want to use -xkb, try the - option [582]-sloppy_keys to attempt a similar type of algorithm. + option [584]-sloppy_keys to attempt a similar type of algorithm. One user had this problem for Italian and German keyboards with the key containing ":" and "." When he typed ":" he would get an extra "." @@ -6707,7 +6718,7 @@ EndSection 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 [583]-modtweak + This all worked fine with x11vnc running with the [585]-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 @@ -6724,7 +6735,7 @@ EndSection * there is a new option -xkb to use the XKEYBOARD extension API to do the Modifier key tweaking. - The [584]-xkb option seems to fix all of the missing keys: "@", "<", + The [586]-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 @@ -6732,7 +6743,7 @@ EndSection debugging output (send it along with any problems you report). Update: as of Jun/2005 x11vnc will try to automatically enable - [585]-xkb if it appears that would be beneficial (e.g. if it sees any + [587]-xkb if it appears that would be beneficial (e.g. if it sees any of "@", "<", ">", "[" and similar keys are mapped in a way that needs the -xkb to access them). To disable this automatic check use -noxkb. @@ -6747,7 +6758,7 @@ EndSection 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: - [586]-skip_keycodes 93 + [588]-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 @@ -6765,16 +6776,16 @@ EndSection 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 [587]-remap x11vnc option: + created using the [589]-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 - [588]-add_keysyms option in the next paragraph. - Update: for convenience "[589]-remap DEAD" does many of these + [590]-add_keysyms option in the next paragraph. + Update: for convenience "[591]-remap DEAD" does many of these mappings at once. - * To complement the above workaround using the [590]-remap, an - option [591]-add_keysyms was added. This option instructs x11vnc + * To complement the above workaround using the [592]-remap, an + option [593]-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 @@ -6793,7 +6804,7 @@ EndSection 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) [592]-norepeat x11vnc option. You will still + use the new (Jul/2004) [594]-norepeat x11vnc option. You will still have autorepeating because that is taken care of on your VNC viewer side. @@ -6817,7 +6828,7 @@ EndSection 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 [593]-norepeat (which has since Dec/2004 been + needed, or to use the [595]-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 @@ -6828,7 +6839,7 @@ EndSection keystrokes!! Are you using x11vnc to log in to an X session via display manager? - (as described in [594]this FAQ) If so, x11vnc is starting before your + (as described in [596]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 @@ -6876,11 +6887,11 @@ EndSection pressed one. You need to do this for both the left and right Shift, Alt, Control, etc. keys to be sure. - You can also use the [595]-clear_mods option to try to clear all of + You can also use the [597]-clear_mods option to try to clear all of the modifier keys at x11vnc startup. You will still have to be careful that you do not leave the modifier key pressed down during your session. It is difficult to prevent this problem from occurring (short - of using [596]-remap to prevent sending all of the problem modifier + of using [598]-remap to prevent sending all of the problem modifier keys, which would make the destkop pretty unusable). During a session these x11vnc remote control commands can also help: @@ -6893,16 +6904,16 @@ EndSection Num_Lock down. When these are locked on the remote side it can sometimes lead to strange desktop behavior (e.g. cannot drag or click on windows). As above you may not notice this because the lock isn't - down on the local (Viewer) side. See [597]this FAQ on lock keys - problem. These options may help avoid the problem: [598]-skip_lockkeys - and [599]-capslock. See also [600]-clear_all. + down on the local (Viewer) side. See [599]this FAQ on lock keys + problem. These options may help avoid the problem: [600]-skip_lockkeys + and [601]-capslock. See also [602]-clear_all. Q-92: The machine where I run x11vnc has an AltGr key, but the local 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 "[601]-remap Super_R-Mode_switch" x11vnc option may + Something like "[603]-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)). @@ -6925,7 +6936,7 @@ EndSection 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 [602]-remap Alt_L-Meta_L to x11vnc may be sufficient for ones + the [604]-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 in Unix. @@ -6945,7 +6956,7 @@ EndSection and similar triple mappings (with two in the AltGr/Mode_switch group) of a keysum to a single keycode. - Use the [603]-nomodtweak option as a workaround. You can also use + Use the [605]-nomodtweak option as a workaround. You can also use xmodmap to correct these mappings in the server, e.g.: xmodmap -e "keycode 47 = 3 numbersign" @@ -6959,7 +6970,7 @@ EndSection 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 [604]-remap + have x11vnc do the remapping. This can be done via the [606]-remap option using the fake "keysyms" Button1, Button2, etc. as the "to" keys (i.e. the ones after the "-") @@ -6968,7 +6979,7 @@ EndSection button "paste" because (using XFree86/Xorg Emulate3Buttons) you have to click both buttons on the touch pad at the same time. This remapping: - [605]-remap Super_R-Button2 + [607]-remap Super_R-Button2 maps the Super_R "flag" key press to the Button2 click, thereby making X pasting a bit easier. @@ -6987,13 +6998,13 @@ EndSection Caps_Lock in the viewer your local machine goes into the Caps_Lock on state and sends keysym "A" say when you press "a". x11vnc will then fake things up so that Shift is held down to generate "A". The - [606]-skip_lockkeys option should help to accomplish this. For finer - grain control use something like: "[607]-remap Caps_Lock-None". + [608]-skip_lockkeys option should help to accomplish this. For finer + grain control use something like: "[609]-remap Caps_Lock-None". - Also try the [608]-nomodtweak and [609]-capslock options. + Also try the [610]-nomodtweak and [611]-capslock options. Another useful option that turns off any Lock keys on the remote side - at startup and end is the [610]-clear_all option. During a session you + at startup and end is the [612]-clear_all option. During a session you can run these remote control commands to modify the Lock keys: x11vnc -R clear_locks x11vnc -R clear_all @@ -7022,7 +7033,7 @@ EndSection There may also be scaling viewers out there (e.g. TightVNC or UltraVNC on Windows) that automatically shrink or expand the remote framebuffer to fit the local display. Especially for hand-held devices. See also - [611]the next FAQ on x11vnc scaling. + [613]the next FAQ on x11vnc scaling. Q-98: Does x11vnc support server-side framebuffer scaling? (E.g. to @@ -7030,7 +7041,7 @@ EndSection As of Jun/2004 x11vnc provides basic server-side scaling. It is a global scaling of the desktop, not a per-client setting. To enable it - use the "[612]-scale fraction" option. "fraction" can either be a + use the "[614]-scale fraction" option. "fraction" can either be a floating point number (e.g. -scale 0.75) or the alternative m/n fraction notation (e.g. -scale 3/4). Note that if fraction is greater than one the display is magnified. @@ -7055,7 +7066,7 @@ EndSection 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 - [613]applications. Since with integer scale factors the framebuffers + [615]applications. Since with integer scale factors the framebuffers become huge and scaling operations time consuming, be sure to use ":nb" for the fastest response. @@ -7081,7 +7092,7 @@ EndSection 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 ([614]-rfbport option, + different scalings listening on separate ports ([616]-rfbport option, etc.). Update: As of May/2006 x11vnc also supports the UltraVNC server-side @@ -7091,8 +7102,8 @@ EndSection "-rfbversion 3.6" for this to be recognized by UltraVNC viewers. BTW, whenever you run two or more x11vnc's on the same X display and - use the [615]GUI, then to avoid all of the x11vnc's simultaneously - answering the gui you will need to use something like [616]"-connect + use the [617]GUI, then to avoid all of the x11vnc's simultaneously + answering the gui you will need to use something like [618]"-connect file1 -gui ..." with different connect files for each x11vnc you want to control via the gui (or remote-control). The "-connect file1" usage gives separate communication channels between a x11vnc process and the @@ -7101,7 +7112,7 @@ EndSection Update: As of Mar/2005 x11vnc now scales the mouse cursor with the same scale factor as the screen. If you don't want that, use the - [617]"-scale_cursor frac" option to set the cursor scaling to a + [619]"-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). @@ -7129,21 +7140,21 @@ EndSection screen is not 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 [618]-blackout x11vnc option + may be distracting to the viewer. The [620]-blackout x11vnc option allows you to blacken-out rectangles by manually specifying their WxH+X+Y geometries. If your system has the libXinerama library, the - [619]-xinerama x11vnc option can be used to have it automatically + [621]-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). Update: - [620]-xinerama is now on by default. + [622]-xinerama is now on by default. 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 [621]-xwarppointer + of the large display. If this happens try using the [623]-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 - Xinerama is enabled). Update: As of Dec/2006 [622]-xwarppointer will + Xinerama is enabled). Update: As of Dec/2006 [624]-xwarppointer will be applied automatically if Xinerama is detected. To disable use: -noxwarppointer @@ -7166,23 +7177,23 @@ EndSection 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 [623]FAQ to increase the limit. It - is probably also a good idea to run with the [624]-onetile option in + /etc/system as mentioned in another [625]FAQ to increase the limit. It + is probably also a good idea to run with the [626]-onetile option in this case (to limit each x11vnc to 3 shm segments), or even - [625]-noshm to use no shm segments. + [627]-noshm to use no shm segments. Q-101: Can x11vnc show only a portion of the display? (E.g. for a special purpose application or a very large screen). - As of Mar/2005 x11vnc has the "[626]-clip WxH+X+Y" option to select a + As of Mar/2005 x11vnc has the "[628]-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. - One user used -clip to split up a large [627]Xinerama screen into two + One user used -clip to split up a large [629]Xinerama screen into two more managable smaller screens. This also works to view a sub-region of a single application window if - the [628]-id or [629]-sid options are used. The offset is measured + the [630]-id or [631]-sid options are used. The offset is measured from the upper left corner of the selected window. @@ -7191,7 +7202,7 @@ EndSection just seems to crash. As of Dec/2004 x11vnc supports XRANDR. You enable it with the - [630]-xrandr option to make x11vnc monitor XRANDR events and also trap + [632]-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. @@ -7201,9 +7212,9 @@ EndSection then the 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 [631]-padgeom option to make the region big + viewers you can try the [633]-padgeom option to make the region big enough to hold all resizes and rotations. We have fixed this problem - for the TightVNC Viewer on Unix: [632]SSVNC + for the TightVNC Viewer on Unix: [634]SSVNC If you specify "-xrandr newfbsize" then vnc viewers that do not support NewFBSize will be disconnected before the resize. If you @@ -7215,7 +7226,7 @@ EndSection reflect the screen that the VNC viewers see? (e.g. for a handheld whose screen is rotated 90 degrees). - As of Jul/2006 there is the [633]-rotate option allow this. E.g's: + As of Jul/2006 there is the [635]-rotate option allow this. E.g's: "-rotate +90", "-rotate -90", "-rotate x", etc. @@ -7280,13 +7291,13 @@ EndSection This may be a bug in kdesktop_lock. For now the only workaround is to disable the screensaver. You can try using another one such as - straight xscreensaver (see the instructions [634]here for how to + straight xscreensaver (see the instructions [636]here for how to disable kdesktop_lock). If you have more info on this or see it outside of KDE please let us know. Update: It appears this is due to kdesktop_lock enabling the screen saver when the Monitor is in DPMS low-power state (e.g. standby, - suspend, or off). In Nov/2006 the x11vnc [635]-nodpms option was added + suspend, or off). In Nov/2006 the x11vnc [637]-nodpms option was added as a workaround. Normally it is a good thing that the monitor powers down (since x11vnc can still poll the framebuffer in this state), but if you experience the kdesktop_lock problem you can specify the @@ -7302,16 +7313,16 @@ EndSection This appears to be because the 3D OpenGL/GLX hardware screen updates do not get reported via the XDAMAGE mechanism. So this is a bug in - [636]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video + [638]beryl/compiz or XDAMAGE/Xorg or the (possibly 3rd party) video card driver. - As a workaround apply the [637]-noxdamage option. As of Feb/2007 + As a workaround apply the [639]-noxdamage option. As of Feb/2007 x11vnc will try to autodetect the problem and disable XDAMAGE if is appears to be missing a lot of updates. But if you know you are using - beryl you might as well always supply -noxdamage. Thanks to [638]this + beryl you might as well always supply -noxdamage. Thanks to [640]this user who reported the problem and discovered the workaround. - A developer for [639]MiniMyth reports that the 'alphapulse' tag of the + A developer for [641]MiniMyth reports that the 'alphapulse' tag of the theme G.A.N.T. can also cause problems, and should be avoided when using VNC. @@ -7331,9 +7342,9 @@ EndSection * 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 [640]this FAQ + desktop in a separate Virtual Console (e.g. VC 8) (see [642]this FAQ on VC's for background). Unfortunately, this Fullscreen VC is not an X - server. So x11vnc cannot access it (however, [641]see this discussion + server. So x11vnc cannot access it (however, [643]see this discussion of -rawfb for a possible workaround). x11vnc works fine with "Normal X application window" and "Quick-Switch mode" because these use X. @@ -7354,13 +7365,13 @@ EndSection improve 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 [642]is in the active VC. + as long as the VMWare X session [644]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) window-id 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 [643]-id windowid option. The + the VMWare menu buttons) by use of the [645]-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 @@ -7376,10 +7387,10 @@ EndSection controlled) via VNC with x11vnc? As of Apr/2005 there is support for this. Two options were added: - "[644]-rawfb string" (to indicate the raw frame buffer device, file, - etc. and its parameters) and "[645]-pipeinput command" (to provide an + "[646]-rawfb string" (to indicate the raw frame buffer device, file, + etc. and its parameters) and "[647]-pipeinput command" (to provide an external program that will inject or otherwise process mouse and - keystroke input). Some useful [646]-pipeinput schemes, VID, CONSOLE, + keystroke input). Some useful [648]-pipeinput schemes, VID, CONSOLE, and UINPUT, have since been built into x11vnc for convenience. This non-X mode for x11vnc is somewhat experimental because it is so @@ -7419,9 +7430,9 @@ EndSection access method). Only use file if map isn't working. BTW, "mmap" is an alias for "map" and if you do not supply a type and the file exists, map is assumed (see the -help output and below for some exceptions to - this). The "snap:" setting applies the [647]-snapfb option with + this). The "snap:" setting applies the [649]-snapfb option with "file:" type reading (this is useful for exporting webcams or TV tuner - video; see [648]the next FAQ for more info). + video; see [650]the next FAQ for more info). 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 @@ -7466,7 +7477,7 @@ EndSection 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, but usable. Of course - for the case of Xvfb x11vnc can poll it much better via the [649]X + for the case of Xvfb x11vnc can poll it much better via the [651]X API, but you get the idea. By default in -rawfb mode x11vnc will actually close any X display it @@ -7497,13 +7508,13 @@ minal #2) tty1-tty6), or X graphical display (usually starting at tty7). In addition to the text console other graphical ones may be viewed and interacted with as well, e.g. DirectFB or SVGAlib apps, VMWare non-X - fullscreen, or [650]Qt-embedded apps (PDAs/Handhelds). By default the + fullscreen, or [652]Qt-embedded apps (PDAs/Handhelds). By default the pipeinput mechanisms UINPUT and CONSOLE (keystrokes only) are automatically attempted in this mode under "-rawfb console". The Video4Linux Capture device, /dev/video0, etc is either a Webcam or a TV capture device and needs to have its driver enabled in the - kernel. See [651]this FAQ for details. If specified via "-rawfb Video" + kernel. See [653]this FAQ for details. If specified via "-rawfb Video" then the pipeinput method "VID" is applied (it lets you change video parameters dynamically via keystrokes). @@ -7511,10 +7522,10 @@ minal #2) also useful in testing. - All of the above [652]-rawfb options are just for viewing the raw + All of the above [654]-rawfb options are just for viewing the raw framebuffer (although some of the aliases do imply keystroke and mouse pipeinput methods). That may be enough for certain applications of - this feature (e.g. suppose a [653]video camera mapped its framebuffer + this feature (e.g. suppose a [655]video camera mapped its framebuffer into memory and you just wanted to look at it via VNC). To handle the pointer and keyboard input from the viewer users the "-pipeinput cmd" option was added to indicate a helper program to @@ -7552,7 +7563,7 @@ minal #2) 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 [654]active VC) one + view and interact with VC #2 (assuming it is the [656]active VC) one can run something like: x11vnc -rawfb map:/dev/fb0@1024x768x16 -pipeinput './vcinject.pl 2' @@ -7607,7 +7618,7 @@ minal #2) better to use the more accurate and faster LinuxVNC program. The advantage x11vnc -rawfb might have is that it can allow interaction with a non-text application, e.g. one based on SVGAlib or - [655]Qt-embedded Also, for example the [656]VMWare Fullscreen mode is + [657]Qt-embedded Also, for example the [658]VMWare Fullscreen mode is actually viewable under -rawfb and can be interacted with if uinput is enabled. @@ -7671,9 +7682,9 @@ minal #2) Q-112: Can I export via VNC a Webcam or TV tuner framebuffer using x11vnc? - Yes, this is possible to some degree with the [657]-rawfb option. + Yes, this is possible to some degree with the [659]-rawfb option. There is no X11 involved: snapshots from the video capture device are - used for the screen image data. See the [658]previous FAQ on -rawfb + used for the screen image data. See the [660]previous FAQ on -rawfb for background. For best results, use x11vnc version 0.8.1 or later. Roughly, one would do something like this: @@ -7685,7 +7696,7 @@ minal #2) snapshot to a file that you point -rawfb to; ask me if it is not clear what to do). - The "snap:" enforces [659]-snapfb mode which appears to be necessary. + The "snap:" enforces [661]-snapfb mode which appears to be necessary. The read pointer for video capture devices cannot be repositioned (which would be needed for scanline polling), but you can read a full frame of data from the device. @@ -7707,7 +7718,7 @@ minal #2) Many video4linux drivers tend to set the framebuffer to be 24bpp (as opposed to 32bpp). Since this can cause problems with VNC viewers, - etc, the [660]-24to32 option will be automatically imposed when in + etc, the [662]-24to32 option will be automatically imposed when in 24bpp. Note that by its very nature, video capture involves rapid change in @@ -7715,7 +7726,7 @@ minal #2) wavering in brightness is always happening. This can lead to much network bandwidth consumption for the VNC traffic and also local CPU and I/O resource usage. You may want to experiment with "dialing down" - the framerate via the [661]-wait, [662]-slow_fb, or [663]-defer + the framerate via the [663]-wait, [664]-slow_fb, or [665]-defer options. Decreasing the window size and bpp also helps. @@ -7804,7 +7815,7 @@ minal #2) format to HI240, RGB565, RGB24, RGB32, RGB555, and GREY respectively. See -rawfb video for details. - See also the [664]-freqtab option to supply your own xawtv channel to + See also the [666]-freqtab option to supply your own xawtv channel to frequency mappings for your country (only ntsc-cable-us is built into x11vnc). @@ -7813,7 +7824,7 @@ minal #2) running on my handheld or PC using the Linux console framebuffer (i.e. not X11)? - Yes, the basic method for this is the [665]-rawfb scheme where the + Yes, the basic method for this is the [667]-rawfb scheme where the Linux console framebuffer (usually /dev/fb0) is polled and the uinput driver is used to inject keystrokes and mouse input. Often you will just have to type: @@ -7826,7 +7837,7 @@ minal #2) x11vnc -rawfb /dev/fb0@640x480x16 Also, to force usage of the uinput injection method use "-pipeinput - UINPUT". See the [666]-pipeinput description for tunable parameters, + UINPUT". See the [668]-pipeinput description for tunable parameters, etc. One problem with the x11vnc uinput scheme is that it cannot guess the @@ -7842,7 +7853,7 @@ minal #2) Even with the correct acceleration setting there is still some drift (probably because of the mouse threshold where the acceleration kicks in) and so x11vnc needs to reposition the cursor from 0,0 about 5 - times a second. See the [667]-pipeinput UINPUT option for tuning + times a second. See the [669]-pipeinput UINPUT option for tuning parameters that can be set (there are some experimental thresh=N tuning parameters as well) @@ -7877,7 +7888,7 @@ minal #2) Q-114: Now that non-X11 devices can be exported via VNC using x11vnc, can I build it with no dependencies on X11 header files and libraries? - Yes, as of Jul/2006 x11vnc enables building for [668]-rawfb only + Yes, as of Jul/2006 x11vnc enables building for [670]-rawfb only support. Just do something like when building: ./configure --without-x (plus any other flags) make @@ -7893,11 +7904,11 @@ minal #2) Yes, since Nov/2006 in the development tree (x11vnc-0.8.4 tarball) there is support for native Mac OS X Aqua/Quartz displays using the - [669]-rawfb mechanism described above. The mouse and keyboard input is + [671]-rawfb mechanism described above. The mouse and keyboard input is achieved via Mac OS X API's. - So you can use x11vnc as an alternative to [670]OSXvnc (aka Vine - Server), or [671]Apple Remote Desktop (ARD). Perhaps there is some + So you can use x11vnc as an alternative to [672]OSXvnc (aka Vine + Server), or [673]Apple Remote Desktop (ARD). Perhaps there is some x11vnc feature you'd like to use on Mac OS X, etc. For a number of activities (e.g. window drags) it seems to be faster than OSXvnc. @@ -7907,7 +7918,7 @@ minal #2) (XDarwin) running on Mac OS X (people often install this software to display remote X11 apps on their Mac OS X system, or use some old favorites locally such as xterm). However in this case x11vnc will - only work reasonably in single window [672]-id windowid mode (and the + only work reasonably in single window [674]-id windowid mode (and the window may need to have mouse focus). If you do not have the DISPLAY env. variable set, x11vnc will assume @@ -7925,9 +7936,9 @@ minal #2) ./configure --without-x make - Win2VNC/x2vnc: One handy use is to use the [673]-nofb mode to + Win2VNC/x2vnc: One handy use is to use the [675]-nofb mode to redirect mouse and keyboard input to a nearby Mac (i.e. one to the - side of your desk) via [674]x2vnc or Win2VNC. See [675]this FAQ for + side of your desk) via [676]x2vnc or Win2VNC. See [677]this FAQ for more info. Options: Here are the Mac OS X specific x11vnc options: @@ -8001,13 +8012,13 @@ rm -f $tmp performance for the case of a large number of simultaneous VNC viewers (e.g. classroom broadcasting or a large demo)? - Yes, as of Feb/2007 there is the "[676]-reflect host:N" option to + Yes, as of Feb/2007 there is the "[678]-reflect host:N" option to connect to the VNC server "host:N" (either another x11vnc or any other VNC server) and re-export it. VNC viewers then connect to the x11vnc(s) running -reflect. The -reflect option is the same as: "-rawfb vnc:host:N". See the - [677]-rawfb description under "VNC HOST" for more details. + [679]-rawfb description under "VNC HOST" for more details. You can replace "host:N" with "listen" or "listen:port" for reverse connections. @@ -8068,18 +8079,18 @@ rm -f $tmp re-exports via VNC to its clients C). However, CopyRect and CursorShape encodings are preserved in the reflection and that helps. Dragging windows with the mouse can be a problem (especially if S is - not doing wireframing somehow, consider [678]-nodragging if the + not doing wireframing somehow, consider [680]-nodragging if the problem is severe) For a really fast reflector/repeater it would have to be implemented from scratch with performance in mind. See these other projects: - [679]http://sourceforge.net/projects/vnc-reflector/, - [680]http://www.tightvnc.com/projector/ (closed source?), + [681]http://sourceforge.net/projects/vnc-reflector/, + [682]http://www.tightvnc.com/projector/ (closed source?), Automation via Reverse Connections: Instead of having the R's connect directly to S and then the C's connect directly to the R they should use, some convenience can be achieved by using reverse - connections (the x11vnc "[681]"-connect host1,host2,..." option). + connections (the x11vnc "[683]"-connect host1,host2,..." option). Suppose all the clients "C" are started up in Listen mode: client1> vncviewer -listen client2> vncviewer -listen @@ -8138,7 +8149,7 @@ rm -f $tmp If the Solaris install is an older X-based one, there will be a menu for you to get a terminal window. From that window you might be able to retrieve x11vnc.static via wget, scp, or ftp. Remember to do "chmod - 755 ./x11vnc.static" and then find the -auth file as in [682]this FAQ. + 755 ./x11vnc.static" and then find the -auth file as in [684]this FAQ. If it is a Linux install that uses an X server (e.g. SuSE and probably Fedora), then you can often get a shell by pressing Ctrl-Alt-F2 or @@ -8147,7 +8158,7 @@ rm -f $tmp wget http://192.168.0.22/x11vnc.static chmod 755 ./x11vnc.static - Find the name of the auth file as in [683]this FAQ. (maybe run "ps + Find the name of the auth file as in [685]this FAQ. (maybe run "ps wwwwaux | grep auth"). Then run it like this: ./x11vnc.static -forever -nopw -display :0 -auth /tmp/wherever/the/authfile @@ -8156,7 +8167,7 @@ rm -f $tmp the display being :1, etc. If there is a firewall blocking incoming connections during the - install, use the [684]"-connect hostname" option option for a reverse + install, use the [686]"-connect hostname" option option for a reverse connection to the hostname running the VNC viewer in listen mode. Debian based installs are either console-text or console-framebuffer @@ -8205,11 +8216,11 @@ rm -f $tmp As of Jan/2004 x11vnc supports the "CutText" part of the rfb protocol. Furthermore, x11vnc is able to hold the PRIMARY and CLIPBOARD selection (Xvnc does not seem to do this). If you don't want the - Clipboard/Selection exchanged use the [685]-nosel option. If you don't + Clipboard/Selection exchanged use the [687]-nosel option. If you don't want the PRIMARY selection to be polled for changes use the - [686]-noprimary option. (with a similar thing for CLIPBOARD). You can - also fine-tune it a bit with the [687]-seldir dir option and also - [688]-input. + [688]-noprimary option. (with a similar thing for CLIPBOARD). You can + also fine-tune it a bit with the [689]-seldir dir option and also + [690]-input. You may need to watch out for desktop utilities such as KDE's "Klipper" that do odd things with the selection, clipboard, and @@ -8221,7 +8232,7 @@ rm -f $tmp Yes, it is possible with a number of tools that record VNC and transform it to swf format or others. One such popular tool is - [689]pyvnc2swf. There are a number of [690]tutorials (broken link?) on + [691]pyvnc2swf. There are a number of [692]tutorials (broken link?) on how to do this. Another option is to use the vnc2mpg that comes in the LibVNCServer package. An important thing to remember when doing this is that tuning @@ -8236,11 +8247,11 @@ rm -f $tmp (and Windows viewers only support filetransfer it appears... but they do work to some degree under Wine on Linux). - The [691]SSVNC Unix VNC viewer supports UltraVNC file transfer by use + The [693]SSVNC Unix VNC viewer supports UltraVNC file transfer by use of a Java helper program. TightVNC file transfer is off by default, if you want to enable it use - the [692]-tightfilexfer option. + the [694]-tightfilexfer option. UltraVNC file transfer is off by default, to enable it use something like "-rfbversion 3.6 -permitfiletransfer" @@ -8263,7 +8274,7 @@ rm -f $tmp IMPORTANT: please understand if -ultrafilexfer or -tightfilexfer is specified and you run x11vnc as root for, say, inetd or display manager (gdm, kdm, ...) access and you do not have it switch users via - the [693]-users option, then VNC Viewers that connect are able to do + the [695]-users option, then VNC Viewers that connect are able to do filetransfer reads and writes as *root*. The UltraVNC and TightVNC settings can be toggled on and off inside @@ -8282,7 +8293,7 @@ rm -f $tmp these extensions you will need to supply this option to x11vnc: -rfbversion 3.6 - Or use [694]-ultrafilexfer which is an alias for the above option and + Or use [696]-ultrafilexfer which is an alias for the above option and "-permitfiletransfer". UltraVNC evidently treats any other RFB version number as non-UltraVNC. @@ -8294,14 +8305,14 @@ rm -f $tmp * 1/n Server Scaling * rfbEncodingUltra compression encoding - The [695]SSVNC Unix VNC viewer supports these UltraVNC extensions. + The [697]SSVNC Unix VNC viewer supports these UltraVNC extensions. - To disable SingleWindow and ServerInput use [696]-noultraext (the + To disable SingleWindow and ServerInput use [698]-noultraext (the others are managed by LibVNCServer). See this option too: - [697]-noserverdpms. + [699]-noserverdpms. - Also, the [698]UltraVNC repeater proxy is supported for use with - reverse connections: "[699]-connect repeater://host:port+ID:NNNN". Use + Also, the [700]UltraVNC repeater proxy is supported for use with + reverse connections: "[701]-connect repeater://host:port+ID:NNNN". Use it for both plaintext and SSL connections. This mode can send any string before switching to the VNC protocol, and so could be used with other proxy/gateway tools. @@ -8312,12 +8323,12 @@ rm -f $tmp reverse vnc connection from their Unix desktop to a helpdesk operator's VNC Viewer. - Yes, UltraVNC's [700]Single Click (SC) mode can be emulated fairly + Yes, UltraVNC's [702]Single Click (SC) mode can be emulated fairly well on Unix. We use the term "helpdesk" below, but it could be any sort of remote assistance you want to set up, e.g. something for Unix-using friends - or family to use. This includes [701]Mac OS X. + or family to use. This includes [703]Mac OS X. Assume you create a helpdesk directory "hd" on your website: http://www.mysite.com/hd (any website that you can upload files to @@ -8373,7 +8384,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc So I guess this is about 3-4 clicks (start a terminal and paste) and pressing "Enter" instead of "single click"... - See [702]this page for some variations on this method, e.g. how to add + See [704]this page for some variations on this method, e.g. how to add a password, SSL Certificates, etc. @@ -8385,11 +8396,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc A bit of obscurity security could be put in with a -passwd, -rfbauth options, etc. (note that x11vnc will require a password even for - reverse connections). More info [703]here. + reverse connections). More info [705]here. Firewalls: If the helpdesk (you) with the vncviewer is behind a - NAT/Firewall/Router the [704]router will have to be configured to + NAT/Firewall/Router the [706]router will have to be configured to redirect a port (i.e. 5500 or maybe different one if you like) to the vncviewer machine. If the vncviewer machine also has its own host-level firewall, you will have to open up the port there as well. @@ -8399,7 +8410,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc configuring a router to do a port redirection (i.e. on your side, the HelpDesk). To avoid modifying either firewall/router, one would need some public (IP address reachable on the internet) redirection/proxy - service. Perhaps such a thing exists. [705]http://sc.uvnc.com provides + service. Perhaps such a thing exists. [707]http://sc.uvnc.com provides this service for their UltraVNC Single Click users. @@ -8435,7 +8446,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc As of Apr/2007 x11vnc supports reverse connections in SSL and so we can do this. On the Helpdesk side (Viewer) you will need STUNNEL or - better use the [706]Enhanced TightVNC Viewer (SSVNC) package we + better use the [708]Enhanced TightVNC Viewer (SSVNC) package we provide that automates all of the SSL for you. To do this create a file named "vncs" in the website "hd" directory @@ -8465,11 +8476,11 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc with the hostnames or IP addresses customized to your case. - The only change from the "vnc" above is the addition of the [707]-ssl + The only change from the "vnc" above is the addition of the [709]-ssl option to x11vnc. This will create a temporary SSL cert: openssl(1) will need to be installed on the user's end. A fixed SSL cert file could be used to avoid this (and provide some authentication; more - info [708]here.) + info [710]here.) The naive user will be doing this: wget -qO - http://www.mysite.com/hd/vncs | sh - @@ -8478,7 +8489,7 @@ chmod 755 ./x11vnc # platform, use $webhost/`uname`/x11vnc But before that, the helpdesk operator needs to have "vncviewer -listen" running as before, however he needs an SSL tunnel at his end. - The easiest way to do this is use [709]Enhanced TightVNC Viewer + The easiest way to do this is use [711]Enhanced TightVNC Viewer (SSVNC). Start it, and select Options -> 'Reverse VNC Connection (-listen)'. Then UN-select 'Verify All Certs' (this can be enabled later if you want; you'll need the x11vnc SSL certificate), and click @@ -8508,7 +8519,7 @@ connect = localhost:5501 answer the prompts with whatever you want; you can take the default for all of them if you like. The openssl(1) package must be installed. - See [710]this link and [711]this one too for more info on SSL certs. + See [712]this link and [713]this one too for more info on SSL certs. This creates $HOME/.vnc/certs/server-self:mystunnel.pem, then you would change the "stunnel.cfg" to look something like: foreground = yes @@ -8529,7 +8540,7 @@ connect = localhost:5501 then all bets are off!. More SSL variations and info about certificates can be found - [712]here. + [714]here. OpenSSL libssl.so.0.9.7 problems: @@ -8539,7 +8550,7 @@ connect = localhost:5501 distros are currently a bit of a mess regarding which version of libssl is installed. - You will find the [713]details here. + You will find the [715]details here. Q-123: Can I (temporarily) mount my local (viewer-side) Windows/Samba @@ -8548,7 +8559,7 @@ connect = localhost:5501 You will have to use an external network redirection for this. Filesystem mounting is not part of the VNC protocol. - We show a simple [714]Samba example here. + We show a simple [716]Samba example here. First you will need a tunnel to redirect the SMB requests from the remote machine to the one you sitting at. We use an ssh tunnel: @@ -8588,7 +8599,7 @@ d,ip=127.0.0.1,port=1139 far-away> smbumount /home/fred/smb-haystack-pub At some point we hope to fold some automation for SMB ssh redir setup - into the [715]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [717]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8598,7 +8609,7 @@ d,ip=127.0.0.1,port=1139 You will have to use an external network redirection for this. Printing is not part of the VNC protocol. - We show a simple Unix to Unix [716]CUPS example here. Non-CUPS port + We show a simple Unix to Unix [718]CUPS example here. Non-CUPS port redirections (e.g. LPD) should also be possible, but may be a bit more tricky. If you are viewing on Windows SMB and don't have a local cups server it may be trickier still (see below). @@ -8680,7 +8691,7 @@ d,ip=127.0.0.1,port=1139 "localhost". At some point we hope to fold some automation for CUPS ssh redir setup - into the [717]Enhanced TightVNC Viewer (SSVNC) package we provide (as + into the [719]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep 2006 it is there for testing). @@ -8781,7 +8792,7 @@ or: the applications will fail to run because LD_PRELOAD will point to libraries of the wrong wordsize. * At some point we hope to fold some automation for esd or artsd ssh - redir setup into the [718]Enhanced TightVNC Viewer (SSVNC) package + redir setup into the [720]Enhanced TightVNC Viewer (SSVNC) package we provide (as of Sep/2006 it is there for testing). @@ -8793,14 +8804,14 @@ or: 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 [719]-nobell option. If + If you don't want to hear the beeps use the [721]-nobell option. If you want to hear the audio from the remote applications, consider - trying a [720]redirector such as esd. + trying a [722]redirector such as esd. Q-127: Does x11vnc work with IPv6? - Currently the only way to do this is via [721]inetd. You configure + Currently the only way to do this is via [723]inetd. You configure x11vnc to be run from inetd or xinetd and instruct it to listen on an IPv6 address. For xinetd the setting "flags = IPv6" will be needed. @@ -8809,7 +8820,7 @@ or: connection). Some sort of ipv4-to-ipv6 redirector tool (perhaps even a perl script) could be useful to avoid this. - Also note that not all VNC Viewers are [722]IPv6 enabled, so a + Also note that not all VNC Viewers are [724]IPv6 enabled, so a redirector could even be needed on the client side. @@ -9364,192 +9375,194 @@ References 534. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scrollcopyrect 535. http://www.karlrunge.com/x11vnc/index.html#beta-test 536. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache - 537. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop - 538. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap - 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr - 540. http://www.virtualgl.org/About/TurboVNC - 541. http://www.virtualgl.org/ - 542. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 543. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 545. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 - 546. http://www.karlrunge.com/x11vnc/ssvnc.html - 547. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow - 548. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 549. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor - 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay - 551. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode - 552. http://www.karlrunge.com/x11vnc/index.html#solaris10-build - 553. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks - 554. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut - 555. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac - 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove - 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend - 559. http://www.karlrunge.com/x11vnc/ssvnc.html - 560. http://www.tightvnc.com/ - 561. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor - 562. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos - 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos - 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape - 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 537. http://www.karlrunge.com/x11vnc/ssvnc.html + 538. http://www.karlrunge.com/x11vnc/ssvnc.html#ycrop + 539. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_no_rootpixmap + 540. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ncache_cr + 541. http://www.virtualgl.org/About/TurboVNC + 542. http://www.virtualgl.org/ + 543. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 544. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 545. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 546. http://sourceforge.net/project/showfiles.php?group_id=117509&package_id=166100 + 547. http://www.karlrunge.com/x11vnc/ssvnc.html + 548. http://www.karlrunge.com/x11vnc/bins + 549. http://www.karlrunge.com/x11vnc/index.html#fb_read_slow + 550. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 551. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursor + 552. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-overlay + 553. http://www.karlrunge.com/x11vnc/faq.html#infaq_the-overlay-mode + 554. http://www.karlrunge.com/x11vnc/index.html#solaris10-build + 555. http://www.karlrunge.com/x11vnc/faq.html#faq-xfixes-alpha-hacks + 556. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphacut + 557. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alphafrac + 558. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-alpharemove + 559. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape + 560. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noalphablend + 561. http://www.karlrunge.com/x11vnc/ssvnc.html + 562. http://www.tightvnc.com/ + 563. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursor + 564. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-cursorpos + 565. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorpos + 566. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nocursorshape 567. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap - 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 569. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 570. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 571. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 572. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 578. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak - 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard - 580. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless - 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 582. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys - 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak - 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb - 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes - 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 568. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_pointer + 569. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-buttonmap + 570. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 571. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 572. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 573. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 574. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 575. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 576. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 577. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 578. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 579. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 580. http://www.karlrunge.com/x11vnc/faq.html#faq-xkbmodtweak + 581. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-debug_keyboard + 582. http://www.karlrunge.com/x11vnc/faq.html#faq-greaterless + 583. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 584. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-sloppy_keys + 585. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-modtweak + 586. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 587. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xkb + 588. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_keycodes 589. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms - 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat - 594. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods - 596. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 597. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock - 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys - 599. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 590. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 591. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 592. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 593. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-add_keysyms + 594. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 595. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-norepeat + 596. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 597. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_mods + 598. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 599. http://www.karlrunge.com/x11vnc/faq.html#faq-remap-capslock + 600. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 601. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 602. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 603. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 604. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 605. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 606. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap 607. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap - 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak - 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock - 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all - 611. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling - 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale - 613. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html - 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport - 615. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui - 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor - 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout - 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama - 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer - 623. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm - 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile - 625. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm - 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip - 627. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama - 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 629. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr - 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom - 632. http://www.karlrunge.com/x11vnc/ssvnc.html - 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate - 634. http://www.jwz.org/xscreensaver/man1.html - 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms - 636. http://www.beryl-project.org/ - 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage - 638. http://www.dslinux.org/blogs/pepsiman/?p=73 - 639. http://minimyth.org/ - 640. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 641. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 608. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-skip_lockkeys + 609. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-remap + 610. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nomodtweak + 611. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-capslock + 612. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clear_all + 613. http://www.karlrunge.com/x11vnc/faq.html#faq-scaling + 614. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale + 615. http://people.pwf.cam.ac.uk/ssb22/setup/vnc-magnification.html + 616. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rfbport + 617. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-gui + 618. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 619. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-scale_cursor + 620. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-blackout + 621. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 622. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xinerama + 623. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 624. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xwarppointer + 625. http://www.karlrunge.com/x11vnc/faq.html#faq-solshm + 626. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-onetile + 627. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noshm + 628. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-clip + 629. http://www.karlrunge.com/x11vnc/faq.html#faq-xinerama + 630. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 631. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 632. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-xrandr + 633. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-padgeom + 634. http://www.karlrunge.com/x11vnc/ssvnc.html + 635. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rotate + 636. http://www.jwz.org/xscreensaver/man1.html + 637. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodpms + 638. http://www.beryl-project.org/ + 639. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noxdamage + 640. http://www.dslinux.org/blogs/pepsiman/?p=73 + 641. http://minimyth.org/ 642. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 643. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 644. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 648. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 649. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb - 650. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 651. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 652. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 643. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 644. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 645. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 646. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 647. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 648. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 649. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 650. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 651. http://www.karlrunge.com/x11vnc/faq.html#faq-xvfb + 652. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded 653. http://www.karlrunge.com/x11vnc/faq.html#faq-video - 654. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc - 655. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded - 656. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware - 657. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 658. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb - 660. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 - 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait - 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb - 663. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer - 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab - 665. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb - 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 667. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput - 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 670. http://www.testplant.com/products/vine_server/OS_X - 671. http://www.apple.com/remotedesktop/ - 672. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 673. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id - 674. http://fredrik.hubbe.net/x2vnc.html - 675. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc - 676. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect - 677. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb - 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging - 679. http://sourceforge.net/projects/vnc-reflector/ - 680. http://www.tightvnc.com/projector/ - 681. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 682. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 683. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager - 684. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 685. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel - 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary - 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir - 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input - 689. http://www.unixuser.org/~euske/vnc2swf/ - 690. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ - 691. http://www.karlrunge.com/x11vnc/ssvnc.html - 692. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer - 693. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users - 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer - 695. http://www.karlrunge.com/x11vnc/ssvnc.html - 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext - 697. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms - 698. http://www.uvnc.com/addons/repeater.html - 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect - 700. http://www.uvnc.com/addons/singleclick.html - 701. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx - 702. http://www.karlrunge.com/x11vnc/single-click.html - 703. http://www.karlrunge.com/x11vnc/single-click.html - 704. http://www.karlrunge.com/x11vnc/index.html#firewalls - 705. http://sc.uvnc.com/ - 706. http://www.karlrunge.com/x11vnc/ssvnc.html - 707. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl - 708. http://www.karlrunge.com/x11vnc/single-click.html - 709. http://www.karlrunge.com/x11vnc/ssvnc.html + 654. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 655. http://www.karlrunge.com/x11vnc/faq.html#faq-video + 656. http://www.karlrunge.com/x11vnc/faq.html#faq-linuxvc + 657. http://www.karlrunge.com/x11vnc/faq.html#faq-qt-embedded + 658. http://www.karlrunge.com/x11vnc/faq.html#faq-vmware + 659. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 660. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 661. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-snapfb + 662. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-24to32 + 663. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-wait + 664. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-slow_fb + 665. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-defer + 666. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-freqtab + 667. http://www.karlrunge.com/x11vnc/faq.html#faq-rawfb + 668. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 669. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-pipeinput + 670. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 671. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 672. http://www.testplant.com/products/vine_server/OS_X + 673. http://www.apple.com/remotedesktop/ + 674. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 675. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-id + 676. http://fredrik.hubbe.net/x2vnc.html + 677. http://www.karlrunge.com/x11vnc/faq.html#faq-win2vnc + 678. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-reflect + 679. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-rawfb + 680. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nodragging + 681. http://sourceforge.net/projects/vnc-reflector/ + 682. http://www.tightvnc.com/projector/ + 683. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 684. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 685. http://www.karlrunge.com/x11vnc/faq.html#faq-display-manager + 686. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 687. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nosel + 688. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noprimary + 689. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-seldir + 690. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-input + 691. http://www.unixuser.org/~euske/vnc2swf/ + 692. http://wolphination.com/linux/2006/06/30/how-to-record-videos-of-your-desktop/ + 693. http://www.karlrunge.com/x11vnc/ssvnc.html + 694. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-tightfilexfer + 695. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-users + 696. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ultrafilexfer + 697. http://www.karlrunge.com/x11vnc/ssvnc.html + 698. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noultraext + 699. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-noserverdpms + 700. http://www.uvnc.com/addons/repeater.html + 701. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-connect + 702. http://www.uvnc.com/addons/singleclick.html + 703. http://www.karlrunge.com/x11vnc/faq.html#faq-macosx + 704. http://www.karlrunge.com/x11vnc/single-click.html + 705. http://www.karlrunge.com/x11vnc/single-click.html + 706. http://www.karlrunge.com/x11vnc/index.html#firewalls + 707. http://sc.uvnc.com/ + 708. http://www.karlrunge.com/x11vnc/ssvnc.html + 709. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-ssl 710. http://www.karlrunge.com/x11vnc/single-click.html - 711. http://www.karlrunge.com/x11vnc/ssl.html + 711. http://www.karlrunge.com/x11vnc/ssvnc.html 712. http://www.karlrunge.com/x11vnc/single-click.html - 713. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems - 714. http://www.samba.org/ - 715. http://www.karlrunge.com/x11vnc/ssvnc.html - 716. http://www.cups.org/ + 713. http://www.karlrunge.com/x11vnc/ssl.html + 714. http://www.karlrunge.com/x11vnc/single-click.html + 715. http://www.karlrunge.com/x11vnc/single-click.html#libssl-problems + 716. http://www.samba.org/ 717. http://www.karlrunge.com/x11vnc/ssvnc.html - 718. http://www.karlrunge.com/x11vnc/ssvnc.html - 719. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell - 720. http://www.karlrunge.com/x11vnc/faq.html#faq-sound - 721. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd - 722. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html + 718. http://www.cups.org/ + 719. http://www.karlrunge.com/x11vnc/ssvnc.html + 720. http://www.karlrunge.com/x11vnc/ssvnc.html + 721. http://www.karlrunge.com/x11vnc/x11vnc_opts.html#opt-nobell + 722. http://www.karlrunge.com/x11vnc/faq.html#faq-sound + 723. http://www.karlrunge.com/x11vnc/faq.html#faq-inetd + 724. http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html ======================================================================= http://www.karlrunge.com/x11vnc/chainingssh.html: @@ -12464,7 +12477,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.9.7 lastmod: 2009-03-07 +x11vnc: allow VNC connections to real X11 displays. 0.9.7 lastmod: 2009-03-08 x11vnc options: -display disp -auth file -N @@ -12589,7 +12602,7 @@ libvncserver-tight-extension options: % x11vnc -help -x11vnc: allow VNC connections to real X11 displays. 0.9.7 lastmod: 2009-03-07 +x11vnc: allow VNC connections to real X11 displays. 0.9.7 lastmod: 2009-03-08 (type "x11vnc -opts" to just list the options.) diff --git a/x11vnc/screen.c b/x11vnc/screen.c index 27c435b..81c6850 100644 --- a/x11vnc/screen.c +++ b/x11vnc/screen.c @@ -1063,7 +1063,7 @@ void vnc_reflect_got_copyrect(rfbClient *cl, int src_x, int src_y, int w, int h, if (dx != last_dx || dy != last_dy) { rc = fb_push_wait(0.05, FB_COPY|FB_MOD); } - if (1) fprintf(stderr, "vnc_reflect_got_copyrect: %03dx%03d+%03d+%03d %3d %3d rc=%d\n", dest_x, dest_y, w, h, dx, dy, rc); + if (0) fprintf(stderr, "vnc_reflect_got_copyrect: %03dx%03d+%03d+%03d %3d %3d rc=%d\n", dest_x, dest_y, w, h, dx, dy, rc); reg = sraRgnCreateRect(dest_x, dest_y, dest_x + w, dest_y + h); do_copyregion(reg, dx, dy, 0); sraRgnDestroy(reg); diff --git a/x11vnc/userinput.c b/x11vnc/userinput.c index 5b83a9b..cf35233 100644 --- a/x11vnc/userinput.c +++ b/x11vnc/userinput.c @@ -3825,7 +3825,8 @@ void ncache_pre_portions(Window orig_frame, Window frame, int *nidx_in, int try_ dx = 0; dy = dpy_y; sraRgnOffset(r2, dx, dy); -if (ncdb) fprintf(stderr, "FB_COPY: %.4f 1) offscreen check:\n", dnow() - ntim); +if (ncdb) fprintf(stderr, "FB_COPY: %.4f 1) offscreen: dx, dy: %d, %d -> %d, %d orig %dx%d+%d+%d bs_xy: %d %d\n", + dnow() - ntim, bs_x - orig_x, bs_y - orig_y, dx, dy, orig_w, orig_h, orig_x, orig_y, bs_x, bs_y); /* 0) save it in the invalid (offscreen) SU portion */ if (! *use_batch) { @@ -4107,8 +4108,20 @@ void do_copyrect_drag_move(Window orig_frame, Window frame, int *nidx, int try_b int dx, dy; int use_batch = 0; double ntim = dnow(); + static int nob = -1; sraRegionPtr r0, r1; + if (nob < 0) { + if (getenv("NOCRBATCH")) { + nob = 1; + } else { + nob = 0; + } + } + if (nob) { + try_batch = 0; + } + dx = x - now_x; dy = y - now_y; if (dx == 0 && dy == 0) { @@ -4125,6 +4138,13 @@ if (ncdb) fprintf(stderr, "do_COPY: now_xy: %d %d, orig_wh: %d %d, xy: %d %d, wh dx = x - now_x; dy = y - now_y; + + /* make sure the source is on-screen too */ + sraRgnOffset(r1, -dx, -dy); + sraRgnAnd(r1, r0); + sraRgnOffset(r1, +dx, +dy); + sraRgnAnd(r1, r0); /* just to be sure, problably not needed */ + if (! use_batch) { do_copyregion(r1, dx, dy, 0); if (!fb_push_wait(0.2, FB_COPY)) { diff --git a/x11vnc/x11vnc.1 b/x11vnc/x11vnc.1 index 93d2d23..5e08c55 100644 --- a/x11vnc/x11vnc.1 +++ b/x11vnc/x11vnc.1 @@ -2,7 +2,7 @@ .TH X11VNC "1" "March 2009" "x11vnc " "User Commands" .SH NAME x11vnc - allow VNC connections to real X11 displays - version: 0.9.7, lastmod: 2009-03-07 + version: 0.9.7, lastmod: 2009-03-08 .SH SYNOPSIS .B x11vnc [OPTION]... diff --git a/x11vnc/x11vnc.c b/x11vnc/x11vnc.c index 0c94168..89ca3df 100644 --- a/x11vnc/x11vnc.c +++ b/x11vnc/x11vnc.c @@ -1824,7 +1824,8 @@ char msg2[] = "\n" " x11vnc -ncache 10 ...\n" "\n" -"more info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching\n" +"One can also add -ncache_cr for smooth 'copyrect' window motion.\n" +"More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching\n" "\n" ; diff --git a/x11vnc/x11vnc_defs.c b/x11vnc/x11vnc_defs.c index e23c58f..4f773ca 100644 --- a/x11vnc/x11vnc_defs.c +++ b/x11vnc/x11vnc_defs.c @@ -15,7 +15,7 @@ int xtrap_base_event_type = 0; int xdamage_base_event_type = 0; /* date +'lastmod: %Y-%m-%d' */ -char lastmod[] = "0.9.7 lastmod: 2009-03-07"; +char lastmod[] = "0.9.7 lastmod: 2009-03-08"; /* X display info */ |
