Comment 48 for bug 419501

Jamey Sharp, an X.org upstream, has taken a look at this and said:

"All those I could find look like one of two cases: Either the app called Xlib from multiple threads without calling XInitThreads first; or it opened a Display, fork()ed, and used the Display from both processes. Both would be bugs in the application."

A few duplicates were reported against python-gasp, which was fixed recently. By far the majority of duplicates are against apport-kde, so I tentatively open a Qt task for this and close the libxcb one.