The Go/No-Go meeting for the Early target date (2022-03-15) is Thursday, which means we want to have a release candidate by Tuesday. Action summary ==================== Accepted blockers ----------------- 1. anaconda — When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout — ASSIGNED ACTION: Maintainers to fix issue 2. anaconda — Some variants are missing /etc/resolv.conf symlink (use systemd-resolved) — POST ACTION: QA to verify FEDORA-2022-cf175d0e19 3. fedora-release — fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years — ASSIGNED ACTION: none 4. mlocate — F35 with mlocate installed cannot be upgraded to F36 due to conflict with plocate — ASSIGNED ACTION: Maintainers to update packages to correctly handle obsoletes 5. mutter — GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available — ASSIGNED ACTION: Upstream to fix mutter to support multiple capabilities on a device 6. plasma-discover — Discover does not display applications correctly. — VERIFIED ACTION: none 7. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — NEW ACTION: Maintainers to resolve build issues 8. oz — Initial Setup startup failed due to invalid kickstart file — ON_QA ACTION: QA to verify FEDORA-2022-c263b25459 Proposed blockers ----------------- 1. NetworkManager-openvpn — After upgrade gnome-control-center to 42~beta-1.fc37 unable to configure VPN connection — NEW ACTION: Upstream to update plugins for GTK4 2. dnfdragora — On Fedora 36 KDE, dnfdragora does not start. — NEW ACTION: Maintainers to fix issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2016613 — ASSIGNED When running anaconda on Wayland with two keyboard layouts configured, hitting any modifier key with the second layout selected switches to the first layout adamwill's research shows that this bug has existed since F25, but became more viisble after KDE switched to Wayland by default. This bug was deferred to F36 Beta under the "too hard to fix" exception. jkonecny is working on a fix to disconnect keyboard control between Anaconda and the live environment. 2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — ON_QA Some variants are missing /etc/resolv.conf symlink (use systemd-resolved) Some variants are not using systemd-resolved as intended. With some recently-merged changes to Anaconda, this appears to be working correctly now, at least for ostree variants. FEDORA-2022-cf175d0e19 contains a candidate fix. 3. fedora-release — https://bugzilla.redhat.com/show_bug.cgi?id=2018271 — ASSIGNED fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years Waived from F35 final under the "late blocker exception." Cloud WG is working on a proposal to re-promote Cloud to Edition status, but that will not happen for F36 release cycle. Council is poised to waive this: https://pagure.io/Fedora-Council/tickets/issue/389 4. mlocate — https://bugzilla.redhat.com/show_bug.cgi?id=2052433 — ASSIGNED F35 with mlocate installed cannot be upgraded to F36 due to conflict with plocate The original change proposal planned for mlocate and plocate to be parallel available in F36. However, this turns out to be more challenging than expected. We have a path forward that will correctly handle upgrades will allowing users to opt into keeping mlocate, it just needs to be implemented. 5. mutter — https://bugzilla.redhat.com/show_bug.cgi?id=2017043 — NEW GNOME doesn't accept input from wireless keyboard if there's not another "keyboard" input available On some hardware, devices with multiple capabilities that include keyboard do not get registered as a keyboard. Thus they only work if another keyboard is connected. It seems to mostly (or exclusively) affect some ARM hardware. This appears to be a design flaw in mutter and is reported upstream as https://gitlab.gnome.org/GNOME/mutter/-/issues/2154 6. plasma-discover — https://bugzilla.redhat.com/show_bug.cgi?id=2057531 — NEW Discover does not display applications correctly. Discover was only showing Flatpaks, not RPMs. Refreshing appstream partially helped. In recent composes, the behavior no longer appears. 7. firefox — https://bugzilla.redhat.com/show_bug.cgi?id=2057193 — NEW f36 composes still have firefox 96, f34 f35 have firefox 97 Builds of Firefox 97, which contains security fixes, are failing on F36 and Rawhide due to a GCC 12 internal error. FEDORA-2022-e056239611 contains a fix for those issues, but is apparently incomplete. 8. oz — https://bugzilla.redhat.com/show_bug.cgi?id=2057600 — ON_QA Initial Setup startup failed due to invalid kickstart file A previous fix for the "initial-setup doesn't require creating an admin user" (RHBZ 2015490) assumes a kickstart file will be available, which is not the case. This results in ARM images not booting to initial-setup. This has been reverted in FEDORA-2022-c263b25459 Proposed blockers ----------------- 1. NetworkManager-openvpn — https://bugzilla.redhat.com/show_bug.cgi?id=2057719 — NEW After upgrade gnome-control-center to 42~beta-1.fc37 unable to configure VPN connection VPN connections can't be configured with recent gnome-control-center builds. This appears to be because the NetworkManager-* plugins are still using GTK3, which can't work with a GTK4 gnome-control-center. Work is in progress to update the plugins. 2. dnfdragora — https://bugzilla.redhat.com/show_bug.cgi?id=2060414 — NEW On Fedora 36 KDE, dnfdragora does not start. dnfdragora fails with a libyui error. There seems to be a bootstrap issue because libyui-bindings is part of libyui now. The question of whether two graphical package managers can be blocking is under discussion. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
