Action summary ==================== Accepted blockers ----------------- 1. anaconda — Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition — ON_QA ACTION: QA to verify FEDORA-2022-c20d42f3bc 2. gnome-initial-setup — Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain — VERIFIED ACTION: (none) 3. gnome-shell — GNOME Initial Setup uses the English keyboard, instead of the default keyboard — VERIFIED ACTION: (none) 4. greenboot — greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." — NEW ACTION: Maintainers to diagnose issue 5. grub2 — Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader — NEW ACTION: QA to finalize updated criterion proposal 6. mesa — totem: nouveau_pushbuf_data(): totem killed by SIGABRT — NEW ACTION: Maintainers to update mesa with fixes for F37 Proposed blockers ----------------- 1. abrt — Abrt does not report a segfault which is reported in journalctl. — ASSIGNED ACTION: Maintainers to diagnose issue 2. nautilus — Nautilus thumbnailing doesn't work on hidpi screens — NEW ACTION: Upstream to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2088113 — ON_QA Custom partitioning with 2 drives selected, bootloader fails to install due to one drive not having a BIOS Boot partition When using custom partitioning on two drives with /boot on a RAID 1 device, the installer only creates one BIOS boot. grub2-install is run against both drives, but the second fails because it has no BIOS boot partition. FEDORA-2022-c20d42f3bc contains a candidate fix. 2. gnome-initial-setup — https://bugzilla.redhat.com/show_bug.cgi?id=2123494 — VERIFIED Unable to set up enterprise account with gnome-initial-setup, clicking continue does not join the domain Initially the buttons were missing. Update FEDORA-2022-50e585b456 fixed that issue, however clicking the button does not joing the domain. Instead, the user is returned to the domain credentials screen, resulting in an endless loop. gnome-initial-setup-43.0-3.fc37 contains a verified fix. 3. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2121110 — ASSIGNED GNOME Initial Setup uses the English keyboard, instead of the default keyboard Regardless of the default keyboard setting, g-i-s uses the English keyboard. Relatedly, new users have the English keyboard selected, even though another language is shown as the default. FEDORA-2022-b14944cb83 contains a verified fix. 4. greenboot — https://bugzilla.redhat.com/show_bug.cgi?id=2121944 — NEW greenboot-grub2-set-counter.service fails on 38 IoT with "cannot open `/boot/grub2/grubenv.new`: No such file or directory." greenboot service fails on a file-not-found error. This also results in rebase tests failing because of conflicts with the rebase triggered by the greenboot failure. 5. grub2 — https://bugzilla.redhat.com/show_bug.cgi?id=2049849 — NEW Windows with bitlocker enabled can't be booted, needs to use bootnext instead of chainloader Dual-booting recent Windows 10 system with TPM 2.0 fails because bitlocker can't be unsealed by the TPM. This was waived to F37 under the "difficult to fix" exception. A proposed change to the release criteria may exclude this from blocker status. 6. mesa — https://bugzilla.redhat.com/show_bug.cgi?id=2123274 — NEW totem: nouveau_pushbuf_data(): totem killed by SIGABRT totem plays ~1 second of video and then crashes. This appears to happen with all video formats. This appears to be an issue in multithreading support in the nouveau driver, which is fixed upstream. The fix is large and may not be suitable for backporting, but would be available in a mesa-22.3 update. Proposed blockers ----------------- 1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2128662 — ASSIGNED Abrt does not report a segfault which is reported in journalctl. In some circumstances (currently unclear), abrt does not report segfaults. Restarting abrt-journal-core (including via reboot) causes abrt to work correctly again. 2. nautilus — https://bugzilla.redhat.com/show_bug.cgi?id=2127618 — NEW Nautilus thumbnailing doesn't work on hidpi screens No thumbnails are generated in the file manager on hidpi screens. Other functionality works. Reported upstream as https://gitlab.gnome.org/GNOME/nautilus/-/issues/2487 -- 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, report it: https://pagure.io/fedora-infrastructure/new_issue