Bug 2081093
| Summary: | Defaulting to wayland causes mame to crash | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Julian Sikorski <belegdol> |
| Component: | SDL2 | Assignee: | Igor Raits <igor.raits> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | dchen, igor.raits, ngompa13, spotrh |
| Target Milestone: | --- | ||
| 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: | 2022-05-08 02:03:30 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
Julian Sikorski
2022-05-02 18:06:15 UTC
I have now managed to submit a PR for mame so that it defaults to the x11 videodriver on Linux: https://github.com/mamedev/mame/pull/9676 With this change mame can keep working with the default config if you decide to keep wayland the default. (In reply to Julian Sikorski from comment #1) > I have now managed to submit a PR for mame so that it defaults to the x11 > videodriver on Linux: > https://github.com/mamedev/mame/pull/9676 > With this change mame can keep working with the default config if you decide > to keep wayland the default. The intent is to keep Wayland the default, as it's the default for several months: https://src.fedoraproject.org/rpms/SDL2/c/adf5181d820ce35e08278903de99b3cc7b9d530c?branch=rawhide Thanks for confirming. As you saw, the PR got merged and I am building a mame update including the changes from the PR. FEDORA-2022-4f48985ac7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f48985ac7 FEDORA-2022-1ec7d5e34d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ec7d5e34d FEDORA-2022-d7be26f27b has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d7be26f27b FEDORA-2022-4f48985ac7 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-4f48985ac7` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4f48985ac7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-1ec7d5e34d has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-1ec7d5e34d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-1ec7d5e34d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-d7be26f27b has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-d7be26f27b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d7be26f27b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-4f48985ac7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-1ec7d5e34d has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-d7be26f27b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |