Bug 1396760
Summary: | qbs randomly segfaults | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Pavel Alexeev <pahan> |
Component: | qt-creator | Assignee: | Itamar Reis Peixoto <itamar> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 26 | CC: | davejohansen, helio, itamar, jreznik, manisandro, pahan, rdieter |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-29 11:46:26 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: | |||
Bug Depends On: | |||
Bug Blocks: | 1307977 |
Description
Pavel Alexeev
2016-11-19 21:54:11 UTC
Fixed in qt-creator-4.2.0-0.3.beta1.fc26 Unfortunately I see still crash in rawhide: https://kojipkgs.fedoraproject.org//work/tasks/991/16640991/build.log on qutim build. Let's wait for qt-creator-4.2.0-rc1 which should be out any day now. Please retest with qt-creator-4.2.0-0.4.rc1.fc26 Thank you Sandro. It looks better. At least x86_64 and i686 build has been done. But other arches still failed with Segmentation fault. Please look for example that build: https://koji.fedoraproject.org/koji/taskinfo?taskID=17183732 Sandro do you plan fix it on PPC? I'm building qt-creator-4.2.1 now [1], hoping it helps. [1] https://koji.fedoraproject.org/koji/taskinfo?taskID=17391503 It still crashed in rawhide for ppc64le, aarch64 and ppc64. Please look at: https://koji.fedoraproject.org/koji/taskinfo?taskID=17443644 Sandro do you plan work on this? Is it at least reported upstream? Hi, sorry this keeps falling off my radar simply because I don't have the hardware to debug it. I've now filed an upstream bug [1], if you have access to such hardware and can provide more meaningful infos upstream that would be great. [1] https://bugreports.qt.io/browse/QBS-1103 At least for arm machines you could use test machines kindly provided by Kevin: https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers I collected a full stracktrace and valgrind output on ppc64le on copr and submitted the info upstream. This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle. Changing version to '26'. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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. |