MAVExplorer: aborts on CentOS 7 (64bit)

When starting MAVExplorer.py without giving a log filename:

MAV> [xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
MAVExplorer.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aborted (core dumped)

When starting on a log, it crashes later, after creating the root window:

[holger-local@atg ~]$ MAVExplorer.py /run/media/holger-local/2A25-F76A/APM/LOGS/69.BIN
MAV> [xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
python: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

(MAVExplorer.py:8462): Gdk-ERROR **: The program 'MAVExplorer.py' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
(Details: serial 1367 error_code 14 request_code 138 minor_code 27)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Aborted (core dumped)

Start with MAVExplorer.py and reproduce the reported launch both without a log filename and with the supplied .BIN log on CentOS 7. Trace the XCB/GDK failure and verify that MAVExplorer starts and opens the log without aborting or producing the reported X server errors.

Written by the indexing model from the issue text.