FS#77268 - [x11vnc] libvncserver 0.9.14 update causes serious lag

Attached to Project: Community Packages
Opened by Tom Yan (tom.ty89) - Thursday, 26 January 2023, 12:08 GMT
Last edited by Daniel Bermond (Bermond) - Saturday, 04 February 2023, 15:29 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Felix Yan (felixonmars)
Daniel Bermond (Bermond)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I tested both 0.9.14-1 and 0.9.14-2, so it does NOT seem like it has something with the new lzo linkage. Also, I rebuilt (asp) x11vnc myself and somehow the problem does NOT exist with that build. (I reinstalled back and forth to make sure it was not due to some temporary network issue.)

I don't know if it's really just the rebuild solved it, or it's because one of the new linkage x11vnc gained in my own build:

+ libXcursor.so.1
+ libcairo.so.2
+ libfontconfig.so.1
+ libfreetype.so.6
+ libxcb-render.so.0
+ libxcb-shm.so.0
+ libpixman-1.so.0
+ libexpat.so.1
+ libbz2.so.1.0
+ libharfbuzz.so.0
+ libgraphite2.so.3
+ libglib-2.0.so.0
+ libpcre2-8.so.0

(from ldd diff)



Additional info:
* package version(s) 1:0.9.16-6
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Daniel Bermond (Bermond)
Saturday, 04 February 2023, 15:29 GMT
Reason for closing:  Fixed
Additional comments about closing:  x11vnc 1:0.9.16-7
Comment by Toolybird (Toolybird) - Sunday, 29 January 2023, 06:07 GMT
> new linkage x11vnc gained in my own build

I don't quite understand what you mean above. Are you not building in a clean chroot? [1]

[1] https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot
Comment by Tom Yan (tom.ty89) - Tuesday, 31 January 2023, 15:47 GMT
> Are you not building in a clean chroot?

No I wasn't. Thanks for the tip, and I just did that instead, and the problem is not observed in the "clean" build either, and I also reinstalled the package on the repo (which is 0.01 MiB smaller according to pacman, if that's relevant at all) again to (re-)confirm that it is problematic, and it is.

TL;DR, a rev bump should close this.
Comment by Daniel Bermond (Bermond) - Saturday, 04 February 2023, 14:50 GMT
@tom.ty89 Could you please test x11vnc 1:0.9.16-7 which is currently at [community-testing]?
Comment by Tom Yan (tom.ty89) - Saturday, 04 February 2023, 15:09 GMT
Works fine. Thanks!
Comment by Daniel Bermond (Bermond) - Saturday, 04 February 2023, 15:29 GMT
@tom.ty89 Thank you for the confirmation and for opening this task.

I wonder if the dependency changing on libvncserver might have caused an ABI change.

Package moved to the stable repositories. Closing.

Loading...