Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#49973 - [x11vnc] Stack Smashing Detected
Attached to Project:
Arch Linux
Opened by Chris (Someguy123) - Wednesday, 06 July 2016, 18:38 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 08 October 2016, 06:53 GMT
Opened by Chris (Someguy123) - Wednesday, 06 July 2016, 18:38 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 08 October 2016, 06:53 GMT
|
DetailsDescription:
X11VNC crashes after just a few minutes, at random, with a stack smashing error. Found the following forum post showing the issue has existed for at least a month: https://bbs.archlinux.org/viewtopic.php?id=213859 Bug reported upstream: https://github.com/LibVNC/x11vnc/issues/27 Steps to reproduce: - Run x11vnc with any Window Manager (I can confirm it crashes with i3wm at the least). - Connect to the VNC server with your client of choice (I have tested it with RealVNC Viewer on OSX, as well as TigerVNC Viewer) - Attempt to browse the web, use the terminal, adjust windows etc. - After a few minutes, x11vnc will crash with "Stack Smashing detected" |
This task depends upon
Closed by Gaetan Bisson (vesath)
Saturday, 08 October 2016, 06:53 GMT
Reason for closing: Fixed
Additional comments about closing: x11vnc-1:0.9.13-9 in [extra]
Saturday, 08 October 2016, 06:53 GMT
Reason for closing: Fixed
Additional comments about closing: x11vnc-1:0.9.13-9 in [extra]
Comment by Daniel Kamil Kozar (XAVeRY) -
Friday, 07 October 2016, 21:48 GMT
Attached is a backport of the relevant commits from the github repo and a PKGBUILD including that patch. Should suffice as long as there is no upstream release.
PKGBUILD
(1.2 KiB)