Created attachment 1222163 [details] Example of poedit window Description of problem: After update of wxGTK3, the main window of poedit is unusable. Version-Release number of selected component (if applicable): wxGTK3-3.0.2-29.fc25.x86_64 poedit-1.8.11-1.fc25.x86_64 wxBase3-3.0.2-29.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. Update wxGTK3 to wxGTK3-3.0.2-29 2. Launch poedit and open a PO file 3. Fields of PO file are covered by some strange gray widget. Actual results: Screenshot is attached, main window of Poedit is unusable. Expected results: Fields should be visible. Additional info: https://bodhi.fedoraproject.org/updates/FEDORA-2016-b372d67ade
Yes, I can reproduce the problem. It looks like the problem does not exist with latest wx git, so there is probably another patch that I need to cherry-pick. Thanks for the report.
wxGTK3-3.0.2-30.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cde7d3d168
wxGTK3-3.0.2-30.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-74bef396a8
wxGTK3-3.0.2-30.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-74bef396a8
wxGTK3-3.0.2-30.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cde7d3d168
wxGTK3-3.0.2-30.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
wxGTK3-3.0.2-30.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.