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.
** Also affects: qt4-x11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: qt4-x11 (Ubuntu)
Status: New => Confirmed
** Changed in: libxcb (Ubuntu)
Status: Incomplete => Invalid
--
apport-kde assert failure: python: ../../src/xcb_io.c:242: process_responses:
Assertion `(((long) (dpy->last_request_read) - (long) (dpy->request)) <= 0)'
failed.
https://bugs.launchpad.net/bugs/419501
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxcb in ubuntu.
_______________________________________________
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
