Description of problem: 0ad worked fine until I upgraded box to Ryzen 3900X CPU. Now it won't start, instead gives error: cache.cpp(43): Assertion failed: "cache.Validate()" Known problem has been fixed upstream. Can we get a new version build for F30? https://trac.wildfiregames.com/ticket/4360 See patch in comment 23 Version-Release number of selected component (if applicable): 0ad-0.0.23b-6.fc30.x86_64 How reproducible: always Steps to Reproduce: 1. Put 0ad on a Ryzen 3xxx CPU 2. type 0ad at the command line 3. Actual results: cache.cpp(43): Assertion failed: "cache.Validate()" Assertion failed: "cache.Validate()" Location: cache.cpp:43 (AddCache) Call stack: (0x989aa5) /bin/pyrogenesis() [0x989aa5] (0x93f8e1) /bin/pyrogenesis() [0x93f8e1] (0x940c47) /bin/pyrogenesis() [0x940c47] (0x9413f9) /bin/pyrogenesis() [0x9413f9] (0x9816ae) /bin/pyrogenesis() [0x9816ae] (0x981cb8) /bin/pyrogenesis() [0x981cb8] (0x98205d) /bin/pyrogenesis() [0x98205d] (0x9b8203) /bin/pyrogenesis() [0x9b8203] (0x981db2) /bin/pyrogenesis() [0x981db2] (0x983b0a) /bin/pyrogenesis() [0x983b0a] (0x9b8203) /bin/pyrogenesis() [0x9b8203] (0x9838de) /bin/pyrogenesis() [0x9838de] (0x670bba) /bin/pyrogenesis() [0x670bba] (0x6666f8) /bin/pyrogenesis() [0x6666f8] (0x47a753) /bin/pyrogenesis() [0x47a753] (0x46983e) /bin/pyrogenesis() [0x46983e] errno = 0 (Error during IO) OS error = ? ** no graphical screen is shown ** Expected results: should start the game and show initial screen Additional info: Looks like the new Ryzens do something weird with the L3 cache that 0ad isn't expecting.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-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 '30'. 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 30 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.
Bug persists in F31: 0ad-0.0.23b-9.fc31.x86_64 The patch I provide in original post completely fixes the problem with just one line changed. Here's a more direct link to the patch: https://trac.wildfiregames.com/changeset/23262 It is patched upstream, but no idea when that newer version is going to be released to the point Fedora has it.
Thanks! I went ahead and backported this in https://src.fedoraproject.org/rpms/0ad/c/67e2fa2f0b66e9aeb6256fe22df151efde41de8f?branch=master
FEDORA-2020-fbc02b5d11 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbc02b5d11
FEDORA-2020-14ac92302f has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-14ac92302f
FEDORA-FLATPAK-2020-6c920b415d has been submitted as an update to Fedora 32 Flatpaks. https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-6c920b415d
FEDORA-2020-14ac92302f has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-14ac92302f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-14ac92302f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-fbc02b5d11 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-fbc02b5d11` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-fbc02b5d11 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-FLATPAK-2020-6c920b415d has been pushed to the Fedora 32 Flatpaks testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-FLATPAK-2020-6c920b415d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-FLATPAK-2020-6c920b415d has been pushed to the Fedora 32 Flatpaks stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-14ac92302f has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
That fixed it! I left karma
Great! Thanks, Trevor.
FEDORA-2020-fbc02b5d11 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.