Pastebin launched a little side project called VERYVIRAL.com, check it out ;-) Want more features on Pastebin? Sign Up, it's FREE!
Guest

Untitled

By: a guest on Sep 11th, 2011  |  syntax: None  |  size: 3.14 KB  |  views: 55  |  expires: Never
download  |  raw  |  embed  |  report abuse  |  print
Text below is selected. Please press Ctrl+C to copy to your clipboard. (⌘+C on Mac)
  1. 11/09/2011 21:01:26 passing arg to libvncserver: -rfbauth
  2. 11/09/2011 21:01:26 passing arg to libvncserver: [my home address]/.vnc/passwd
  3. 11/09/2011 21:01:26 x11vnc version: 0.9.9 lastmod: 2009-12-21  pid: 4466
  4. 11/09/2011 21:01:26 XOpenDisplay("") failed.
  5. 11/09/2011 21:01:26 Trying again with XAUTHLOCALHOSTNAME=localhost ...
  6. 11/09/2011 21:01:26 
  7. 11/09/2011 21:01:26 *** XOpenDisplay failed. No -display or DISPLAY.
  8. 11/09/2011 21:01:26 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
  9. 11/09/2011 21:01:26 *** 1 2 3 4
  10. No protocol specified
  11. No protocol specified
  12. No protocol specified
  13. No protocol specified
  14. 11/09/2011 21:01:30
  15.  
  16. 11/09/2011 21:01:30 ***************************************
  17. 11/09/2011 21:01:30 *** XOpenDisplay failed (:0)
  18.  
  19. *** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
  20. *** There may be "Xlib:" error messages above with details about the failure.
  21.  
  22. Some tips and guidelines:
  23.  
  24. ** An X server (the one you wish to view) must be running before x11vnc is
  25.    started: x11vnc does not start the X server.  (however, see the -create
  26.    option if that is what you really want).
  27.  
  28. ** You must use -display <disp>, -OR- set and export your $DISPLAY
  29.    environment variable to refer to the display of the desired X server.
  30.  - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
  31.    to specify it), but in some multi-user situations it could be ":1", ":2",
  32.    or even ":137".  Ask your administrator or a guru if you are having
  33.    difficulty determining what your X DISPLAY is.
  34.  
  35. ** Next, you need to have sufficient permissions (Xauthority)
  36.    to connect to the X DISPLAY.   Here are some Tips:
  37.  
  38.  - Often, you just need to run x11vnc as the user logged into the X session.
  39.    So make sure to be that user when you type x11vnc.
  40.  - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
  41.    file will be accessed.  The cookie file contains the secret key that
  42.    allows x11vnc to connect to the desired X DISPLAY.
  43.  - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
  44.    by the -auth option, e.g.:
  45.        x11vnc -auth /home/someuser/.Xauthority -display :0
  46.        x11vnc -auth /tmp/.gdmzndVlR -display :0
  47.    you must have read permission for the auth file.
  48.  
  49. ** If NO ONE is logged into an X session yet, but there is a greeter login
  50.    program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
  51.    to find and use the raw display manager MIT-MAGIC-COOKIE file.
  52.    Some examples for various display managers:
  53.  
  54.      gdm:     -auth /var/gdm/:0.Xauth
  55.               -auth /var/lib/gdm/:0.Xauth
  56.      kdm:     -auth /var/lib/kdm/A:0-crWk72
  57.               -auth /var/run/xauth/A:0-crWk72
  58.      xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
  59.      dtlogin: -auth /var/dt/A:0-UgaaXa
  60.  
  61.    Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.
  62.  
  63.    Only root will have read permission for the file, and so x11vnc must be run
  64.    as root (or copy it).  The random characters in the filenames will of course
  65.    change and the directory the cookie file resides in is system dependent.
  66.  
  67. See also: http://www.karlrunge.com/x11vnc/faq.html