Bug filed: https://github.com/TigerVNC/tigervnc/issues/218
I am not sure how much context to include. On Tue, Oct 13, 2015 at 4:32 PM, Brian Hinz <[email protected]> wrote: > Would you mind filing a bug report on the TigerVNC github tracker so that > we can follow up on it there? And since that image looks like an ASIC > layout, can you tell me what application triggers it so I can try to > reproduce (you can email me off list if you want). > > Thanks, > -brian > > On Tue, Oct 13, 2015 at 6:20 PM, Brett Williams wrote: > >> I've been unable to reproduce the problem using the TurboVNC server. >> >> On Tue, Oct 13, 2015 at 3:05 PM, DRC wrote: >> >>> OK, well the image is definitely corrupt, meaning that this is a >>> server-side issue. Is there any way you can try to reproduce the issue >>> using the TurboVNC 2.0 server? Building the TigerVNC Server isn't exactly >>> straightforward, so in order for me to send you an instrumented binary with >>> the afore-mentioned codec checks, I'm going to have to do that using our >>> server code. >>> >>> It may also be that there is simply a rare bug in the TigerVNC encoder >>> that doesn't affect the TurboVNC Server. >>> >> > > ------------------------------------------------------------------------------ > > _______________________________________________ > TurboVNC-Users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/turbovnc-users > >
------------------------------------------------------------------------------
_______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
