-
Notifications
You must be signed in to change notification settings - Fork 414
Python3 dump core immediately on Pyfa-2.9.3's pyfa.py startup #1968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Did it happen with earlier versions? Also, please post full output of |
I can reproduce the crash on my debian box. It launches fine from venv built by pycharm but fails to launch from venv built manually using the steps above.
To confirm it, launching python file with just:
Also crashes. Most likely related to wx build process. I do not know how to help with that though, it doesn't seem to be bug with pyfa application or packaging. I will investigate it further and make issue in wxPython's repo a bit later. Might be something caused by distributive as well. |
The last version that I was running and that was working for me with setup instructions similar to the ones in my initial bug report was Pyfa-2.7.0. I never tried Pyfa-2.8.0 myself. |
And this is the log of pip3 -v install -r /home/user/bin/Pyfa-2.9.3/requirements.txt inside a fresh python venv |
I suspect that 78836ad broke it (by switching to wx version which is broken in pip). Could you check with |
Filed upstream issue wxWidgets/Phoenix#1220 |
I also experienced the issue. |
See comment in the upstream issue.
I cannot verify it atm, so please check it if you have time. |
still get the segfault after installing that package and reinstalling wxPython4.0.4
|
Was wx package rebuilt or taken from cache? Try again with |
Works after ignoring cache. Though, it may be because I still have the old version installed now.
I can't seem to get rid of it:
|
@AdamGalt seems like you have it installed not just for your venv, but system-wide.
Location shows you where it's installed. Original ticket is for venv installation (if you've executed If you try to get pyfa working, just use 4.0.1 which you already have installed (temporarily remove wxpython from |
@DarkFenX Thank you for clarifying. I've manually removed it now and Pyfa is still working for me as well. |
@maxheise per comment from the upstream issue, you need to install Closing this issue, reopen if it still doesn't work for you. |
After your help mid May I wanted to post a late reply that the current pyfa 2.9.6 works for me with these installation instructions for Ubuntu 18.04, Linux Mint 19.1 Tessa: $ lsb_release -d The Pyfa 2.9.6 tarball is extracted to /home/user/bin/Pyfa-2.9.6/ already. sudo apt-get install libwebkit2gtk-4.0-dev libwebkit2gtk-4.0 python3-wxgtk4.0 python3-logbook python3-matplotlib python3-dateutil python3-requests-cache python3-sqlalchemy python3-cryptography libmarkdown2 python3-roman pypy-bs4 python3-yaml python3-wxgtk-webview4.0 python3-packaging => works Ty |
Glad it helped! |
Bug Report
Python3 dumps core immediately on pyfa.py startup
Expected behavior:
A normal startup of pyfa
Actual behavior:
Dumps core immediately on startup
Detailed steps to reproduce:
python3 -m venv /home/user/bin/python3-venv-pyfa_2019_05_06/
cd /home/user/bin/python3-venv-pyfa_2019_05_06/
source bin/activate
pip3 install -r /home/user/bin/Pyfa-2.9.3/requirements.txt
python3 /home/user/bin/Pyfa-2.9.3/pyfa.py
Speicherzugriffsfehler (Speicherabzug geschrieben)
which is the German translation of of "Segmentation fault ( core dumped )"
Fits involved in EFT format (Edit > To Clipboard > EFT):
Release or development git branch? Please note the release version or commit hash:
pyfa release 2.9.3 downloaded from github
Operating system and version (eg: Windows 10, OS X 10.9, OS X 10.11, Ubuntu 16.10):
lsb_release -d
Description: Ubuntu 18.04.2 LTS
cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
Other relevant information:
python3 --version
Python 3.6.7
The text was updated successfully, but these errors were encountered: