> Hi Picca! Please next time you reassign a bug also CC the maintainer/team that > receives the bug, else we don't get this very text you wrote above :-)
sorry about that. > No, this not seems to be a Qt bug, and even less a Qt5 bug, as the lib > mentioned in the backtrace is from Qt4. By looking at the bug log I am > wondering if you are not happen to be mixing Qt4 and Qt5 in the same package. I am not at all a Qt specialiste, so I red the first lines of the backtrace #0 registerFont (fnt=0xbfffdd24) at text/qfontdatabase.cpp:1025 #1 QFontDatabasePrivate::addAppFont (this=<optimized out>, fontData=..., fileName=...) at text/qfontdatabase.cpp:2436 #2 0xb47ea5dd in QFontDatabase::addApplicationFont (fileName=...) at text/qfontdatabase.cpp:2482 #3 0xb4c5bc0a in ?? () from /usr/lib/python2.7/dist-packages/PyQt5/QtGui.i386-linux-gnu.so #4 0x800d6ba1 in call_function (oparg=<optimized out>, pp_stack=0xbfffde88) at ../Python/ceval.c:4352 then I seems to me that we where talking about PyQT5 (the binding) and then I deducted that the #0 where commin from qt5. How do I know from which library this is comming from. I obtained these backtrace by installing the qt5 debug symbols and not the qt4 ones. > Please double check all your dependencies that you are not mixing Qt4 and Qt5. > And before reassigning to Qt please check that the issue is not in the > bindings. Hint: try coding a minimal example. > Due to the above I'm reassigning you the bug. > It can be caused by a missued of your > library but nevertheless it should not segfault :). > Pass a null pointer to be dereferenced and you will get a segfault. And that's > purely missuse. Yes this si why I like haskell ;) Regards, Fred -- debian-science-maintainers mailing list debian-science-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
