The most interesting thing about it is that the order of the three import statements in demo.py has an effect on what happens:
# Finally leads to the segfault described in this bug report. from kiwi.environ import Application from gobject import property, GObject from demo_util import GObjectSingletonMeta # Everything works fine from gobject import property, GObject from kiwi.environ import Application from demo_util import GObjectSingletonMeta # Raises # Exception exceptions.TypeError: 'could not get typecode from object' in <module 'threading' from '/usr/lib/python2.5/threading.pyc'> ignored from gobject import property, GObject from demo_util import GObjectSingletonMeta from kiwi.environ import Application Can anyone confirm this behaviour? -- Segfault starting with 2.16.1-0ubuntu2 using Python 2.5 https://bugs.launchpad.net/bugs/334784 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygobject in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
