Bug 1364726
| Summary: | diodon-test fail with 18479 Floating point exception(core dumped) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Raphael Groner <projects.rg> |
| Component: | xorg-x11-server | Assignee: | X/OpenGL Maintenance List <xgl-maint> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | cosimo.cecchi, mclasen, mtasaka, ofourdan, xgl-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-12 10:27:53 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: | |||
|
Description
Raphael Groner
2016-08-06 16:03:30 UTC
This also happens in rubygem-gtk3 test suite or so. This is perhaps: https://bugzilla.gnome.org/show_bug.cgi?id=768999 https://git.gnome.org/browse/gtk+/commit/?id=f44baf51d9e8616acd9b929d9cfef83a4a3ad00a One possible workaround is to disable randr extension for Xvfb like $ xvfb-run -s '-screen 0 640x480x8 -extension RANDR' -a ./diodon-test Scratch build: http://koji.fedoraproject.org/koji/taskinfo?taskID=15261347 (In reply to Mamoru TASAKA from comment #3) > One possible workaround is to disable randr extension for Xvfb like > $ xvfb-run -s '-screen 0 640x480x8 -extension RANDR' -a ./diodon-test > > Scratch build: > http://koji.fedoraproject.org/koji/taskinfo?taskID=15261347 Well, that's a temporary workaround to let the tests pass. But does that mean a normal user of diodon has to disable randr, too? Or is the bug specific for Xvfb only? I don't have a rawhide/f25 machine to test with. > But does that mean a normal user of diodon has to disable randr, too? Or is the bug specific for Xvfb only?
This is when using Xvfb only. Normal user is not affected with this bug.
lxqt-wallet-3.0.0-1.el7 zulucrypt-5.0.0-2.20160802git064e9db.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-f08257b92c Please ignore comment #6. Wrong bug in bodhi, sorry. (In reply to Mamoru TASAKA from comment #5) > > But does that mean a normal user of diodon has to disable randr, too? Or is the bug specific for Xvfb only? > > This is when using Xvfb only. Normal user is not affected with this bug. Reassigning. This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. |