As someone in a prior bug-report discovered that uncommenting line 27 in dist-packages/gobject/constants.py cures the crash. Actually that line makes no sense as a python statement, but just listing the variable name TYPE_INVALID, without assigning any value in constants.py (which the comment there states is defined in gobjectmodule.c) eliminates the crash.
This would seem to discredit the theory that simultaneous loading of static and dynamic bindings is to blame. Does the variable NEED to be declared in the python even if it's value is assinge in a .c file in order to work ? I'm not knowledgable about the inner workings of the python language. Is this a valid fix? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/896836 Title: Segmentation fault when asking help() for the list of modules To manage notifications about this bug go to: https://bugs.launchpad.net/pygtk/+bug/896836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
