Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- 11/09/2011 20:22:00 passing arg to libvncserver: -rfbauth
- 11/09/2011 20:22:00 passing arg to libvncserver: [my home address]/.vnc/passwd
- 11/09/2011 20:22:00 x11vnc version: 0.9.9 lastmod: 2009-12-21 pid: 754
- 11/09/2011 20:22:00
- 11/09/2011 20:22:00 wait_for_client: WAIT:cmd=FINDCREATEDISPLAY-Xvfb
- 11/09/2011 20:22:00
- 11/09/2011 20:22:00 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560
- 11/09/2011 20:22:00
- 11/09/2011 20:22:00 Autoprobing TCP port
- 11/09/2011 20:22:00 Autoprobing selected port 5900
- 11/09/2011 20:22:00
- The VNC desktop is: [name of the server]:0
- 11/09/2011 20:22:36 Got connection from client [android IP]
- 11/09/2011 20:22:36 other clients:
- 11/09/2011 20:22:36 incr accepted_client=1 for [android IP]:46354 sock=4
- 11/09/2011 20:22:36 wait_for_client: got client
- 11/09/2011 20:22:36 Client Protocol Version 3.8
- 11/09/2011 20:22:36 Protocol version sent 3.8, using 3.8
- 11/09/2011 20:22:36 client progressed=1 in 2/8 0.002783 s
- 11/09/2011 20:22:36 client_set_net: [android IP] 0.0002
- 11/09/2011 20:22:36 wait_for_client: running: env X11VNC_SKIP_DISPLAY='' /bin/sh /tmp/x11vnc-find_display.65BqLr
- 11/09/2011 20:22:36 wait_for_client: find display cmd failed.
- 11/09/2011 20:22:36 wait_for_client: FINDCREATEDISPLAY cmd: /bin/sh /tmp/x11vnc-find_display.65BqLr Xvfb
- trying N=20 ...
- redir_daemon=
- /usr/bin/xinit /usr/bin/xterm -- /usr/bin/Xvfb :20 -screen 0 1280x1024x24 +kb -cc 4 -nolisten tcp -auth /tmp/.xas87817719.cvWoFR
- Unrecognized option: +kb
- use: X [:<display>] [option]
- -a # default pointer acceleration (factor)
- -ac disable access control restrictions
- -audit int set audit trail level
- -auth file select authorization file
- -br create root window with black background
- +bs enable any backing store support
- -bs disable any backing store support
- -c turns off key-click
- c # key-click volume (0-100)
- -cc int default color visual class
- -nocursor disable the cursor
- -core generate core dump on fatal error
- -dpi int screen resolution in dots per inch
- -dpms disables VESA DPMS monitor control
- -deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs
- -f # bell base (0-100)
- -fc string cursor font
- -fn string default font name
- -fp string default font path
- -help prints message with these options
- -I ignore all remaining arguments
- -ld int limit data space to N Kb
- -lf int limit number of open files to N
- -ls int limit stack space to N Kb
- -nolock disable the locking mechanism
- -nolisten string don't listen on protocol
- -noreset don't reset after last client exists
- -background [none] create root window with no background
- -reset reset after last client exists
- -p # screen-saver pattern duration (minutes)
- -pn accept failure to listen on all ports
- -nopn reject failure to listen on all ports
- -r turns off auto-repeat
- r turns on auto-repeat
- -render [default|mono|gray|color] set render color alloc policy
- -retro start with classic stipple and cursor
- -s # screen-saver timeout (minutes)
- -t # default pointer threshold (pixels/t)
- -terminate terminate at server reset
- -to # connection time out
- -tst disable testing extensions
- ttyxx server started from init on /dev/ttyxx
- v video blanking for screen-saver
- -v screen-saver without video blanking
- -wm WhenMapped default backing-store
- -wr create root window with white background
- -maxbigreqsize set maximal bigrequest size
- +xinerama Enable XINERAMA extension
- -xinerama Disable XINERAMA extension
- -dumbSched Disable smart scheduling, enable old behavior
- -schedInterval int Set scheduler interval in msec
- -sigstop Enable SIGSTOP based startup
- +extension name Enable extension
- -extension name Disable extension
- -query host-name contact named host for XDMCP
- -broadcast broadcast for XDMCP
- -indirect host-name contact named host for indirect XDMCP
- -port port-num UDP port number to send messages to
- -from local-address specify the local address to connect from
- -once Terminate server after one session
- -class display-class specify display class to send in manage
- -cookie xdm-auth-bits specify the magic cookie for XDMCP
- -displayID display-id manufacturer display ID for request
- [+-]accessx [ timeout [ timeout_mask [ feedback [ options_mask] ] ] ]
- enable/disable accessx key sequences
- -ardelay set XKB autorepeat delay
- -arinterval set XKB autorepeat interval
- -screen scrn WxHxD set screen's width, height, depth
- -pixdepths list-of-int support given pixmap depths
- +/-render turn on/off RENDER extension support(default on)
- -linebias n adjust thin line pixelization
- -blackpixel n pixel value for black
- -whitepixel n pixel value for white
- -fbdir directory put framebuffers in mmap'ed files in directory
- -shmem put framebuffers in shared memory
- Fatal server error:
- Unrecognized option: +kb
- 11/09/2011 20:22:38 XOpenDisplay(":20") failed.
- 11/09/2011 20:22:38 Trying again with XAUTHLOCALHOSTNAME=localhost ...
- 11/09/2011 20:22:38 ***************************************
- 11/09/2011 20:22:38 *** XOpenDisplay failed (:20)
- *** x11vnc was unable to open the X DISPLAY: ":20", it cannot continue.
- *** There may be "Xlib:" error messages above with details about the failure.
- Some tips and guidelines:
- ** An X server (the one you wish to view) must be running before x11vnc is
- started: x11vnc does not start the X server. (however, see the -create
- option if that is what you really want).
- ** You must use -display <disp>, -OR- set and export your $DISPLAY
- environment variable to refer to the display of the desired X server.
- - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
- to specify it), but in some multi-user situations it could be ":1", ":2",
- or even ":137". Ask your administrator or a guru if you are having
- difficulty determining what your X DISPLAY is.
- ** Next, you need to have sufficient permissions (Xauthority)
- to connect to the X DISPLAY. Here are some Tips:
- - Often, you just need to run x11vnc as the user logged into the X session.
- So make sure to be that user when you type x11vnc.
- - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
- file will be accessed. The cookie file contains the secret key that
- allows x11vnc to connect to the desired X DISPLAY.
- - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
- by the -auth option, e.g.:
- x11vnc -auth /home/someuser/.Xauthority -display :0
- x11vnc -auth /tmp/.gdmzndVlR -display :0
- you must have read permission for the auth file.
- ** If NO ONE is logged into an X session yet, but there is a greeter login
- program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
- to find and use the raw display manager MIT-MAGIC-COOKIE file.
- Some examples for various display managers:
- gdm: -auth /var/gdm/:0.Xauth
- -auth /var/lib/gdm/:0.Xauth
- kdm: -auth /var/lib/kdm/A:0-crWk72
- -auth /var/run/xauth/A:0-crWk72
- xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
- dtlogin: -auth /var/dt/A:0-UgaaXa
- Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.
- Only root will have read permission for the file, and so x11vnc must be run
- as root (or copy it). The random characters in the filenames will of course
- change and the directory the cookie file resides in is system dependent.
- See also: http://www.karlrunge.com/x11vnc/faq.html
- /usr/bin/xmodmap: unable to open display ':20'
- /usr/bin/xinit: giving up
- /usr/bin/xinit: unable to connect to X server: Connection refused
- /usr/bin/xinit: server error
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement