On 08.01.20 09:04, Mike Gabriel wrote:
> I attached a .debdiff that reflects todays regression fix upload to
> buster-pu (I also did one to stretch-pu). I cherry-pick 2 more patches
> from upstream that relate to pthreading in libvncserver. I was able to
> reproduce your x11vnc crash on buster and
Hi Daniel,
On Sa 04 Jan 2020 01:07:21 CET, Daniel Reichelt wrote:
On 02.01.20 16:39, Daniel Reichelt wrote:
With 7e63df224aa45a8b541cd63a870594454aba7526 applied, this happens 9
out of 10 times.
Actually, that's crap.
I noticed a ton of running x11vnc processes and re-tried ~debu10 with
7e
On 02.01.20 16:39, Daniel Reichelt wrote:
> With 7e63df224aa45a8b541cd63a870594454aba7526 applied, this happens 9
> out of 10 times.
Actually, that's crap.
I noticed a ton of running x11vnc processes and re-tried ~debu10 with
7e63df224aa45a8b541cd63a870594454aba7526 applied.
Result: just the err
> Does this upstream commit being added to the patches in +deb10u2 fix
> your issue?
> https://github.com/LibVNC/libvncserver/commit/7e63df224aa45a8b541cd63a870594454aba7526.patch
Not really.
With just ~debu10, 1 out of 10 times, the client window would stay open,
but I wasn't able to transmit an
Hi Daniel,
thanks for this regression report.
On Mo 30 Dez 2019 14:01:04 CET, Daniel Reichelt wrote:
Hi all,
the new use-after-free patches introduced in 0.9.11+dfsg-1.3~deb10u2
hurt connections to servers provided by x11vnc.
Previously, a server initiated by
x11vnc -nopw -auth guess -disp
Hi all,
the new use-after-free patches introduced in 0.9.11+dfsg-1.3~deb10u2
hurt connections to servers provided by x11vnc.
Previously, a server initiated by
x11vnc -nopw -auth guess -display :0 -forever
was perfectly fine to connect to using tightvncviewer. Now, with
~deb10u2, the remote wind
6 matches
Mail list logo
