Hi all, We are only a few weeks away from the F43 Final Go/No-Go meeting[1] and there are a number of proposed and accepted blockers in the blocker bug app[2]. Your help diagnosing, fixing and voting on blockers would be greatly appreciated to get this list slimmed down. Below is a summarised list of the blockers, and there is also a blocker bug meeting on Monday, 4 Oct[3] run by QA. If you can, please consider voting on proposed blocker bugs ahead of this meeting, and also attend to help review and address F43 Final blockers.
As mentioned, this is a brief summary of each blocker. Please visit the blocker bug app and each bug directly for more detailed information on each bug. Action summary ==================== Accepted blockers ----------------- 1. abrt — All crashes are ignored by ABRT because of "Package isn't signed with proper key" — ON_QA ACTION: QA to verify fix https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed458ffe66 2. distribution — Fedora 43: Workstation live x86_64 image exceeds maximum size — ASSIGNED ACTION: Maintainers to review options for size reduction 3. distribution — Fedora 43: Server boot aarch64 image exceeds maximum size — ASSIGNED ACTION: Maintainer to review options for size reduction 4. dracut — default hostonly-mode "sloppy" results in significant increase in initramfs size — MODIFIED ACTION: Upstream to help find fix 5. gnome-desktop-remote — Drop-down menus not working over RDP in Anaconda — NEW ACTION: Maintainers to diagnose issue 6. 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 7. selinux-policy — SELinux is preventing systemd from 'open' accesses on the file /tmp/webui-cockpit-ws.env. — POST ACTION: No action required Proposed blockers ----------------- 1. anaconda — WebUI: Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Bt%2C%20v%7D for the full message or use the non-minified dev environment for full errors and additional helpful warning — NEW ACTION: Maintainers to diagnose issue and more tests to reproduce the bug would be helpful 2. libdnf — libdnf context is not reading and enforcing protected packages, causing PackageKit to not honor protected packages settings — NEW ACTION: Upstream to diagnose issue Bug-by-bug detail ============= Accepted blockers ----------------- 1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2396899 — ON_QA All crashes are ignored by ABRT because of "Package isn't signed with proper key" After a crash occurs, ABRT is not saving or reporting its findings and instead disregards them. It also appears to be rejecting 'proper' signed packages. Changes made to the rpm https://github.com/rpm-software-management/rpm/issues/2403 is suspected to have been the cause of the bug, and a fix has since been submitted for testing https://bodhi.fedoraproject.org/updates/FEDORA-2025-ed458ffe66 2. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2360056 — ASSIGNED Fedora 43: Workstation live x86_64 image exceeds maximum size The image is over the maximum size and is failing. QA have investigated some possible causes for increase and there are a few options that could reduce the size of the image to potentially bring it down to the recommended max size. These include a surprising increase of the rpm database to 95M, a potential duplication in the initramfs for firmware, two versions of libicudata (77 and 76) and other findings of increases that could be trimmed through various means. A review of the findings would be helpful to decide on which or all are necessary to take, mainly from Workstation WG, but others are also welcome to help review and fix. 3. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2387466 — ASSIGNED Fedora 43: Server boot aarch64 image exceeds maximum size The server aarch64 image is still oversize. There have been a number of additions such as an extra 65M of NVIDIA firmware and an additional 10MB of Qualcom firmware. There is a suggestion in this report to drop tivervnc and a PR has been sent to lorax https://github.com/weldr/lorax/pull/1495. Other suggestions to reduce the image size to bring it under the rmax size would be very appreciated. 4. dracut — https://bugzilla.redhat.com/show_bug.cgi?id=2394213 — MODIFIED default hostonly-mode "sloppy" results in significant increase in initramfs size After upgrading to dracut-107 (vs older dracut-105, etc.), users are seeing a large jump in the size of the generated initramfs images. The increased size is troublesome because the /boot partition (where these images go) is limited in space, and some users with smaller /boot partitions might run out of space and be unable to install or upgrade kernels or systems. There are a few suggestions to try to resolve this issue, including /boot to be expanded to 2GB, which should help with new installs, but not those using smaller machines, and a PR to partially revert hostonly sloppy mode might help resolve this https://github.com/dracut-ng/dracut-ng/pull/1673. Help with finding an appropriate solution would be very appreciated. 5. gnome-remote-desktop — https://bugzilla.redhat.com/show_bug.cgi?id=2397086 — NEW Drop-down menus not working over RDP in Anaconda When using the graphical installation in Gnome over RDP, drop-down menus in the installer UI (Anaconda) don’t respond to mouse clicks. You can still use the keyboard (tab, arrow keys) to move focus and pick options—so the menu entries are present, just not clickable by mouse. This also affects gtk3 applications too. This bug also seems reproducible while not using RDP install too, which might indicate a wider problem. 6. 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. 7. selinux-policy — https://bugzilla.redhat.com/show_bug.cgi?id=2394561 — POST SELinux is preventing systemd from 'open' accesses on the file /tmp/webui-cockpit-ws.env. When launching the installer (Anaconda) via the KDE Live image, a SELinux denial warning appears. A PR has been submitted upstream that should resolve this issue https://github.com/fedora-selinux/selinux-policy/pull/2882 Proposed blockers ----------------- 1. anaconda — https://bugzilla.redhat.com/show_bug.cgi?id=2388216 — NEW WebUI: Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=object%20with%20keys%20%7Bt%2C%20v%7D for the full message or use the non-minified dev environment for full errors and additional helpful warning An error message of "Minified React error #31" happens on install with the WebUI for anaconda. The install proceeds when root is enabled for some users, but not others. Not setting the timezone or a non-default NTP server also seems to allow installation to proceed. The cause of the error seems inconsistent so more investigation is needed for this bug. Help would be appreciated to do some more testing on the installation to see if there is a more consistent pattern for the error message to be triggered. 2. libdnf — https://bugzilla.redhat.com/show_bug.cgi?id=2400488 — NEW 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. Upstream help is needed to provide a fix. [1] https://calendar.fedoraproject.org/meeting/11131/ [2] https://qa.fedoraproject.org/blockerbugs/milestone/43/final/buglist [3] https://calendar.fedoraproject.org/QA/2025/10/6/#m11115 -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ 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
