xpra icon
Bug tracker and wiki


OpenGL Debugging

See also: wiki/ClientRendering and OpenGL client rendering

The first step is to run the client with -d opengl, this should log a lot more information about opengl calls and is often enough to spot the source of the problem

Then there is also the environment variable XPRA_OPENGL_DEBUG=1 which will enable the GREMEDY extension if present.

If these options are not sufficient to identify the source of the problem, you can use other tools to dig into the opengl rendering:

Apitrace Installation

The *Apitrace* tool will get a dump of the OpenGL command stream, allowing it to be sent to the developers for replaying and investigation.

  • On Linux:

Download Apitrace, build it according to the documentation: apitrace INSTALL

  • On Windows:

You can use pre-built binaries found at http://people.freedesktop.org/~jrfonseca/apitrace/ Try to always use the latest version and fallback to an older one if it doesn't work.

Apitrace Usage

This trace will enable you to replay the actions of the client without having to re-run it; giving you additional error tracing, ability to send the trace to another person, and ability to replay the exact same steps every time.

Use as follows:

$ apitrace trace xpra attach <your regular commandline>
  • Do whatever is needed to reproduce the issue you are experiencing. Beware: Apitrace is keeping a copy of everything you do in RAM, it's going to be huge, so don't run the session for too long, and focus on reproducing one issue at a time.
  • Exit Xpra when done
    $ qapitrace

File -> load the trace Then go to Trace -> Replay and check both boxes

Apitrace will replay your trace and report in the bottom panel any errors it found, with additional explanation as compared to what the GL driver typically gives.

Be ready to send the .trace file to the developers for further investigation.

Last modified 10 months ago Last modified on 06/27/16 15:18:58