> infact I don't think it is: I first upgraded the QT4 stack, and still > segfault, then python-qt4, still segfault, only after upgradng also > libqtwebkit4 the segfault gone away.
do you have the version before and after ? that way I should prevent spyder to be installed with the wrong libqtwebkit4 > I don't know, maybe ask the QT4 maint? I will look for the libqtwebkit4 bugs for now > Well, you'd have to check if the version in testing of > qt4/python-qt/libwebkitqt don't make spyder segfault. Else, I think > it's better not to transit to testing until it's working correctly > out-of-the-box (which currently doesn't). I un-install all the qt4 library from my unstable box then switch to testing repository and re-install spyder 2.0.12 from testing. guest what it works out of the box. then I upgraded to spyder 2.1.1 and it was also ok. so it seems that spyder segfault for a faulty combination of python-qt4 / libqtwebkit4. I doesn not seems to me that this is a spyder bug. Maybe a Break should be added to libqtwebkit4 to avoid installation of the faulty combination I will forward this bug to python-qt4 if you are ok with my "analyse". Cheers, Fred -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
