> From the original bug report (the only thing I had up to know): I attached my backtrace in the bug report. this is why we are speaking about different things;)
> Then if the gdb backtrace in the original bug report is to be trusted then > you are indeed mixing Qt4 and Qt5. And you can expect dragons for doing that > ;-) the original bactrace was done by the initial bug reporter then I tryed to reproduce the failure and I also got a segfault, but for a different reason. so I think that there is a problem in the python pyqt5 binding... let's investigate Cheers -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
