© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
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?