Arch Linux

Shapeshifter

Member

Registered: 2008-03-11

Posts: 231

x11vnc dies/exits after a single successful session

Well, I've set up x11vnc on the server (without a .x11vncrc which is not needed) and I start it as user like this:

x11vnc -rfbport 41333 -rfbauth /home/medja/.vnc/passwd &

The log after starting it looks like this (all good):

[medja@Mothership ~]$ x11vnc -rfbport 41333 -rfbauth /home/medja/.vnc/passwd
06/01/2009 22:06:06 passing arg to libvncserver: -rfbport
06/01/2009 22:06:06 passing arg to libvncserver: 41333
06/01/2009 22:06:06 passing arg to libvncserver: -rfbauth
06/01/2009 22:06:06 passing arg to libvncserver: /home/medja/.vnc/passwd
06/01/2009 22:06:06 x11vnc version: 0.9.4 lastmod: 2007-12-21
06/01/2009 22:06:06 
06/01/2009 22:06:06 *** XOpenDisplay failed. No -display or DISPLAY.
06/01/2009 22:06:06 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
06/01/2009 22:06:06 *** 1 2 3 4 
06/01/2009 22:06:10 *** XOpenDisplay of ":0" successful.
06/01/2009 22:06:10 
06/01/2009 22:06:10 Using X display :0
06/01/2009 22:06:10 
06/01/2009 22:06:10 ------------------ USEFUL INFORMATION ------------------
06/01/2009 22:06:10 X DAMAGE available on display, using it for polling hints.
06/01/2009 22:06:10   To disable this behavior use: '-noxdamage'
06/01/2009 22:06:10 
06/01/2009 22:06:10 Wireframing: -wireframe mode is in effect for window moves.
06/01/2009 22:06:10   If this yields undesired behavior (poor response, painting
06/01/2009 22:06:10   errors, etc) it may be disabled:
06/01/2009 22:06:10    - use '-nowf' to disable wireframing completely.
06/01/2009 22:06:10    - use '-nowcr' to disable the Copy Rectangle after the
06/01/2009 22:06:10      moved window is released in the new position.
06/01/2009 22:06:10   Also see the -help entry for tuning parameters.
06/01/2009 22:06:10   You can press 3 Alt_L's (Left "Alt" key) in a row to 
06/01/2009 22:06:10   repaint the screen, also see the -fixscreen option for
06/01/2009 22:06:10   periodic repaints.
06/01/2009 22:06:10 
06/01/2009 22:06:10 XFIXES available on display, resetting cursor mode
06/01/2009 22:06:10   to: '-cursor most'.
06/01/2009 22:06:10   to disable this behavior use: '-cursor arrow'
06/01/2009 22:06:10   or '-noxfixes'.
06/01/2009 22:06:10 using XFIXES for cursor drawing.
06/01/2009 22:06:10 GrabServer control via XTEST.
Xlib:  extension "RECORD" missing on display ":0.0".
06/01/2009 22:06:10 
06/01/2009 22:06:10 The RECORD X extension was not found on the display.
06/01/2009 22:06:10 If your system has disabled it by default, you can
06/01/2009 22:06:10 enable it to get a nice x11vnc performance speedup
06/01/2009 22:06:10 for scrolling by putting this into the "Module" section
06/01/2009 22:06:10 of /etc/X11/xorg.conf or /etc/X11/XF86Config:
06/01/2009 22:06:10 
06/01/2009 22:06:10   Section "Module"
06/01/2009 22:06:10   ...
06/01/2009 22:06:10       Load    "record"
06/01/2009 22:06:10   ...
06/01/2009 22:06:10   EndSection
06/01/2009 22:06:10 
06/01/2009 22:06:10 
06/01/2009 22:06:10 XKEYBOARD:
06/01/2009 22:06:10 Switching to -xkb mode to recover these keysyms:
06/01/2009 22:06:10    xkb  noxkb   Keysym  ("X" means present)
06/01/2009 22:06:10    ---  -----   -----------------------------
06/01/2009 22:06:10     X           0x40  at
06/01/2009 22:06:10     X           0x23  numbersign
06/01/2009 22:06:10     X           0x5b  bracketleft
06/01/2009 22:06:10     X           0x5d  bracketright
06/01/2009 22:06:10     X           0x7b  braceleft
06/01/2009 22:06:10     X           0x7d  braceright
06/01/2009 22:06:10     X           0x7c  bar
06/01/2009 22:06:10     X           0x5c  backslash
06/01/2009 22:06:10 
06/01/2009 22:06:10   If this makes the key mapping worse you can
06/01/2009 22:06:10   disable it with the "-noxkb" option.
06/01/2009 22:06:10 
06/01/2009 22:06:10 X FBPM extension not supported.
06/01/2009 22:06:10 X display is capable of DPMS.
06/01/2009 22:06:10 --------------------------------------------------------
06/01/2009 22:06:10 
06/01/2009 22:06:10 Default visual ID: 0x21
06/01/2009 22:06:10 Read initial data from X display into framebuffer.
06/01/2009 22:06:10 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/9856
06/01/2009 22:06:10 
06/01/2009 22:06:10 X display :0.0 is 32bpp depth=24 true color
06/01/2009 22:06:10 
06/01/2009 22:06:10 Listening for VNC connections on TCP port 41333
06/01/2009 22:06:10 
06/01/2009 22:06:10 Xinerama is present and active (e.g. multi-head).
06/01/2009 22:06:10 Xinerama: enabling -xwarppointer mode to try to correct
06/01/2009 22:06:10 Xinerama: mouse pointer motion. XTEST+XINERAMA bug.
06/01/2009 22:06:10 Xinerama: Use -noxwarppointer to force XTEST.
06/01/2009 22:06:10 blackout rect: 1024x132+1440+768: x=1440-2464 y=768-900
06/01/2009 22:06:10 
06/01/2009 22:06:10 fb read rate: 405 MB/sec
06/01/2009 22:06:10 screen setup finished.
06/01/2009 22:06:10 

The VNC desktop is:      Mothership:35433
06/01/2009 22:06:10 possible aliases:  Mothership:41333, Mothership::41333
PORT=41333

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval.  It should work with any VNC viewer.  Try it by running:

    x11vnc -ncache 10 ...

more info: http://www.karlrunge.com/x11vnc/#faq-client-caching

Then I connect to it with a client (arch as well) like this:

vncviewer 192.168.1.4:41333

and the server outputs this stuff:

06/01/2009 22:09:18 Got connection from client 192.168.1.2
06/01/2009 22:09:18   other clients:
06/01/2009 22:09:18 Disabled X server key autorepeat.
06/01/2009 22:09:18   to force back on run: 'xset r on' (3 times)
06/01/2009 22:09:18 created xdamage object: 0xc00005
06/01/2009 22:09:18 copy_tiles: allocating first_line at size 78
06/01/2009 22:09:18 Client Protocol Version 3.8
06/01/2009 22:09:18 Protocol version sent 3.8, using 3.8
06/01/2009 22:09:18 rfbProcessClientSecurityType: executing handler for type 2
06/01/2009 22:09:21 Pixel format for client 192.168.1.2:
06/01/2009 22:09:21   32 bpp, depth 24, little endian
06/01/2009 22:09:21   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
06/01/2009 22:09:21 no translation needed
06/01/2009 22:09:22 Using compression level 1 for client 192.168.1.2
06/01/2009 22:09:22 Using image quality level 6 for client 192.168.1.2
06/01/2009 22:09:22 Enabling X-style cursor updates for client 192.168.1.2
06/01/2009 22:09:22 Enabling full-color cursor updates for client 192.168.1.2
06/01/2009 22:09:22 Enabling cursor position updates for client 192.168.1.2
06/01/2009 22:09:22 Enabling LastRect protocol extension for client 192.168.1.2
06/01/2009 22:09:22 Using tight encoding for client 192.168.1.2
06/01/2009 22:09:22 client 1 network rate 6693.8 KB/sec (35456.1 eff KB/sec)
06/01/2009 22:09:22 client 1 latency:  0.5 ms
06/01/2009 22:09:22 dt1: 0.2502, dt2: 0.0004 dt3: 0.0005 bytes: 1677818
06/01/2009 22:09:22 link_rate: LR_LAN - 1 ms, 6693 KB/s
06/01/2009 22:09:52 client_count: 0
06/01/2009 22:09:52 Restored X server key autorepeat to: 1
06/01/2009 22:09:52 viewer exited.
06/01/2009 22:09:52 deleted 1 tile_row polling images.
[medja@Mothership ~]$

I'm able to use it without problems but when I disconnect, the server just dies.

Of course I can't connect to the box via vnc anymore.

ps -A  | grep vnc shows nothing after that. It's definitely gone.

Does anyone have an idea what is wrong here? BTW, the same happens on another arch server I've set up for a friend but I'm not able to compare the logs and all that but he also can only connect to the vnc server once.

sofa5000

Member

Registered: 2008-03-18

Posts: 10

Re: x11vnc dies/exits after a single successful session

This is how it's meant to be.

By default x11vnc will not allow the screen to be shared and it will exit
as soon as the client disconnects.

You should take a look at the "-forever" option.

Last edited by sofa5000 (2009-01-07 16:19:07)

Shapeshifter

Member

Registered: 2008-03-11

Posts: 231

Re: x11vnc dies/exits after a single successful session

Ohhhh.... :O

so that's how it is. Thanks!

Alexandre Magno

Member

Registered: 2014-07-17

Posts: 4

Re: x11vnc dies/exits after a single successful session

$ while true; do x11vnc; done;  # To end, make 2x Control^C

Last edited by Alexandre Magno (2016-10-06 09:30:50)