We are just under one week away from the Fedora Linux 41 Final Go/No-Go meeting, and we're hoping to release on the early target date[1] of 22nd October, but in order to do that, we need your help with our blocker bugs[2]. Below is a short summary of the current F41 Final blocker bugs, and as always your help testing and helping come up with a fix is hugely appreciated. For more detailed information on each bug, please visit the bugzilla trackers and the blocker bugs app to vote on and/or propose any other bugs you may have found for F41. Action Summary 2024-10-12 == Proposed Blocker == 1. 389-ds-base - VLV errors in Fedora 40 with RSNv3 and pruning enabled - POST ACTION: QA to confirm fix is available 2. anaconda - Firmware RAID installation is impossible with automatic partitioning -ASSIGNED ACTION: Maintainer to diagnose issue 3. dbus-broker - dbus activated apps including the welcome dialog suffer 30-45 sec delay and/or crash on Workstation Live image randomly - NEW ACTION: Maintainer to diagnose issue == Accepted Blockers == 1. anaconda - pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 - VERIFIED ACTION: N/A 2. bcm283x-firmware - gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 - ON_QA ACTION: QA to verify fix https://bodhi.fedoraproject.org/updates/FEDORA-2024-872cfc5769 3. distribution - Fedora 41 aarch64 KDE disk image is oversize - POST ACTION: N/A = Bug by Bug Detail = == Proposed Blockers == 1. - 389-ds-base - VLV errors in Fedora 40 with RSNv3 and pruning enabled https://bugzilla.redhat.com/show_bug.cgi?id=2317851 - POST A regression in F40 affecting VLV caused errors when 398-ds-base changed to a new database(LMDB) and resulted in the cache being out of sync with the database. This is a component of Dogtag PKI which FreeIPA uses to manage certificate checks, and when trying to search using the VLV feature, this would fail, or pull incorrect data. Fixes are available upstream that resolve the misalignment between cache and database and have been initially tested by FreeIPA as valid. 2. anaconda - Firmware RAID installation is impossible with automatic partitioning https://bugzilla.redhat.com/show_bug.cgi?id=2317287 - ASSIGNED Automatic partitioning should work normally on FW RAID systems and when installing Fedora 41, 'no usable configuration' displays. 3. dbus-broker - dbus activated apps including the welcome dialog suffer 30-45 sec delay and/or crash on Workstation Live image randomly https://bugzilla.redhat.com/show_bug.cgi?id=2316066 - NEW Apps that are dbus-activated are experiencing a delayed start of approx 30 - 45 seconds at boot time. The behaviour exists in the Workstation live image and when booting from a VM. A low number of CPUs seems to be a likely factor, however using Gnome Boxes to create the VM and boot F41 workstation image seems to resolve the delay. More troubleshooting is required to find the root cause and solutionize a fix or workaround. == Accepted Blockers == 1. anaconda - pyanaconda.modules.common.errors.storage.UnknownDeviceError: Volume0_0 https://bugzilla.redhat.com/show_bug.cgi?id=2311936 - VERIFIED Originally after installing F41 on a firmware RAID and trying to reclaim the space it took, Anaconda crashed. This was resolved by a PR upstream https://github.com/rhinstaller/anaconda/pull/5875 and the behaviour no longer happens. 2. bcm283x-firmware - gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 - https://bugzilla.redhat.com/show_bug.cgi?id=2282171 - ON_QA An issue with the mesa driver running out of memory as soon as gtk reallocates the swapchain causes the apps to crash. However the default cma value can be increased to 512M by adding cma=512M, when using workstation on RPI4+. 256Mb is not enough for desktop usage with 4k video decode, and this changed in the latest update for Pi4. A PR has been merged downstream to increase the CMA to 512MB by default. A fix for F41 has been submitted to bodhi and is awaiting verification that this resolves the issue. 3. distribution - Fedora 41 aarch64 KDE disk image is oversize - https://bugzilla.redhat.com/show_bug.cgi?id=2283978 - POST The KDE aarch64 disc image exceeds the 16GB limit. A PR was sent that would adjust the 'free space' estimate that would adjust for compression on btrfs which resolved the issue and the download is now successful. [1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html [2] https://qa.fedoraproject.org/blockerbugs/milestone/41/final/buglist -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ 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
