Dotaz: problem nastartovat x11vnc cez ssh

[sid.dagivers]

sid@sid-GX700:~$ sudo startx [sudo] password for sid:

X.Org X Server 1.14.3 Release Date: 2013-09-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.2.0-37-generic x86_64 Ubuntu Current Operating System: Linux sid-GX700 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=ff0b39c3-cdc6-4e40-a617-1452710fbb7a ro quiet splash vt.handoff=7 Build Date: 15 October 2013 09:23:37AM xorg-server 2:1.14.3-3ubuntu2 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.30.2 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.1.log", Time: Tue Oct 29 20:20:15 2013 (==) Using system config directory "/usr/share/X11/xorg.conf.d" setversion 1.4 failed Initializing built-in extension Generic Event Extension Initializing built-in extension SHAPE Initializing built-in extension MIT-SHM Initializing built-in extension XInputExtension Initializing built-in extension XTEST Initializing built-in extension BIG-REQUESTS Initializing built-in extension SYNC Initializing built-in extension XKEYBOARD Initializing built-in extension XC-MISC Initializing built-in extension SECURITY Initializing built-in extension XINERAMA Initializing built-in extension XFIXES Initializing built-in extension RENDER Initializing built-in extension RANDR Initializing built-in extension COMPOSITE Initializing built-in extension DAMAGE Initializing built-in extension MIT-SCREEN-SAVER Initializing built-in extension DOUBLE-BUFFER Initializing built-in extension RECORD Initializing built-in extension DPMS Initializing built-in extension X-Resource Initializing built-in extension XVideo Initializing built-in extension XVideo-MotionCompensation Initializing built-in extension SELinux Initializing built-in extension XFree86-VidModeExtension Initializing built-in extension XFree86-DGA Initializing built-in extension XFree86-DRI Initializing built-in extension DRI2 Loading extension GLX setversion 1.4 failed

najprv sa musim prihlasit lokalne na pc cez gui a spustit x11vnc server a potom ide sa pripojit na pc

googlil som uz vela for ale nepodarilo sa mi to nijako rozbehat

nejake napady? len zacinam s linuxom pc mam bez monitora a po kazdom restarte ho musim prenasat a zapajat naspat.

dik moc

Odpovědi

[Peter Golis]

Príkazom startx nenaštartuješ vnc.

[Jendа]

Spusť po SSH rovnou x11vnc -- pokud ti Xka už běží (přes nějaký display manager). Budeš muset nastavit -auth /home/UŽIVATEL/.Xauthority, případně někde ve /var/run/tvůj_správce_obrazovky.

No a nebo se dá spustit X úplně headless klidně na počítači bez grafiky - příkaz vncserver.

[sid.dagivers]

Ahojte

mam problem rozbehat remote na ubuntu 13.x

ked nastartujem pc a pripojim sa cez ssh a chcem spustit vncserver nejde to

sid@sid-GX700:~$ x11vnc

** WARNING ** WARNING ** WARNING ** WARNING ** YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! This means anyone with network access to this computer may be able to view and control your desktop. If you did not mean to do this Press CTRL-C now! You can create an x11vnc password file by running: x11vnc -storepasswd password /path/to/passfile or x11vnc -storepasswd /path/to/passfile or x11vnc -storepasswd (the last one will use ~/.vnc/passwd) and then starting x11vnc via: x11vnc -rfbauth /path/to/passfile an existing ~/.vnc/passwd file from another VNC application will work fine too. You can also use the -passwdfile or -passwd options. (note -passwd is unsafe if local users are not trusted) Make sure any -rfbauth and -passwdfile password files cannot be read by untrusted users. Use x11vnc -usepw to automatically use your ~/.vnc/passwd or ~/.vnc/passwdfile password files. (and prompt you to create ~/.vnc/passwd if neither file exists.) Under -usepw, x11vnc will exit if it cannot find a password to use. Even with a password, the subsequent VNC traffic is sent in the clear. Consider tunnelling via ssh(1): http://www.karlrunge.com/x11vnc/#tunnelling Or using the x11vnc SSL options: -ssl and -stunnel Please Read the documention for more info about passwords, security, and encryption. http://www.karlrunge.com/x11vnc/faq.html#faq-passwd To disable this warning use the -nopw option, or put 'nopw' on a line in your ~/.x11vncrc file.

29/10/2013 20:20:57 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 2386 29/10/2013 20:20:57 XOpenDisplay("") failed. 29/10/2013 20:20:57 Trying again with XAUTHLOCALHOSTNAME=localhost ... 29/10/2013 20:20:57 29/10/2013 20:20:57 *** XOpenDisplay failed. No -display or DISPLAY. 29/10/2013 20:20:57 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort. 29/10/2013 20:20:57 *** 1 2 3 4 Invalid MIT-MAGIC-COOKIE-1 key29/10/2013 20:21:01 XOpenDisplay(":0") failed. 29/10/2013 20:21:01 Trying again with XAUTHLOCALHOSTNAME=localhost ... Invalid MIT-MAGIC-COOKIE-1 key29/10/2013 20:21:01 XOpenDisplay(":0") failed. 29/10/2013 20:21:01 Trying again with unset XAUTHLOCALHOSTNAME ... Invalid MIT-MAGIC-COOKIE-1 key29/10/2013 20:21:01

29/10/2013 20:21:01 *************************************** 29/10/2013 20:21:01 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", 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 may 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. See also '-auth guess' and '-findauth' discussed below.

** 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.

Starting with x11vnc 0.9.9 you can have it try to guess by using:

-auth guess

(see also the x11vnc -findauth option.)

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

[pavel]

Klient:
ssh -L 5900:localhost:5900 -C -c blowfish alois@ipadresa

Po přihlášení na server:
x11vnc -noxrecord -noxfixes -noxdamage -nomodtweak -display :0 -geometry 1000x760 -localhost

Klient:
vncviewer -encodings Tight -compresslevel 8 -quality 1 localhost:5900

Nebo použiješ jako klienta program "ssvnc", popřípadě "Remmina".

[Jendа]

x11vnc -noxrecord -noxfixes -noxdamage -nomodtweak -display :0 -geometry 1000x760 -localhost

Podle mě nemá cestu k Xauthority.

[pavel]

Xauthority je třeba k přihlášení do G(K)DM. Pokud se přihlašuji do již spuštěného grafického prostředí, není potřeba. Pokud se vzdáleně připojuji třeba do GDM, musím se po ssh-přihlášení přihlásit jako uživatel root a spustit:

x11vnc -display :0 -localhost -auth /var/run/gdm/auth-for-gdm-neco/database

kde "/var/run/gdm/auth-for-gdm-neco/database" je cesta k souboru "magic cookie" - umístění záleží na druhu grafického správce přihlašování a distribuci linuxu.

[Milan Uhrák]

Takhle to nepujde, jak to děláš ...

kdysi jsem řešil připojení na vnc server, který třebas i neběží takto :

#! /bin/bash
RemoteHost="server"
echo "Testuji, zda běží náš VNC server"
vncprocess=`ssh $RemoteHost ps ax | grep [m]ydesktop`
if [ "$vncprocess" == "" ]; then
  echo "VNC server neběží, spouštím jej"
  ssh $RemoteHost vncserver -geometry 1180x990 -desktop mydesktop
  sleep 3s
  echo "Naběhl server ?"
  vncprocess=`ssh $RemoteHost ps ax | grep [m]ydesktop`
  if [ "$vncprocess" == "" ]; then
    echo " Spuštění vzdáleného serveru se nezdařilo"
    exit 1
  fi 
fi
vncprocess=${vncprocess##*rfbport }
vncport=${vncprocess%% -*}
echo "spouštím vncviewer na portu /*$vncport*/"
vncviewer -passwd ~/.vnc/mypass -encodings zlib -compresslevel 4 -via $RemoteHost localhost::"$vncport"

Podmínkou je použít ssh s autentizaci pomocí klíče (jinak budeš x krát řešit zadávání hesla).

Vncserver musíš mít nastaven, aby naběhl (pokud není dobře nakonfigurován, uvidíš jen šedou plochu se zaměřovacím křížem).

v tomto skriptu se používá tunelování přes ssh (--via) kdy se k vncserveru připojuješ vlastně lokálně, tunelem vytvořeným ssh. To je ale dobré hlavně na připojování se k serverům, které mají veřejnou adresu a jsou dosažitelné z celého světa, protože pak se vncserver taky pouští jinak, aby naslouchal jen na localhostu, ale to je jiné téma. pokud si jen hraješ, můžeš "-via $RemoteHost localhost" nahradit prostě natvrdo nějaou tou adresou , třeba "192.168.0.1", nebo jak to máš doma nastavené

RemoteHost MUSÍ být uveden v ~/.ssh/config (doufám, že se připojuješ z linuxu)

pokud se připojuješ z widlí ... tak ...

------------------------------------------

si na server umístí do domovského adresáře skript např. runmyvnc.sh

#! /bin/bash

dbus-launch vncserver -desktop mydesktop -geometry 1100x900

nezapomeň ho označit jako spustitelný

a v ~/.vnc/ upravit soubor xstartup takto :

#!/bin/sh

#xrdb $HOME/.Xresources
#xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
startkde &

tuto úpravou se zajistí, že po spuštění vncserveru se spustí prostředí KDE ... pokud upřednostňuješ jiné prostředí, je nutno najít, jakým příkazem se spouští

Takže pak se logneš na server ssh-čkem, zadáš povel ~/runmyvnc.sh a startující vncserver vyhodí asi takovouto hlášku :

Starting applications specified in /home/milan/.vnc/xstartup
Log file is /home/milan/.vnc/server:2.log

ono server:2 znamená , že se musíš pak připojit na server:2 nebo na server::5902

Není to dokonalé, ale použitelné

Milan