Re: [VirtualGL-Users] ERROR: in FBX -- XCopyArea symbol not loaded

[DRC <dco...@us...>]

Which version of VirtualGL?  That is literally the most important detail 
to include in any bug report.

Also, if you're observing that '-c proxy' performs better than the 
default '-c jpeg', then something is terribly wrong.  "Proxy mode" is 
intended for X proxies, e.g. TurboVNC.  It sends the images uncompressed 
through the X11 protocol, which means that, even on gigabit, the most 
you'll see is 30 Megapixels/sec (JPEG can easily achieve twice that on a 
100 Mbit network.)

Also, just to clarify, '-c proxy' fails only with Cygwin but works with 
TurboVNC?  Definitely something amiss there as well.  You're going to 
need to provide a lot more details before I can even begin to figure out 
what's going on.


On 9/3/15 2:28 PM, Michael Mirsky wrote:
> Hello,
>
> I’m new to VirtualGL and I’ve been testing it with my Qt5 app. For the
> most part, it works flawlessly! However, I have run into one issue.
> Specifically, my build of VirtualGL fails with the following error if I
> try to launch my app with the “-c proxy” compression option:
>
> [VGL] ERROR: in FBX—
>
> [VGL]         510: [FBX] ERROR: XCopyArea symbol not loaded
>
> Any ideas of what this error means or what I might have missed during
> compilation? Running with “-c rgb” or the default works.
>
> I first tested with the “official” VirtualGL binary package, and vglrun
> with the “-c proxy” option performs with the least lag. Thus, it would
> be nice to combine that with the xcb interposer so that resize works.
>
> As some background, my VirtualGL server is running on Linux (RHEL6) and
> my client is Windows with Cygwin\X. I’ve tested using TurboVNC and that
> works great, but I’d prefer to get Cygwin\X to work if possible.