The Fedora Linux 41 Final Go/No-Go meeting is scheduled for this Thursday, 24th October, and we're hoping to release on the early target date[1] of 29th October. 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. If you can spare some time to test the proposed blockers and vote as to whether they should be a blocker or not, that would be great. Even better is if you find a fix that would resolve the blocker and propose it!
The F41 blocker review meeting[3] will also take place later today, and for more detailed information on each bug, please visit the bugzilla trackers and the blocker bugs app.
Action Summary 2024-10-21
== Proposed Blocker == 1. cups - dbus activated apps including the welcome dialog suffer 30-45 sec delay and/or crash on Workstation Live image randomly - POST ACTION: N/A
2. kernel - Bluetooth devices are not getting paired - ON_QA ACTION: QA to verify fix https://bodhi.fedoraproject.org/updates/FEDORA-2024-b1092ef4d5
3. konsole - Konsole command output isn't read by the screen reader when activated - NEW ACTION: Upstream to diagnose issue
4. plasma-welcome - Plasma Welcome isn't read by the screen reader when activated - NEW ACTION: Upstream to diagnose issue
5. qt6-qtbase - Qt does not watch for screen reader being enabled properly, rendering Plasma invisible to Orca - POST ACTION: QA to verify fix https://codereview.qt-project.org/c/qt/qtbase/+/598549
6. qt6-qywayland - KDE apps like KInfoCenter and System Settings sometimes don't start - NEW ACTION: Maintainer to diagnose issue and test potential fix https://codereview.qt-project.org/c/qt/qtwayland/+/574934
== Accepted Blockers == 1. distribution - osbuild tasks are consistently failing and breaking composes, but building ARM minimal with ImageFactory instead would compromise device support - ON_QA ACTION: QA to verify fix
= Bug by Bug Detail =
== Proposed Blockers == 1. cups - 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 - POST
There has been a delay of up to 45 seconds on booting to display the Welcome message. After extensive testing, the issue was narrowed down to be a time jump issue with CUPS and a PR has been submitted with a potential fix https://src.fedoraproject.org/rpms/cups/pull-request/34
2. kernel - Bluetooth devices are not getting paired https://bugzilla.redhat.com/show_bug.cgi?id=2319597 - ON_QA
Pairing bluetooth devices with kernel 6.11 was not working for some users. A fix has been applied https://bodhi.fedoraproject.org/updates/FEDORA-2024-b1092ef4d5
3. konsole - Konsole command output isn't read by the screen reader when activated https://bugzilla.redhat.com/show_bug.cgi?id=2320046 - NEW
Output from programs are not being read from Orca, the screen reader. Double-pressing the '+' button on a number pad resolves the issue but this is not suitable for all users and it's not clear if this is an actual workaround or not. Anyone with experience with Orca would be welcome to take a look, and would be very appreciated.
4. plasma-welcome - plasma-welcome - Plasma Welcome isn't read by the screen reader when activated https://bugzilla.redhat.com/show_bug.cgi?id=2320044 - NEW
The welcome window on Plasma is not being read by Orca on first activation, and only works if forced - by double-pressing + button. This should not be the intended behaviour for Orca, it should read the screen once activated and shortcuts should not be the default option to enable it to work.
5. qt6-qtbase - Qt does not watch for screen reader being enabled properly, rendering Plasma invisible to Orca https://bugzilla.redhat.com/show_bug.cgi?id=2320043 - POST
Orca doesn't read the shell when the screen reader function is activated and so does not display the 'Welcome to Fedora' message on KDE. A fix has been submitted upstream to resolve this issue https://codereview.qt-project.org/c/qt/qtbase/+/598549
6. qt6-qtwayland - KDE apps like KInfoCenter and System Settings sometimes don't start https://bugzilla.redhat.com/show_bug.cgi?id=2318535 - NEW
KInfoCenter doesn't start due to a regression in qt6-qtwayland-6.7.2-4. A patch has been submitted upstream and the issue seems to be resolved by a performance fix in kwin https://codereview.qt-project.org/c/qt/qtwayland/+/574934 . Testing to confirm the issue is resolved would be welcome.
== Accepted Blockers == 1. distribution - osbuild tasks are consistently failing and breaking composes, but building ARM minimal with ImageFactory instead would compromise device support https://bugzilla.redhat.com/show_bug.cgi?id=2320081 - ON_QA
A pipeline rebuild was clearing previous AMIs which was causing build failures for osbuild. This has since been cleared and a new pipeline has been reinstalled and a test compose has been ran successfully https://koji.fedoraproject.org/koji/taskinfo?taskID=125049061, so we are now waiting on compose testing from Qa to verify this resolves the issue.
[1] https://fedorapeople.org/groups/schedule/f-41/f-41-key-tasks.html [2] https://qa.fedoraproject.org/blockerbugs/milestone/41/final/buglist [3] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/...