-
-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sluggish performance and debug messages from x11vnc #220
Comments
UPDATE: This issuse (the ** fb_push ublen NOT ZERO log in systemd) appears in ArchLinux x11vnc-1:0.9.16-5-x86_64. After I update with x11vnc 1:0.9.16.r12.g97d632c-1 built from aur it dispeared.
|
I am also having this issue with Arch x11vnc-1:0.9.16-5-x86_64 since I updated. |
Great to hear that. Could you investigate what fixed the problem in your case? Is there a specific patch applied to x11vnc or one of its dependencies in Arch AUR? |
Just in case it helps, I'm often getting negative numbers in this error message:
|
By building the aur version x11vnc-git 1:0.9.16.r12 it fixed the issue. Thanks |
See this, but this thread posted at 2013-04-03 https://aur.archlinux.org/packages/x11vnc-git And the x11vnc aur package in archlinux still used libjpeg-turbo, and libjpeg-turbo(version 2.1.4-2) contains libjpeg, here's the log
|
Hrmm...interesting. It turns out that simply recompiling the package locally fixed the problem for me as well (on Debian 11), without removing the patch mentioned above. I have no idea what is going on here...but it is unlikely to be an issue with the x11vnc code, so I am going to close this. Thanks for the input! Edit: in Debian 11, this has been fixed in x11vnc 0.9.16-9. |
In Debian 11 testing as well as in Debian 10 since a recent update to libvncserver, x11vnc performance is quite bad when accessing a running X session via ssh tunnel using different VNC viewers (i.e. ssvncviewer on Linux, vnc-viewer/RealVNC on macOS).
The terminal running the ssh session shows repeated output lines from x11vnc, such as:
Those messages can be triggered for example by moving the mouse around the VNC screen.
From the recent appearance of this bug in Debian 10, I was able to attribute the bug to this change in libvncserver:https://github.com/LibVNC/libvncserver/blame/f45672cdc9b749e100be2463b1a04f3a9fc0aa26/rfb/rfb.h#L570
UPDATE_BUF_SIZE has been changed from 30000 to 32768. This macro definition is used in x11vnc as well, more specifically in misc/turbovnc/tight.c.Changing the value back to 30000 and recompiling fixes the problem.The triggered messages are printed out here.
It would be great if someone with a deeper knowledge of x11vnc and associated protocols could comment as I am not certain if things are broken here or maybe even inside the viewer code.
References:
Edit:
Apparently this problem is caused by something else and can be fixed by simply recompiling x11vnc locally.
The text was updated successfully, but these errors were encountered: