Fedora 37 Final has been delayed by several weeks due to multiple factors (most lately the pending critical openssl vuln). Currently we have Plasma 5.25.5 and KDE Gear 22.08.1 in stable for F37. Plasma 5.26.1 is in updates-testing with broadly positive feedback. 5.26.0 is in updates-testing for F36, and may be pushed stable before the new F37 release date (meaning F36 would be ahead of F37). Given the delays, I'd suggest it makes sense to pull Plasma 5.26.1 or 5.26.2 (which is released but not yet built for Fedora) in for F37 Final. This provides a newer (and hopefully better) experience on the live images, a better impression of freshness for the release, and avoids potential downgrades for people upgrading from F36 before the 0-day update push. This bug is filed for the purpose of being proposed as a freeze exception to allow this to happen. This is part of the broader plan, generally agreed upon at the 2022-10-27 go/no-go meeting, to consider freshening up key components for the delayed release.
FEDORA-2022-23a0a34ea5 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5
FEDORA-2022-23a0a34ea5 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-23a0a34ea5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
+8 in https://pagure.io/fedora-qa/blocker-review/issue/992 , marking accepted.
With all the upstream 5.26 bug reports about multiple display problems getting worse instead of better, jumping to 5.26 may be a poor plan: https://bugs.kde.org/show_bug.cgi?id=385135 Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types https://bugs.kde.org/show_bug.cgi?id=450068 Use of volatile connector IDs to map containments to screens cannot be made to work reliably and should be replaced with something else
It doesn't seem particularly significant, honestly. We're not going to leave F37 on 5.25 for the entire release cycle; if we don't pull 5.26 in at release time we'll pull it in as a 0-day or shortly-after update. Given that, I don't see how those issues make any difference to whether we include it at release time or a little later.
Maybe a relnote would be in order, so those with multiple display configurations could lock down 5.25 before upgrading, and wait for 5.27 before unlocking.
F36 is also being updated to 5.26, so it doesn't seem particularly related to a release transition anyway...
(In reply to Fedora Update System from comment #8) > FEDORA-2022-23a0a34ea5 has been pushed to the Fedora 37 testing repository. > Soon you'll be able to install the update with the following command: > `sudo dnf upgrade --enablerepo=updates-testing --refresh > --advisory=FEDORA-2022-23a0a34ea5` > You can provide feedback for this update here: > https://bodhi.fedoraproject.org/updates/FEDORA-2022-23a0a34ea5 > > See also https://fedoraproject.org/wiki/QA:Updates_Testing for more > information on how to test updates. That's what you said on comment #2. https://bugzilla.redhat.com/show_bug.cgi?id=2138251#c2
FEDORA-2022-23a0a34ea5 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.