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: Maintainers to package upstream PR 3884 3. fedora-release — fedora-release-identity-cloud says "Cloud Edition", Cloud has not been an edition for years — ASSIGNED ACTION: Maintainers to update fedora-release-identity-cloud or group-with-such-authority to waive this. 4. mlocate — F35 with mlocate installed cannot be upgraded to F36 due to conflict with plocate — ASSIGNED ACTION: FESCo to vote on #2765 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. — ON_QA ACTION: QA to check if the behavior reappears 7. sddm — SDDM crashes upon log out from the KDE session. — NEW ACTION: Maintainers to diagnose and fix issue Proposed blockers ----------------- 1. firefox — f36 composes still have firefox 96, f34 f35 have firefox 97 — NEW ACTION: Maintainers to resolve build issues 2. gnome-control-center — After upgrade gnome-control-center to 42~beta-1.fc37 unable to configure VPN connection — NEW ACTION: Reporter to confirm the behavior exists on F36 3. initial-setup — dnf system-upgrade 35 to 36 fails with various pipewire wireplumber conflicts — NEW ACTION: Maintainers to package upstream PR 297 (or find a better fix) 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. There's ongoing discussion trying to come up with a potential fix, however we still seem to be a long way from that point. 2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2032085 — POST 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. Upstream PR has a fix for F36: https://github.com/rhinstaller/anaconda/pull/3884 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. A ticket is pending with the Fedora Council, although Cloud could proceed with removing the word "Edition" for now: 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. FESCo #2765 requests approval to have plocate replace mlocate on upgrade. 5. libinput — 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. We'll keep this bug open to keep checking if the bad cache returns. 7. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2057419 — NEW SDDM crashes upon log out from the KDE session. When logging out of a Plasma session, SDDM does not restart, leaving the user at a terminal. A reboot is required to fix. This may be specific to Wayland. Proposed blockers ----------------- 1. 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. 2. gnome-control-center — 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 bug is reported against Rawhide and there's no confirmation at this moment that the behavior exists on F36. 3. initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2057600 — NEW 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. An upstream PR reverts the partial fix while a better long-term solution is found: https://github.com/clalancette/oz/pull/297 -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
