On Tuesday, 7 February 2023, 03:40:58 am AEDT, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Hi Jay,
On Di 27 Dez 2022 00:19:31 CET, Jay wrote:
> Dear Maintainer,
>
> * What led up to the situation?
>
> I run x11vnc over a gigabit direct connection with:
>
> x11vnc -usepw -ncache_cr -display :0 -loop -noxdamage -shared
> -nomodtweak -noshm
>
> Upgrading to 0.9.13+dfsg-2+deb11u1 and then reconnecting my client
> caused x11vnc
> to run very slowly. `*** fb_push ublen NOT ZERO: 3290940` appeared
> in the log
> very frequently. From my logs, I had only seen this message once before, 10
> months ago.
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> Ineffective: reconnecting, restarting x11vnc, or rebooting
>
> Effective: downgrading to 0.9.13+dfsg-2 and reconnecting
>
> * What was the outcome of this action?
>
> reconnecting, restarting x11vnc, or rebooting: x11vnc remained sluggish and
> `fb_push ublen NOT ZERO` continued to appear
>
> downgrading to 0.9.13+dfsg-2 and reconnecting: went back to a usable speed
>
> * What outcome did you expect instead?
>
> I did not expect a minor update to change the speed of x11vnc.
It seems that a new libvncserver patch in
debian/patches/0003-rfb-increase-update-buf-size.patch create an ABI
incompatibility between x11vnc and libvncserver.
Could you try this: rebuild x11vnc 0.9.16-7 (as found in Debian
bullseye, if it's bullseye that you use) from source with the latest
libvncserver version (library + dev:pkg) installed?
With the rebuilt x11vnc, does the error persist? Or is it gone, then?
Mike
--
DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940
GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31
mail:
mike.gabriel@das-netzwerkteam.de,
http://das-netzwerkteam.de