Bug 1911344
| Summary: | spyder SIGSEGV-s on Open->File dialog | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | oleg.makarenko | ||||
| Component: | qgnomeplatform | Assignee: | Jan Grulich <jgrulich> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | jgrulich, m, nonamedotc | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | qgnomeplatform-0.7.0-2.fc33 qgnomeplatform-0.7.0-2.fc32 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2021-01-07 01:15:12 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
oleg.makarenko
2020-12-28 18:56:14 UTC
These are the components on my system $ rpm -qa *spyder python3-qt5 qt5-qtbase python3-spyder-4.1.5-1.fc33.noarch qt5-qtbase-5.15.2-2.fc33.x86_64 python3-qt5-5.15.0-4.fc33.x86_64 And, I have not been able to reproduce this crash at all. Do you see anything other than segfault if you open spyder from a terminal? *** Bug 1911614 has been marked as a duplicate of this bug. *** Today: - installed a clean Fedora 33 into a virtual machine with all default settings - dnf updated it with dnf update -y - to crash spyder3 run it and press Ctrl-O to open a file chooser On my console I can see only: [test@localhost ~]$ spyder3 QSocketNotifier: Can only be used with threads started with QThread "/proc/2309/root" Segmentation fault (core dumped) On the test machine the crush is automatically reported to bugzilla and in "problem Reporter" I can see the culprit traps: spyder3[21411] general protection fault ip:7fc755700624 sp:7ffe9d9714d8 error:0 in libqgnomeplatform.so[7fc7556f8000+30000] [test@localhost ~]$ rpm -q qgnomeplatform qgnomeplatform-0.7.0-1.fc33.x86_64 My blind guess is that qgnomeplatform-0.6 to 0.7 added new xdg-desktop-portal file chooser from QT and wants to use it on my machine and it is not working when it is called from spyder3. Okay, I can now reproduce this and this affects spyder 4.2.x as well. Let me move this the component to qgomeplatform for comment. FEDORA-2021-4badd755a9 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-4badd755a9 FEDORA-2021-c8bf9e1d53 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c8bf9e1d53 qgnomeplatform-0.7.0-2.fc33.x86_64.rpm has fixed spyder3 crash for me. Many thanks. FEDORA-2021-4badd755a9 has been pushed to the Fedora 32 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4badd755a9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4badd755a9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-c8bf9e1d53 has been pushed to the Fedora 33 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c8bf9e1d53` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c8bf9e1d53 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2021-c8bf9e1d53 has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2021-4badd755a9 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. |