Hi folks, We are fast approaching the end of the F40 Final Freeze and the F40 Go/No-Go meetings will start real soon. There are a number of bugs, both accepted and proposed, filed against F40 Final, so your help in troubleshooting and potentially finding a fix for those would be greatly appreciated. In particular, there is a blocker bug outstanding from the F39 release, and some additional feedback on the ideas to resolve the issue is needed. Please visit the blocker bugs app for more details https://qa.fedoraproject.org/blockerbugs/milestone/40/final/buglist Summary 2024-04-05 == Proposed Blocker == 1. khelpcenter - bluetooth.service becomes unresponsive when disabling the interface while a device is still connected since bluez 5.73 - ON_QA ACTION: QA to verify fix https://bodhi.fedoraproject.org/updates/FEDORA-2024-8d9c6f3fae 2. gtk4 - snapshot crashes on launch or after taking a picture, console error "thread 'main' has overflowed its stack", backtrace is 4000+ frames and inc "Cannot access memory at address 0xffffffffffffffff" - NEW ACTION: Maintainer to diagnose issue 3. plasma-drkonqi - Logoout after less than 60 seconds is broken on Plasma 6.0.3 - POST ACTION: QA to verify https://bodhi.fedoraproject.org/updates/FEDORA-2024-668daf04ea 4. python-blivet - Firmware RAID set not usable in anaconda when booting native UEFI: "ERROR:blivet:failed to determine name for the md array a7ff7f19-f142-4329-6b52-1dbafa835906" - ASSIGNED ACTION: More testing with other hardware using firmware RAID in UEFI mode needed and appreciated 5. uboot-tools - U-Boot doesn't find and load the fedoa provided DTBS from /boot/dtb - MODIFIED ACTION: QA to verify https://bodhi.fedoraproject.org/updates/FEDORA-2024-1d0b793bc1 == Accepted Blockers == 1. khelpcenter - The KDE help center does not show the documentation for KDE applications - NEW ACTION: Upstream to diagnose issue 2. loupe - Loupe cannot open JPEG images - VERIFIED ACTION: None 3. snapshot - Snapshot displays only on solid pink - VERIFIED ACTION: None 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: HELP WANTED to figure out a fix please = Bug by Bug Detail = == Proposed Blockers == 1. khelpcenter - bluetooth.service becomes unresponsive when disabling the interface while a device is still connected since bluez 5.73 - https://bugzilla.redhat.com/show_bug.cgi?id=2269516 - ON_QA There were issues enabling and disabling the bluetooth interface after an update to bluez in F39. It also affected connecting and disconnecting bluetooth devices. An upstream patch was filed with bluez that reverts a commit which appears to resolve the issue https://lore.kernel.org/linux-bluetooth/20240403205252.71978-1-dimitris.on.linux@xxxxxxxxx/T/#t and a build with this patch, bluez 5.73-3 has been pushed to the Fedora 40 testing repo for verification https://bodhi.fedoraproject.org/updates/FEDORA-2024-8d9c6f3fae 2. gtk4 - snapshot crashes on launch or after taking a picture, console error "thread 'main' has overflowed its stack", backtrace is 4000+ frames and inc "Cannot access memory at address 0xffffffffffffffff" - https://bugzilla.redhat.com/show_bug.cgi?id=2273497 - NEW Snapshot is crashing in launch or after taking the first picture when using the Logitech C920 camera. It also shows a 'no camera found' message when launching from the gnome-shell launcher. This issue does not seem to affect an integrated HD Webcam on an acer notebook, so more testing on other types of hardware would be of great benefit to identify if this bug is only related to the C920 camera, or if there are other affected machines. 3. plasma-drkonqi - Logout after less than 60 seconds is broken in Plasma 6.0.3 - https://bugzilla.redhat.com/show_bug.cgi?id=2272712 - POST When wanting to log out of KDE through the graphical interface, the system does not log the user out at all, however the issue is only active within the first 60 seconds of logging in. An update that backports and upstream fix which caused the issue has been submitted to the testing repository for F40 https://bodhi.fedoraproject.org/updates/FEDORA-2024-668daf04ea 4. python-blivet - Firmware RAID set not usable in anaconda when booting native UEFI: "ERROR:blivet:failed to determine name for the md array a7ff7f19-f142-4329-6b52-1dbafa835906" - https://bugzilla.redhat.com/show_bug.cgi?id=2270209 -ASSIGNED Anaconda (via blivet) does not detect the firmware RAID to set as a viable target for install when booting from BIOS. This issue is found in F39 as well as F40 beta. More testing of the F40 beta on other hardware with firmware RAID on UEFI would be most appreciated as it is not clear whether this is hardware specific or not as the behaviour is seen on an Asus H97M-E motherboard, but not on a Gigabyte GA-Z170M-D3H. 5. uboot-tools - U-Boot doesn't find and load the Fedora provided DTBs from /boot/dtb - https://bugzilla.redhat.com/show_bug.cgi?id=2247873 - MODIFIED Fedora Server images do not boot on the Jetson Nano. Non-Server images are not affected as they can use the kernel DTBs, and they boot OK. There is a similar root cause in https://bugzilla.redhat.com/show_bug.cgi?id=2246428 for this bug also. A fix was submitted to the Fedora 40 testing repository, but never made it into 'stable' before F40 beta release. A new update has been submitted to the F40 testing repository for testing https://bodhi.fedoraproject.org/updates/FEDORA-2024-1d0b793bc1 == Accepted Blockers == 1. khelpcenter - The KDE help center does not show the documentation for KDE applications - https://bugzilla.redhat.com/show_bug.cgi?id=2271837 - NEW The KDE Help centre does not show, or is missing, documentation for the KDE applications. A workaround can be found by doing a search for the documentation through the help centre, but there are two links, of which only one currently works. An upstream bug has been filed https://bugs.kde.org/show_bug.cgi?id=484176 and the upstream maintainers are aware of the issue and are working on a fix. 2. loupe - Loupe cannot open JPEG images https://bugzilla.redhat.com/show_bug.cgi?id=2272149 - VERIFIED The RPM version of Loupe 46 has had some issues opening all file formats images with Fedora Workstation 40. The Flatpak version was unaffected, as were older versions of Fedora (39) and Loupe (45.3). A dependency on glycin-loaders 1.0 seems to have been the issue, as most machines were running on an older version of this. An update with the most recent version of glycin-loaders has been submitted to the F40 testing repository and which fixes this issue and has been tested and a confirmed fix has been found https://bodhi.fedoraproject.org/updates/FEDORA-2024-2d6f70c275 3. snapshot - Snapshot displays only on solid pink - https://bugzilla.redhat.com/show_bug.cgi?id=2269286 - VERIFIED When the webcam is enabled in Snapshot 45.2, the live display screen is pink. Recordings and snapshots work fine. When building Snapshot 46, there were several build dependencies expecting the older version. These dependancies have now been updated and a fix https://bodhi.fedoraproject.org/updates/FEDORA-2024-a18f8e83b4 has been submitted to the Fedora 40 testing repository which appears to have resolved the 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 this bug and solutionize a fix. Kind regards, Aoife -- 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
