Bug#855967: x11vnc suddenly dropped the connection

2017-02-23 Thread zoltan herman 
Tags: moreinfo

after checked logfile, found error.
23/02/2017 22:24:30 passing arg to libvncserver: -desktop
23/02/2017 22:24:30 passing arg to libvncserver: dl360g7:0.0
###
#@#
#@   @#
#@  **  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.   @#
#@   @#
#@#
###
23/02/2017 22:24:31 x11vnc version: 0.9.13 lastmod: 2011-08-10  pid: 11706
23/02/2017 22:24:31 XOpenDisplay("") failed.
23/02/2017 22:24:31 Trying again with XAUTHLOCALHOSTNAME=localhost ...
23/02/2017 22:24:31 
23/02/2017 22:24:31 *** XOpenDisplay failed. No -display or DISPLAY.
23/02/2017 22:24:31 *** Trying ":0" in 4 seconds.  Press Ctrl-C to abort.
23/02/2017 22:24:31 *** 1 2 3 4 
23/02/2017 22:24:35 *** XOpenDisplay of ":0" successful.
23/02/2017 22:24:35 
23/02/2017 22:24:35 Using X display :0
23/02/2017 22:24:35 rootwin: 0x49e reswin: 0x121 dpy: 0xf5454ac0
23/02/2017 22:24:35 
23/02/2017 22:24:35 -- USEFUL INFORMATION --
23/02/2017 22:24:35 X DAMAGE available on display, using it for polling hints.
23/02/2017 22:24:35   To disable this behavior use: '-noxdamage'
23/02/2017 22:24:35 
23/02/2017 22:24:35   Most compositing window managers like 'compiz' or 'beryl'
23/02/2017 22:24:35   cause X DAMAGE to fail, and so you may not see any screen
23/02/2017 22:24:35   updates via VNC.  Either

Bug#855967: x11vnc suddenly dropped the connection

2017-02-23 Thread zoltan herman 
Package: x11vnc
Version: 0.9.13-2
Severity: normal
Tags: newcomer

Dear Maintaners,
after upgrade the system, x11vnc dropped the connection(s),
especially when I use Firefox/CodeBlocks applications.
I have not found error in log files.

After dropped the connection, service wrote info :
systemctl status myvncserver
● myvncserver.service - VNC Server for X11
   Loaded: loaded (/lib/systemd/system/myvncserver.service; disabled; vendor
preset: enabled)
   Active: failed (Result: exit-code) since cs 2017-02-23 21:26:57 CET; 43min
ago
  Process: 8310 ExecStart=/usr/bin/x11vnc -auth /tmp/xauth-1000-_0 -desktop
dl360g7:0.0 -forever -bg -o /var/log/x1
 Main PID: 8312 (code=exited, status=2)

febr 23 21:14:16 dl360g7 systemd[1]: Starting VNC Server for X11...
febr 23 21:14:22 dl360g7 x11vnc[8310]: PORT=5900
febr 23 21:14:22 dl360g7 systemd[1]: Started VNC Server for X11.
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Main process exited,
code=exited, status=2/INVALIDARGUMEN
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Unit entered failed
state.
febr 23 21:26:57 dl360g7 systemd[1]: myvncserver.service: Failed with result
'exit-code'.

x11vnc log part after restarted it :

23/02/2017 22:25:23 Got connection from client 192.168.0.13
23/02/2017 22:25:23   other clients:
23/02/2017 22:25:23 Normal socket connection
23/02/2017 22:25:23 incr accepted_client=1 for 192.168.0.13:26525  sock=11
23/02/2017 22:25:23 Client Protocol Version 3.8
23/02/2017 22:25:23 Protocol version sent 3.8, using 3.8
23/02/2017 22:25:23 rfbProcessClientSecurityType: executing handler for type 1
23/02/2017 22:25:23 rfbProcessClientSecurityType: returning securityResult for
client rfb version >= 3.8
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x0016)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x0015)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0x000F)
23/02/2017 22:25:23 rfbProcessClientNormalMessage: ignoring unsupported
encoding type Enc(0xFEC6)
23/02/2017 22:25:23 Enabling full-color cursor updates for client 192.168.0.13
23/02/2017 22:25:23 Enabling NewFBSize protocol extension for client
192.168.0.13
23/02/2017 22:25:23 Using ZRLE encoding for client 192.168.0.13
23/02/2017 22:25:23 Pixel format for client 192.168.0.13:
23/02/2017 22:25:23   32 bpp, depth 24, little endian
23/02/2017 22:25:23   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
23/02/2017 22:25:23 no translation needed
23/02/2017 22:25:23 copy_tiles: allocating first_line at size 41
23/02/2017 22:25:24 client useCopyRect: 192.168.0.13 -1
23/02/2017 22:25:24 client_set_net: 192.168.0.13  0.0098
23/02/2017 22:25:24 created   xdamage object: 0x120002c
23/02/2017 22:25:26 client 1 network rate 2533.8 KB/sec (69257.0 eff KB/sec)
23/02/2017 22:25:26 client 1 latency:  3.8 ms
23/02/2017 22:25:26 dt1: 0.0212, dt2: 0.0126 dt3: 0.0038 bytes: 80860
23/02/2017 22:25:26 link_rate: LR_LAN - 3 ms, 2533 KB/s
23/02/2017 22:25:33 created selwin: 0x120002d
23/02/2017 22:25:33 called initialize_xfixes()
23/02/2017 22:31:04 cursor_noshape_updates_clients: 0
23/02/2017 22:31:26 added missing keysym to X display: 093 0xd6 "Odiaeresis"
23/02/2017 22:39:22 cursor_noshape_updates_clients: 0
23/02/2017 22:39:30 cursor_noshape_updates_clients: 0



Greetings
hz



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.7.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=hu_HU.UTF-8, LC_CTYPE=hu_HU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages x11vnc depends on:
ii  libavahi-client3  0.6.32-2
ii  libavahi-common3  0.6.32-2
ii  libc6 2.24-9
ii  libjpeg62-turbo   1:1.5.1-2
ii  libssl1.1 1.1.0e-1
ii  libvncclient1 0.9.11+dfsg-1
ii  libvncserver1 0.9.11+dfsg-1
ii  libx11-6  2:1.6.4-3
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxinerama1  2:1.1.3-1+b1
ii  libxrandr22:1.5.1-1
ii  libxtst6  2:1.2.3-1
ii  openssl   1.1.0e-1
ii  tk8.6.0+9
ii  x11vnc-data   0.9.13-2
ii  zlib1g1:1.2.8.dfsg-5

x11vnc recommends no packages.

x11vnc suggests no packages.

-- no debconf information