Description of problem: I can't start spyder2 (python-spyder2). It crashes on start every time. Abrt claims the traceback is not useful enough to create a bug report. I'll attach the files anyway, maybe they'll help. The FAF report is: https://retrace.fedoraproject.org/faf/reports/1772144/ Version-Release number of selected component (if applicable): python2-spyder-3.1.4-2.fc26.noarch How reproducible: always Steps to Reproduce: 1. start spyder
Created attachment 1295813 [details] backtrace
Created attachment 1295814 [details] core_backtrace
Created attachment 1295815 [details] journal.txt
python-QtPy-1.3.1-1.fc26 spyder-3.2.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-42dc455c05
python-QtPy-1.3.1-1.fc27 spyder-3.2.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-89fbfdd482
python-QtPy-1.3.1-1.fc27 spyder-3.2.1-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-89fbfdd482
python-QtPy-1.3.1-1.fc26, spyder-3.2.1-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-42dc455c05
python-QtPy-1.3.1-1.fc27, spyder-3.2.1-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-89fbfdd482
Could we get a F26 update as well?
yes. I will update directly to 3.2.2 in a day or two.
Can you try this for launching spyder (py2)? https://koji.fedoraproject.org/koji/taskinfo?taskID=21717585
If this works, I will push 3.2.2 as an update.
python-QtPy-1.3.1-1.fc27 spyder-3.2.2-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-89fbfdd482
python-QtPy-1.3.1-1.fc26 spyder-3.2.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-42dc455c05
python-QtPy-1.3.1-1.fc27, spyder-3.2.2-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-89fbfdd482
Created attachment 1324648 [details] screenshot launching spyder2 kparal - Are you still seeing the crash with 3.2.2? I was able to reproduce the crash with older version. But, I am fairly certain I fixed the underlying issue. I cannot reproduce the crash any more. Can you try launching spyder from a terminal using this? spyder --reset
python-QtPy-1.3.1-1.fc26, spyder-3.2.2-1.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-42dc455c05
(In reply to Mukundan Ragavan from comment #16) > kparal - Are you still seeing the crash with 3.2.2? Yes, I commented here: https://bodhi.fedoraproject.org/updates/python-QtPy-1.3.1-1.fc26%20spyder-3.2.2-1.fc26#comment-657521 > I was able to reproduce the crash with older version. But, I am fairly > certain I fixed the underlying issue. I cannot reproduce the crash any more. I can :) ABRT doesn't want me to allow creating a bug report, because the traceback is "unusable". But I can give you a traceback from gdb if you want. > Can you try launching spyder from a terminal using this? > > spyder --reset Good that I looked first what this does: --reset Remove all configuration files! If I moved "~/.spyder2" and "~/.config/spyder" away, it did not help. "spyder --reset" did not help either. Always the same crash (well at least abrt increases the crash count, so it considers those crashes to be the same). $ spyder --reset Segmentation fault (core dumped) I also created a completely clean user account and tried it there, same result. I also tried in a clean F26 VM, and spyder works. Both machines are F26 fully updated with updates-testing. I went package by package comparing the different rpms installed on both machines, and I found the difference. The problem is: pygtk2-2.24.0-16.fc26.x86_64 If pygtk2 is installed, spyder crashes on start.
Finally we are getting somewhere! I can reproduce this consistently. I will file this upstream. This is not resolved even in Spyder 3.2.3. Let me see what upstream says.
Also, with the prior versions, there was an issue with pylint that I fixed (your launches would not even have reached that point). But, this is much more severe.
python-QtPy-1.3.1-1.fc26, spyder-3.2.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
reopening.
python-QtPy-1.3.1-1.fc27, spyder-3.2.2-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.
I am also seeing these issues when trying to run Spyder2 on Fedora26. However, if I git spyder directly from git and run bootstrap back to qt4 I see: python2 bootstrap.py --gui=pyqt4 Traceback (most recent call last): File "bootstrap.py", line 52, in <module> "Invalid GUI toolkit option '%s'" % options.gui AssertionError: Invalid GUI toolkit option 'pyqt4' [xray@localhost spyder]$ python2 bootstrap.py --gui=pyqt Executing Spyder from source checkout Revision 55db01bf1, Branch: master 01. Patched sys.path with /home/xray/build/spyder 02. Skipping GUI toolkit detection 03. Imported Spyder 4.0.0.dev0 [Python 2.7.13 64bits, Qt 4.8.7, PyQt4 (API v2) 4.12 on Linux] 04. Running Spyder /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) Bootstrap completed in 00:00:00.5714 loaded the Generic plugin Where as the same run without pytqt4 is pretty similar to that running spyder2 from the rpm. python2 bootstrap.py Executing Spyder from source checkout Revision 55db01bf1, Branch: master 01. Patched sys.path with /home/xray/build/spyder 02. PyQt5 is detected, selecting 03. Imported Spyder 4.0.0.dev0 [Python 2.7.13 64bits, Qt 5.7.1, PyQt5 5.8.1 on Linux] 04. Running Spyder /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) Bootstrap completed in 00:00:00.5431 Segmentation fault (core dumped)
*** Bug 1529972 has been marked as a duplicate of this bug. ***
*** Bug 1532346 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.