*Correction - the Fedora QA meeting is (likely) cancelled, but the Blocker Review meeting[1] will go ahead as scheduled this afternoon. I had my wires/meetings crossed. If you can attend this meeting today, your help reviewing, triaging and resolving the proposed blockers ahead of the Go/No-Go meeting[2] on Thursday would be very appreciated.
Kind regards, Aoife [1] https://calendar.fedoraproject.org/QA/#m11115 [2] https://calendar.fedoraproject.org/meeting/11131/ On Sun, Oct 12, 2025 at 5:41 PM Aoife Moloney <[email protected]> wrote: > Hi folks, > > > With the F43 Final Go/No-Go meeting happening on Thursday[1], it would > be great if you could spare some time to review the proposed blockers > that are filed in the blocker bugs app[2]. Right now we are targeting > the early release deadline of Tuesday, Oct 21 2025[3]. As there may > not be a blocker bug meeting tomorrow[4] (unless someone would like to > run it), it would be really beneficial to arrive in the Go/No-Go > meeting with the bug list reviewed, voted on and maybe even have some > fixes for! :crosses fingers: > This is also true if the blocker review meeting does go ahead tomorrow too > :) > > So if you can, please take a look at the proposed blockers, and as > always please refer to the blocker bug app and each bugzilla for more > detailed information on the bug. > > > Action summary > ==================== > > Accepted blockers (6) > ----------------- > > 1. blivet-gui — Cannot add encrypted MD RAID btrfs device in blivet-gui — > ON_QA > ACTION: QA to verify fix > https://bugzilla.redhat.com/show_bug.cgi?id=2401870 > > 2. dracut — default hostonly-mode "sloppy" results in significant > increase in initramfs size — MODIFIED > ACTION: Upstream to review and submit patch to F43 > > 3. fedora repos — fedora-repos: disable updates-testing repo for final > F43 release — ON_QA > ACTION: QA to verify PR > https://src.fedoraproject.org/rpms/fedora-repos/pull-request/161 > > 4. gtk3 — Drop-down menus not working over RDP in Anaconda — VERIFIED > ACTION: No action required, fix has been provided > https://bodhi.fedoraproject.org/updates/FEDORA-2025-d6e439498a > > 5. kiwi — Radxa Rock Pi 4 and Pine64 RockPro64 boards fail to boot > with Kiwi-produced images, probably all RockChip models — ON_QA > ACTION: QA to verify fix > > 6. libdnf — libdnf context is not reading and enforcing protected > packages, causing PackageKit to not honor protected packages settings > — VERIFIED > ACTION: No action required, fix submitted > https://bodhi.fedoraproject.org/updates/FEDORA-2025-005db2cfbf > > > Proposed blockers (11) > ----------------- > 1. anaconda — WebUI: > org.fedoraproject.Anaconda.KeyboardConfigurationError: The live system > has layout 'typing-booster' which can't be used for installation. — > NEW > ACTION: Upstream to diagnose issue > > 2. anaconda — rescue mode fails to mount /boot and /boot/efi — NEW > ACTION: Upstream to diagnose issue > > 3. anaconda-webui — anaconda WebUI crashes with "Password is too weak" > error — POST > ACTION: QA to verify fixes > > 4. anaconda-webui — anaconda-webui on KDE produces unusable > configuration when selecting Russian (etc.) keyboard layout — POST > ACTION: QA to verify fixes > > 5. anaconda-webui — The partition resize slider is broken for certain > languages — VERIFIED > ACTION: Upstream to diagnose issue > > 6. edk2 — fedora ISOs will not boot in qemu-kvm using UEFI — NEW > ACTION: Fix available > https://bodhi.fedoraproject.org/updates/FEDORA-2025-addc7b1924 > > 7. gnome-initial-setup — Input source menu not available for IME after > gnome-initial-setup — POST > ACTION: No action required > > 8. gnome-shell — System freeze when touching QuickMenu sliders > (volume/brightness) with touchscreen — NEW > ACTION: Upstream to diagnose issue > > 9. linux-firmware — Regression in mediatek mt7922 wifi — ASSIGNED > ACTION: Upstream to provide fix if possible > > 10. systemd — Version upgrade from Fedora 41 to 42 disables > postfix.service — NEW > ACTION: Upstream to provide more information on cause and possible > workaround/fix > > 11. uboot-tools — uboot-tools-2025.10 is available — NEW > ACTION: Please review and determine if this is a valid blocker bug by > voting in the app > > > Bug-by-bug detail > ============= > > Accepted blockers > ----------------- > > 1. blivet-gui — https://bugzilla.redhat.com/show_bug.cgi?id=2401870 — > ON_QA > Cannot add encrypted MD RAID btrfs device in blivet-gui > > The installer's graphical interface crashes during complex disk setup > involving encryption and specialized file systems. A fix has already > been submitted that resolves this issue > https://github.com/storaged-project/blivet-gui/pull/520 > > > 2. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2394213 — MODIFIED > default hostonly-mode "sloppy" results in significant increase in > initramfs size > > Over time the size of the Linux kernel and its associated initial > ramdisk (initramfs) images has grown very large, very quickly, making > the default or traditional size for the /boot partition too small. > Some areas to shave off additional bloat have been identified, and a > PR for a partial revert for the hostonly sloppy mode has been > submitted upstream https://github.com/dracut-ng/dracut-ng/pull/1673/. > This fix has landed for Rawhide, but not for F43 yet > > https://src.fedoraproject.org/rpms/dracut/c/6908946c3c0751e9ca807bd230ba62e8a42d38f8?branch=rawhide > > > 3. fedora-repos — https://bugzilla.redhat.com/show_bug.cgi?id=2394213 — > ON_QA > fedora-repos: disable updates-testing repo for final F43 release > > A PR has been submitted to disable the updates-testing repo ahead of > F43 final https://src.fedoraproject.org/rpms/fedora-repos/pull-request/161 > > > 4. gtk3 — https://bugzilla.redhat.com/show_bug.cgi?id=2397086 — NEW > Drop-down menus not working over RDP in Anaconda > > When gtk3 drop-downs are used over RDP, on the first attempt, the > dropdown closes immediately. On further attempts, they work OK. An > issue has been filed upstream > https://gitlab.gnome.org/GNOME/gtk/-/issues/7811 and a fix has been > submitted https://bodhi.fedoraproject.org/updates/FEDORA-2025-d6e439498a > which resolves the issue somewhat > > > 5. kiwi — https://bugzilla.redhat.com/show_bug.cgi?id=2396309 — ON_QA > Radxa Rock Pi 4 and Pine64 RockPro64 boards fail to boot with > Kiwi-produced images, probably all RockChip models > > Images built for RockChip-based SBCs by Kiwi appear to have been > failing to boot because of how the partitions and firmware are laid > out. A PR has been submitted to fedora-kiwi-descriptions > https://pagure.io/fedora-kiwi-descriptions/pull-request/221 and is > also submitted for F43 > > https://pagure.io/fedora-kiwi-descriptions/c/176a9d56aa6b00ec66ad1c4680ae110c07c00b88?branch=f43 > , > so following a compose this should resolve the issue. Testing of the > fix once available will be required to verify it works. > > > 6. libdnf — https://bugzilla.redhat.com/show_bug.cgi?id=2400488 — VERIFIED > libdnf context is not reading and enforcing protected packages, > causing PackageKit to not honor protected packages settings > > Removing the cantarell-VF font from Gnome Software causes the Gnome > desktop environment to break and gives users a shell screen rather > than the graphical login. The suspected cause is a regression in > libdnf in PackageKit, which has recently been upgraded, but this > upgrade caused an issue with PackageKit and ultimately seems to be > causing this end-user issue. A fix has been provided which resolves > this issue https://bodhi.fedoraproject.org/updates/FEDORA-2025-005db2cfbf > > > > > Proposed blockers > ----------------- > 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2402675 — NEW > WebUI: org.fedoraproject.Anaconda.KeyboardConfigurationError: The live > system has a layout 'typing-booster' which can't be used for > installation. > > The installer seems to trigger a KeyboardConfigurationError because it > is unable to handle or use the special keyboard layout > ('typing-booster') that was set in the live system. It also happens > when the installer is running and you click "Change system keyboard > layout", and then add an input method too. > > > 2. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2402976 — NEW > rescue mode fails to mount /boot and /boot/efi > > When a user boots into the installer, selects Troubleshooting, and > enters Rescue Mode, the system only successfully mounts the main root > (/) partition of the installed operating system to /mnt/sysimage. > There may be an issue with blivet at the core, but further > investigation is needed to confirm the cause of this bug. > > > 3. anaconda-webui — https://bugzilla.redhat.com/show_bug.cgi?id=2389356 — > POST > anaconda WebUI crashes with "Password is too weak" error > > The installer crashes immediately when a user types a password for > disk encryption (LUKS) that is considered "too weak." This seems to > have been triggered when the system's password strength checker > (pwscore) returns a value of 0 (which means the password is the > weakest possible or fails minimum rules). It immediately crashes as it > identifies this as a 'critical error', rather than displaying a > 'password too weak' message. A PR has been submitted upstream which > fixes this issue > https://github.com/cockpit-project/cockpit/pull/22494, and includes a > webui fix for cockpit too > https://github.com/rhinstaller/anaconda-webui/pull/1036 > > > 4. anaconda-webui — https://bugzilla.redhat.com/show_bug.cgi?id=2402430 — > POST > anaconda-webui on KDE produces unusable configuration when selecting > Russian (etc.) keyboard layout > > For languages like Russian, the standard setup requires two keyboard > layouts to be configured simultaneously: one for the native (Cyrillic) > characters and the standard US-English layout for ASCII characters. > When a user selects a language like Russian in the KDE-based WebUI, it > only allows them to select a single layout, which makes it impossible > for the user to type all ASCII characters and restricts users from > having disk encryption passphrases and creating username and passwords > with ascii characters. A suggested fix, albeit a minimal one, has been > sent https://github.com/rhinstaller/anaconda-webui/pull/1037 which > would hide keyboard layout options that cant input ASCII, thus > removing the option, but this also relies on > https://github.com/rhinstaller/anaconda/pull/6692 being reviewed, > preferably by someone who has experience with javascript. Any help > reviewing these PRs would be appreciated. > > > 5. anaconda-webui — https://bugzilla.redhat.com/show_bug.cgi?id=2403028 — > NEW > The partition resize slider is broken for certain languages > > The partition resizing tool in the installer is broken for users who > select a language that uses a comma (,) as the decimal separator > (instead of a period (.), as used in English). If a user tries to > install Fedora using another language like French, German and Spanish, > the slider doesn't show the size numbers correctly. Also if the user > interacts with the accompanying text field, the slider breaks > completely and becomes unusable. If anyone could take some time to > take a look at this bug and identify its cause (suspected decimal > comma issue), that would be really helpful. > > > 6. edk2 — https://bugzilla.redhat.com/show_bug.cgi?id=2401623 — NEW > fedora ISOs will not boot in qemu-kvm using UEFI > Fedora 43 ISO fails to boot the kernel on suspected older Intel NUC > hardware when using a VM for this. This is not true for other hardware > such as Lenovo Thinkpads, as the same F43 ISO boots successfully here. > A fix has been submitted which seems to resolve the issue > https://bodhi.fedoraproject.org/updates/FEDORA-2025-addc7b1924 > > > 7. gnome-initial-setup — > https://bugzilla.redhat.com/show_bug.cgi?id=2402147 — POST > Input source menu not available for IME after gnome-initial-setup > > The specialized text input tools needed for CJK languages appear to be > missing after install. Users must manually go into the GNOME settings > and add the input source again. This functionality was available in > F42. An issue was filed upstream > https://gitlab.gnome.org/GNOME/gnome-initial-setup/-/issues/239 and a > fix has been found by the maintainers, which is to not use the > /var/lib/gdm persistent settings location for gnome-initial-setup. > This will match the behavior of previous versions of GNOME. > > > 8. gnome-shell — https://bugzilla.redhat.com/show_bug.cgi?id=2399599 — NEW > System freeze when touching QuickMenu sliders (volume/brightness) with > touchscreen > > On a Wayland session, using the touchscreen to interact with GNOME > Shell’s QuickMenu sliders (volume or brightness) causes the entire > system to become unresponsive. The mouse pointer can still move, but > clicks, keyboard input, and touch input do not work. Users need to > either shut down the system or close the lid to suspend to get their > sessions working again. > > > 9. linux-firmware — > https://bugzilla.redhat.com/show_bug.cgi?id=2401216 — ASSIGNED > Regression in mediatek mt7922 wifi > A recent update to the Linux firmware package in Fedora seems to have > caused the MT7922 Wi-Fi adapter on several common laptops to fail, > such as the ASUS Zenbook UM3406KA, ASUS Vivobook S14, and Lenovo > ThinkPad L13 Yoga Gen 4. The package version causing this failure > seems to be 20250917-2.fc42. A workaround currently in use is to > downgrade both the linux-firmware and mt7xxx-firmware packages to an > older version, such as linux-firmware-20250808-1 and 20250311-1.fc42 > > > 10. systemd — https://bugzilla.redhat.com/show_bug.cgi?id=2363937 — NEW > Version upgrade from Fedora 41 to 42 disables postfix.service > > Some users who are upgrading from F41 -> F42, and some F42 - F43 Beta > upgrades too, are reporting losing the postfix.service and nftables. > > > 11. uboot-tools — https://bugzilla.redhat.com/show_bug.cgi?id=2401964 — > ASSIGNED > uboot-tools-2025.10 is available > > The upstream release monitoring system has reported the availability > of a new updated package set. More investigation is needed to figure > out what the cause of this bug is, as an upgrade from > postfix-2:3.9.0-8.fc41.x86_64 → postfix-2:3.9.1-3.fc42.x86_64, and > then to 2:3.9.1-5.fc42 was successful for one reporter. More > information is definitely needed, so help would be appreciated. > > > > > > > [1] https://calendar.fedoraproject.org/meeting/11131/ > [2] https://qa.fedoraproject.org/blockerbugs/milestone/43/final/buglist > [3] > https://lists.fedoraproject.org/archives/list/[email protected]/thread/2LKCLTJCNIFK53TVR3VYLD6XX3LO34KT/ > [4] https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html > > > -- > Aoife Moloney > > Fedora Operations Architect > > Fedora Project > > Matrix: @amoloney:fedora.im > > IRC: amoloney > -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney
-- _______________________________________________ devel-announce mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
