Hello Armen, it's hard to tell from just one error message, but it smells of a version mismatch in the libraries. The answers in the stackoverflow thread guessed that, too. So one solution could be to update all packages (Python, Qt, PyQt, PyQtGraph) to their newest version (with apt-get) and take care that the (Python-)versions match! But I remember that was a pain to do under Ubuntu, because it insistet on using an old version of Python for it's internal scripts and a lot of the included packages are not up-to-date. So, I had to get some packages from alternative sources.
My recommended solution would be to use a virtual environent, where you can configure your Python exactly to your needs. I usually use Anaconda ( https://www.anaconda.com/download/) and create a clean environment for each project. I haven't testet the Linux version, but it should be worth a try. There are also other Python-distributions and virtual environments, this is just what I'm going with. I hope it helps! Regards Sebastian Am Mittwoch, 13. September 2017 23:31:27 UTC+2 schrieb Armen Levonian: > > So for some reason pyqtgraph started giving the segmentation fault > immediately upon importing the module. > The strange thing was that after I installed it today for Python 3.52 and > after installing all the other deps, it was working perfectly, including > running examples for PyQt5. > > The other strange thing is that it is working perfectly for Python 2.7 > (with PyQt4). > Google search led me to: > *https://stackoverflow.com/questions/44821475/segmentation-fault-core-dumped-in-python-2-7-when-importing-pyqtgraph > > <https://stackoverflow.com/questions/44821475/segmentation-fault-core-dumped-in-python-2-7-when-importing-pyqtgraph>* > > ...and I am having exactly the same problem but only in Python 3.52. I did > the "gdb Python3" step and it reported the same string issue... > > ... > $ gdb python3 > GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1 > Copyright (C) 2016 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later < > http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "x86_64-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from python3...(no debugging symbols found)...done. > (gdb) run > Starting program: /usr/bin/python3 > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > Python 3.5.2 (default, Nov 17 2016, 17:05:23) > [GCC 5.4.0 20160609] on linux > Type "help", "copyright", "credits" or "license" for more information. > >>> import pyqtgraph > > *Program received signal SIGSEGV, Segmentation fault.* > *strlen () at ../sysdeps/x86_64/strlen.S:106* > *106 ../sysdeps/x86_64/strlen.S: No such file or directory.* > (gdb) > > ... > > > I think the only thing I did between it working and giving a seg fault is > that Mint update updated google Cloud SDK, but I cannot fathom what > relationship that has except that I noticed it generated an error (did not > note it). > > -- You received this message because you are subscribed to the Google Groups "pyqtgraph" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyqtgraph+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/pyqtgraph/c7ce1b64-e6b9-40be-8467-99cbf414fc48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
