Usually Python programs are pretty good approximations of their C
counterparts, but in this case the bug is in PyGTK. It's on line 1098
of gtk.override from the pygtk package.
Actually the bug has been in PyGTK for a long time. It was in the
version distributed in hardy. The reason it's cropping up in Jaunty is
that Python 2.6 has the "PySignal_SetWakeupFd" function that has to be
defined in order for the buggy code path to get invoked. Intrepid uses
2.5, but has this function backported in a patch.
The correct solution would be to inspect the return value of
PySignal_SetWakeupFd and restore it (and close the signal pipe) when the
gtk main loop exits, rather than throwing it away and calling pipe()
every time.
** Changed in: gtk+2.0 (Ubuntu)
Status: New => Invalid
--
gtk_main leaks a file descriptor every time the main loop is run if threads
have been initialized
https://bugs.launchpad.net/bugs/363245
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
