Hello folks, Fedora Linux 41 Beta is just around the corner[1] and we're hoping to release on the early target date of 17th September, but in order to do that, we need to get our blocker bugs in good order. Below is a short summary of the current F41 beta blocker bugs on file, 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[2] to vote on and/or propose any other bugs you may have found for F41. Action Summary 2024-09-05 == Proposed Blocker == 1. dnf5 - dnf plugins not handled in the upgrade process - ASSIGNED ACTION: Maintainers to diagnose issue == Accepted Blockers == 1. bcm283x-firmware - gsk: vulkan renderer causes gtk4 apps to crash on resize operations on Raspberry Pi 4 and 400 - ASSIGNED ACTION: Maintainers to diagnose issue 2. distribution - Fedora 41: Workstation live x86_64 image exceeds maximum size - POST ACTION: N/A 3. kernel - Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but can't be woken up - ASSIGNED ACTION: QA to verify https://bodhi.fedoraproject.org/updates/FEDORA-2024-dbf55dbc52 4. mesa - Raspberry Pi 4: KDE initial setup is broken without nomodeset, KDE desktop wont load with nonodeset - MODIFIED ACTION: Maintainers to diagnose issue Accepted Previous Release Blocker 1. distribution - dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key - NEW ACTION: Still waiting for a Hero to emerge to figure out a fix please = Bug by Bug Detail = == Proposed Blockers == 1. dnf5 - dnf plugins not handled in the ugprade process - https://bugzilla.redhat.com/show_bug.cgi?id=2309697 - ASSIGNED The dnf5-plugins package is not available when trying to upgrade from dnf4 -> dnf5. The current way of upgrading is to use the dnf4-plugins package along with the python3-dnf package but this is not an ideal default user experience. The dnf5 change owners are looking into a better way for users to manage these dependencies. == Accepted Blockers == 1. gcc - 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 - ASSIGNED It is likely that the mesa driver is running out of memory as soon as gtk reallocates the swapchain, 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 https://github.com/raspberrypi/linux/pull/5376. More testing is required to verify that a fix is in place. 2. distribution - Fedora 41: Workstation live x86_64 image exceeds maximum size - https://bugzilla.redhat.com/show_bug.cgi?id=2271837 - POST The current limit for release blocking images has been bumped to 2.5 GB https://pagure.io/fedora-pgm/pgm_docs/pull-request/75 and python3-botocore has been excluded https://pagure.io/fedora-kickstarts/pull-request/1051# to fix this issue. 3. kernel - Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but cant be woken up - https://bugzilla.redhat.com/show_bug.cgi?id=2283978 - ASSIGNED RPi4 4 does not wake up from 'suspend' mode and needs to be turned off and back on again to function. The option to disable suspend is being discussed, but an update that may resolve the issue slightly as it allows the kernel to interface directly with the firmware for suspend, has been submitted for testing https://bodhi.fedoraproject.org/updates/FEDORA-2024-dbf55dbc52 4. mesa - Raspberry Pi 4: KDE initial setup is broken without nomodeset, KDE desktop wont load with nomodeset - https://bugzilla.redhat.com/show_bug.cgi?id=2270430 - MODIFIED Initial setup with KDE on RPi4 needs to be rebooted before finishing setup, and then the graphical desktop wont load with nomodeset in place. This needs to be rebooted again, this time without nomodeset. An update has been submitted to F41 that v3d always use LINEAR which should be backported to mesa stable versions also, including Fedora mesa package https://bodhi.fedoraproject.org/updates/FEDORA-2024-dbf55dbc52, but this update unfortunately doesn't solve the full issue. == Accepted Previous Release Blocker == 1. distribution - dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key - https://bugzilla.redhat.com/show_bug.cgi?id=2242759 - NEW beta dnf system-upgrade reboot fails on Raspberry Pi 4 (8 gb). Using dnf system-upgrade log --number=-1, an entry like "Signature 10d5 created at Wed Sep 27 16:33:34 2023 invalid: signature is not alive" is generated for each rpm in the upgrade list. Raspberry Pi 4 does not have a hardware real time clock so when the Pi is booting Fedora system time is at some (arbitrary?) date and time. During a normal boot chronyd is executed and will set the clock: "chronyd[571]: System clock wrong by 944623.935135 seconds". If the gpg key used by DNF during the system-upgrade has a valid period more recent than the boot time, system-upgrade will fail. There are various possible workarounds, but none ideal for users to have to implement, so a fix is still required for this bug to be resolved. Anyone with Python experience would be most welcome to give feedback on some of the ideas to fix that have been proposed or come up with a fix. [1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html [2] https://qa.fedoraproject.org/blockerbugs/milestone/41/beta/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
