ubuntu-x-swat team mailing list archive

[Robert Schroll <rschroll@xxxxxxxxx>]

I don't know if this helps or not, but I've found a work-around for my
test case.  The trick is to hold off on importing gtk and vte until
after the child process forks off.  I'm guessing that the error is due
to two separate processes holding the same objects.  (This affects both
gtk and vte, but I suspect the problem with vte is that it imports gtk
within itself.)

Unfortunately, this is likely not a feasible solution for most real
cases.  If the fork is triggered by some user action, the UI must be up
before the fork.  I tried to delete all references to the module in the
child process, but that didn't work.  Some online sources claim that
this will only work for pure python modules; I'm guessing that GTK
isn't.

I want to emphasize that my test case does not fail on Jaunty.  Is there
any evidence of this bug prior to Karmic?

** Attachment added: "Test case work-around"
   http://launchpadlibrarian.net/38908962/echotest.workaround.py

-- 
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.