Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530
Control: fixed 902893 0.9.13-6 Dear Maintainer, just tried to make a more readable stack out of these backtraces. This one points to function snapshot_stack_list, and this one saw also a fix some time ago. Therefore marking as fixed. Kind regards, Bernhard https://github.com/LibVNC/x11vnc/pull/25 https://github.com/LibVNC/x11vnc/pull/25/commits/c93aa29ae76a2fbb3e8c8e55a68de5544bd863b5 *** Error in `x11vnc': corrupted size vs. prev_size: 0x55f181552530 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fa6d0bcdbfb] /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fa6d0bd3fc6] /lib/x86_64-linux-gnu/libc.so.6(+0x780a4)[0x7fa6d0bd50a4] /usr/lib/x86_64-linux-gnu/libX11.so.6(XFree+0x9)[0x7fa6d1c19699] src/XlibInt.c, line 1553: callq 0x760c5600 x11vnc(+0xaceb4)[0x55f17f5b9eb4] win_utils.c, line 304: callq 0x55610da0 x11vnc(+0x41887)[0x55f17f54e887] pointer.c, line 552: callq 0x55600c70 x11vnc(+0x42846)[0x55f17f54f846] pointer.c, line 931: callq 0x55595540 /usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbProcessClientMessage+0x7d6)[0x7fa6d36aaa56] rfbserver.c, line 2447: callq *%rbx /usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbCheckFds+0x3a8)[0x7fa6d36b09e8] sockets.c, line 464: callq 0x77b7fb70 /usr/lib/x86_64-linux-gnu/libvncserver.so.1(rfbProcessEvents+0x1e)[0x7fa6d36a793e] main.c, line 1109: callq 0x77b7f130 x11vnc(+0xaa721)[0x55f17f5b7721] util.c, line 581: callq 0xd520 x11vnc(+0xa27e5)[0x55f17f5af7e5] userinput.c, line 5212: callq 0x555fe590 x11vnc(+0x6a77c)[0x55f17f5c] screen.c, line 4561: callq 0x555f5e90 x11vnc(+0x13ae4)[0x55f17f520ae4] x11vnc.c, line 5990: callq 0x555bdd10 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7fa6d0b7d2e1] x11vnc(+0x1cd7a)[0x55f17f529d7a] # Stretch amd64 qemu VM 2019-03-29 apt update apt dist-upgrade approx: debian-10-buster-snapshot.debian.org https://snapshot.debian.org/archive/debian/20180703T00Z/ sources.list deb [check-valid-until=no] http://192.168.178.25:/debian-10-buster-snapshot.debian.org/ buster main echo 'Acquire::Languages "none";' > /etc/apt/apt.conf.d/99disable-translations echo 'Acquire::Check-Valid-Until "no";' > /etc/apt/apt.conf.d/99disable-check-valid-until apt update apt dist-upgrade apt install dpkg-dev devscripts x11vnc gdb mc wget https://snapshot.debian.org/archive/debian-debug/20180508T213823Z/pool/main/x/x11vnc/x11vnc-dbgsym_0.9.13-6_amd64.deb dpkg -i x11vnc-dbgsym_0.9.13-6_amd64.deb wget https://snapshot.debian.org/archive/debian/20161222T033154Z/pool/main/x/x11vnc/x11vnc_0.9.13-2_amd64.deb wget https://snapshot.debian.org/archive/debian/20161222T033154Z/pool/main/x/x11vnc/x11vnc-data_0.9.13-2_all.deb wget https://snapshot.debian.org/archive/debian-debug/20161222T030857Z/pool/main/x/x11vnc/x11vnc-dbgsym_0.9.13-2_amd64.deb dpkg -i *0.9.13-2*deb wget https://snapshot.debian.org/archive/debian-security/20180608T202807Z/pool/updates/main/libv/libvncserver/libvncserver1_0.9.11%2Bdfsg-1%2Bdeb9u1_amd64.deb wget https://snapshot.debian.org/archive/debian-security/20180608T202807Z/pool/updates/main/libv/libvncserver/libvncserver1-dbg_0.9.11%2Bdfsg-1%2Bdeb9u1_amd64.deb dpkg -i *0.9.11+dfsg-1+deb9u1*deb wget https://snapshot.debian.org/archive/debian/20170128T033044Z/pool/main/libx/libx11/libx11-6_1.6.4-3_amd64.deb wget https://snapshot.debian.org/archive/debian-debug/20170128T030650Z/pool/main/libx/libx11/libx11-6-dbgsym_1.6.4-3_amd64.deb dpkg -i *1.6.4-3*deb mkdir /home/benutzer/source/x11vnc/orig -p cd/home/benutzer/source/x11vnc/orig dget https://snapshot.debian.org/archive/debian-debug/20161222T030857Z/pool/main/x/x11vnc/x11vnc_0.9.13-2.dsc gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace past-main on' -ex 'directory /home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 'b main' -ex 'run' --args x11vnc script -c "gdb -q -ex 'set width 0' -ex 'set pagination off' -ex 'set backtrace past-main on' -ex 'directory /home/benutzer/source/x11vnc/orig/x11vnc-0.9.13/x11vnc' -ex 'b main' -ex 'run' --args x11vnc" -a x11vnc-gdb_$(date +%Y-%m-%d_%H-%M-%S).log *** Error in `x11vnc': corrupted size vs. prev_size: 0x55f181552530 *** === Backtrace: = /lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7fa6d0bcdbfb] /lib/x86_64-linux-gnu/libc.so.6(+0x76fc6)[0x7fa6d0bd3fc6] /lib/x86_64-linux-gnu/libc.so.6(+0x780a4)[0x7fa6d0bd50a4]
Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530
Hi Nikita,
Thank you for the quick reply. I am afraid it works today - I cannot
reproduce the problem anymore, although I didn't install any new package
on the system. Meanwhile, I used the system in question sitting at the
console, locked the kde console again in the evening... now I can run
x11vnc from remote without any problem.
I swear yesterday it happened every time I tried.
I will get back to this in case it happens again.
Slightly embarrassed, thanks again,
moritz
Am 03.07.2018 um 09:08 schrieb Nikita Youshchenko:
Hello Mortiz.
Please check latest package version from sid/testing.
(it should not have any dependences not available in stretch)
I believe issue with memory corruption is resolved there.
I can't comment on input issue yet, did not face it.
Nikita
Package: x11vnc
Version: 0.9.13-2
Severity: important
Dear Maintainer,
for me x11vnc does not accept any input although I can see the
remove screen. I use tightvnc viewer 2.6 on windows 7 as the client.
Also, x11vnc shows a memory corruption issue. Output of the session follows.
###
#@#
#@ @#
#@ ** 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. @#
#@ @#
#@#
###
03/07/2018 04:58:08 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 26307
03/07/2018 04:58:08 XOpenDisplay("") failed.
03/07/2018 04:58:08
Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530
Hello Mortiz.
Please check latest package version from sid/testing.
(it should not have any dependences not available in stretch)
I believe issue with memory corruption is resolved there.
I can't comment on input issue yet, did not face it.
Nikita
> Package: x11vnc
> Version: 0.9.13-2
> Severity: important
>
> Dear Maintainer,
>
> for me x11vnc does not accept any input although I can see the
> remove screen. I use tightvnc viewer 2.6 on windows 7 as the client.
>
> Also, x11vnc shows a memory corruption issue. Output of the session follows.
>
> ###
> #@#
> #@ @#
> #@ ** 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. @#
> #@ @#
> #@#
> ###
> 03/07/2018 04:58:08 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 26307
> 03/07/2018 04:58:08 XOpenDisplay("") failed.
> 03/07/2018 04:58:08 Trying again with XAUTHLOCALHOSTNAME=localhost ...
> 03/07/2018 04:58:08
> 03/07/2018 04:58:08 *** XOpenDisplay failed. No -display or DISPLAY.
> 03/07/2018 04:58:08 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
> 03/07/2018 04:58:08 *** 1 2 3 4
> 03/07/2018 04:58:12 *** XOpenDisplay of ":0" successful.
> 03/07/2018 04:58:12
> 03/07/2018 04:58:12 Using X display :0
> 03/07/2018 04:58:12
Bug#902893: x11vnc: Error in `x11vnc': corrupted size vs. prev_size: 0x000055f181552530
Package: x11vnc
Version: 0.9.13-2
Severity: important
Dear Maintainer,
for me x11vnc does not accept any input although I can see the
remove screen. I use tightvnc viewer 2.6 on windows 7 as the client.
Also, x11vnc shows a memory corruption issue. Output of the session follows.
###
#@#
#@ @#
#@ ** 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. @#
#@ @#
#@#
###
03/07/2018 04:58:08 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 26307
03/07/2018 04:58:08 XOpenDisplay("") failed.
03/07/2018 04:58:08 Trying again with XAUTHLOCALHOSTNAME=localhost ...
03/07/2018 04:58:08
03/07/2018 04:58:08 *** XOpenDisplay failed. No -display or DISPLAY.
03/07/2018 04:58:08 *** Trying ":0" in 4 seconds. Press Ctrl-C to abort.
03/07/2018 04:58:08 *** 1 2 3 4
03/07/2018 04:58:12 *** XOpenDisplay of ":0" successful.
03/07/2018 04:58:12
03/07/2018 04:58:12 Using X display :0
03/07/2018 04:58:12 rootwin: 0xd5 reswin: 0xa81 dpy: 0x8118a660
03/07/2018 04:58:12
03/07/2018 04:58:12 -- USEFUL INFORMATION --
03/07/2018 04:58:12 X DAMAGE available on display, using it for polling hints.
03/07/2018 04:58:12 To disable this behavior use: '-noxdamage'
03/07/2018 04:58:12
03/07/2018 04:58:12 Most compositing window managers like 'compiz' or 'beryl'
03/07/2018 04:58:12 cause
