#blocker-review:fedoraproject.org: F41-blocker-review

Meeting started by @adamwill:fedora.im at 16:00:02 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:05)
    1. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:05:03)
    2. INFO: Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs. (@adamwill:fedora.im, 16:05:03)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:05:03)
    1. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:05:03)
    2. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:05:03)
    3. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:03)
    4. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:03)
    5. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:03)
    6. LINK: https://fedoraproject.org/wiki/Fedora_41_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:03)
    7. LINK: https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria (@adamwill:fedora.im, 16:05:03)
    8. INFO: for F41 Final, we have: (@adamwill:fedora.im, 16:05:16)
    9. INFO: 1 Accepted Blockers (@adamwill:fedora.im, 16:05:17)
    10. INFO: 1 Accepted 0-day Blockers (@adamwill:fedora.im, 16:05:17)
    11. INFO: 6 Proposed Blockers (@adamwill:fedora.im, 16:05:17)
    12. INFO: 3 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:05:21)
    13. INFO: 7 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:05:21)
    14. INFO: FrantiĊĦek Zatloukal will secretarialize (@adamwill:fedora.im, 16:05:42)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:05:48)
    1. INFO: several of these technically have enough ticket votes for a decision already, but I decided to keep them on the agenda as we're trying to pull together a candidate to make extra sure we're all on the same page (@adamwill:fedora.im, 16:06:18)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2316066 (@adamwill:fedora.im, 16:06:30)
    3. INFO: Ticket vote: FinalBlocker (+8,1,-1) (+asciiwolf, +jmaybaum, +sumantrom, +ngompa, +catanzaro, +pbrobinson, +lruzicka, +thebeanogamer, geraldosimiao, -nielsenb) (@adamwill:fedora.im, 16:06:30)
    4. INFO: Proposed Blocker, cups, POST (@adamwill:fedora.im, 16:06:30)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1677 (@adamwill:fedora.im, 16:06:30)
  4. TOPIC:(2316066) dbus activated apps including the welcome dialog suffer 30-45 sec delay and/or crash on Workstation Live image randomly (@adamwill:fedora.im, 16:06:30)
    1. AGREED: 2316066 - punt (delay decision) - voting on this is at +8 / -7, so it's undecided. as it's an accepted FE and we have a probably-good fix for it, we're expecting to pull that fix in and make this go away that way. (@adamwill:fedora.im, 16:16:48)
    2. INFO: Proposed Blocker, kernel, ON_QA (@adamwill:fedora.im, 16:17:00)
    3. INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+asciiwolf, +adamwill, +kevin) (@adamwill:fedora.im, 16:17:00)
  5. TOPIC:(2319597) Bluetooth devices are not getting paired (@adamwill:fedora.im, 16:17:00)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2319597 (@adamwill:fedora.im, 16:17:00)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1721 (@adamwill:fedora.im, 16:17:00)
    3. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+asciiwolf, +geraldosimiao, +lruzicka, +kparal) (@adamwill:fedora.im, 16:17:00)
    4. AGREED: 2319597 - AcceptedBlocker (Final) - there definitely seems to be enough of an indication that bluetooth is broken enough in 6.11.3 (which was stable in F41) to affect live media use cases, even potentially making it unusable if you have to use bluetooth peripherals, so this is accepted as a violation of audio criteria and any criterion requiring input, in the case that bluetooth periperals are required and the hardware is affected by this bug (@adamwill:fedora.im, 16:23:23)
    5. INFO: we have three KDE screen reader issues coming up: 2320046 , 2320044 , 2320043 . let's have a bit of a pre-discussion about how to handle this (@adamwill:fedora.im, 16:24:12)
    6. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+nielsenb, +geraldosimiao, +thebeanogamer, +lruzicka) (@adamwill:fedora.im, 16:28:07)
    7. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320043 (@adamwill:fedora.im, 16:28:07)
    8. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1723 (@adamwill:fedora.im, 16:28:07)
    9. INFO: Proposed Blocker, qt6-qtbase, MODIFIED (@adamwill:fedora.im, 16:28:07)
  6. TOPIC:(2320043) Qt does not watch for screen reader being enabled properly, rendering Plasma invisible to Orca (@adamwill:fedora.im, 16:28:07)
    1. AGREED: 2320043 - AcceptedBlocker (Final) - this is accepted as a conditional violation of all desktop related criteria for KDE for all people who need a screen reader (same rationale on which we previously accepted 2305763) (@adamwill:fedora.im, 16:30:58)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320046 (@adamwill:fedora.im, 16:31:13)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1725 (@adamwill:fedora.im, 16:31:13)
    4. INFO: Ticket vote: FinalBlocker (+3,0,-0) (+nielsenb, +thebeanogamer, +lruzicka) (@adamwill:fedora.im, 16:31:13)
    5. INFO: Proposed Blocker, konsole, NEW (@adamwill:fedora.im, 16:31:13)
  7. TOPIC:(2320046) Konsole command output isn't read by the screen reader (@adamwill:fedora.im, 16:31:13)
    1. AGREED: 2320046 - RejectedBlocker (Final), AcceptedFreezeException (Final) - this is rejected as a blocker as the problem is not too critical: screen reading works, and all content can be read, it just seems necessary to prompt the reader to continue (using the normal key for this purpose) at points where it seems like that shouldn't be necessary. we also note that this is not new behaviour (previous releases behaved the same) (@adamwill:fedora.im, 16:41:46)
    2. INFO: Proposed Blocker, plasma-welcome, NEW, depends on other bugs (@adamwill:fedora.im, 16:42:07)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320044 (@adamwill:fedora.im, 16:42:07)
  8. TOPIC:(2320044) Plasma Welcome isn't read by the screen reader when activated (@adamwill:fedora.im, 16:42:07)
    1. INFO: Ticket vote: FinalBlocker (+4,0,-0) (+nielsenb, +geraldosimiao, +thebeanogamer, +lruzicka) (@adamwill:fedora.im, 16:42:07)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1724 (@adamwill:fedora.im, 16:42:07)
    3. AGREED: 2320044 - RejectedBlocker (Final), AcceptedFreezeException (Final) - this is rejected as a blocker as the problem is not too critical: screen reading works, and all critical content can be read, it just seems necessary to prompt the reader to get body content read (using the normal key for this purpose) at points where it seems like that shouldn't be necessary. we also note that this is not new behaviour (previous releases behaved the same) (@adamwill:fedora.im, 16:50:49)
    4. INFO: Proposed Blocker, qt6-qtwayland, NEW (@adamwill:fedora.im, 16:51:05)
    5. INFO: Ticket vote: FinalBlocker (+1,0,-1) (+lruzicka, -nielsenb) (@adamwill:fedora.im, 16:51:05)
  9. TOPIC:(2318535) KDE apps like KInfoCenter and System Settings sometimes don't start (@adamwill:fedora.im, 16:51:05)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2318535 (@adamwill:fedora.im, 16:51:05)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1694 (@adamwill:fedora.im, 16:51:05)
    3. AGREED: 2318535 - RejectedBlocker (Final) RejectedFreezeException (Final) - this seems to be pretty much entirely mitigated by the fix for KDE performance under software acceleration (https://bugzilla.redhat.com/show_bug.cgi?id=2312900 ). there probably is still technically a bug here, and upstream is working on it, but it doesn't seem like we need to rush to pull it in for release (@adamwill:fedora.im, 16:56:57)
  10. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 16:57:15)
    1. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+augenauf) (@adamwill:fedora.im, 16:57:27)
    2. INFO: Proposed Freeze Exceptions, golang, NEW (@adamwill:fedora.im, 16:57:27)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1715 (@adamwill:fedora.im, 16:57:27)
    4. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2310555 (@adamwill:fedora.im, 16:57:27)
  11. TOPIC:(2310555) CVE-2024-34156 golang: Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion [fedora-all] (@adamwill:fedora.im, 16:57:27)
    1. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+augenauf) (@adamwill:fedora.im, 16:57:27)
    2. INFO: this bug is actually closed, seems to be a blip in blockerbugs. moving on (@adamwill:fedora.im, 16:58:20)
    3. AGREED: 2310555 - RejectedBlocker (Final) RejectedFreezeException (Final) - this is rejected on the basis that the issues caused can be "satisfactorily resolved by a package update" (per the criteria). anything built with Go and persistently parsing untrusted input is probably some kind of system service which should be deployed only on an installed system. we are not aware of any likely context in which this vulnerability would be exposed in a live or installer environment (@adamwill:fedora.im, 17:13:08)
    4. INFO: Proposed Freeze Exceptions, rust-cursive0.16, MODIFIED (@adamwill:fedora.im, 17:13:37)
  12. TOPIC:(2320157) F41FailsToInstall: rust-cursive0.16+crossterm-devel, rust-cursive0.16+pancurses-devel (@adamwill:fedora.im, 17:13:37)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1728 (@adamwill:fedora.im, 17:13:37)
    2. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+frantisekz) (@adamwill:fedora.im, 17:13:37)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320157 (@adamwill:fedora.im, 17:13:37)
    4. AGREED: 2320157 - AcceptedFreezeException (Final) - this is accepted as we generally accept FTI fixes in the interest of keeping the frozen final repo as consistent as possible (@adamwill:fedora.im, 17:20:16)
    5. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1727 (@adamwill:fedora.im, 17:20:28)
    6. INFO: Ticket vote: FinalFreezeException (+2,0,-0) (+lruzicka, +frantisekz) (@adamwill:fedora.im, 17:20:28)
  13. TOPIC:(2320158) F41FailsToInstall: rust-termbg-devel (@adamwill:fedora.im, 17:20:28)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320158 (@adamwill:fedora.im, 17:20:28)
    2. INFO: Proposed Freeze Exceptions, rust-termbg, VERIFIED (@adamwill:fedora.im, 17:20:28)
    3. AGREED: 2320158 - AcceptedFreezeException (Final) - this is accepted as we generally accept FTI fixes in the interest of keeping the frozen final repo as consistent as possible (@adamwill:fedora.im, 17:26:18)
  14. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 17:26:32)
    1. INFO: Accepted Blocker, distribution, ON_QA (@adamwill:fedora.im, 17:26:43)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1726 (@adamwill:fedora.im, 17:26:43)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2320081 (@adamwill:fedora.im, 17:26:43)
  15. TOPIC:(2320081) osbuild tasks are consistently failing and breaking composes, but building ARM minimal with ImageFactory instead would compromise device support (@adamwill:fedora.im, 17:26:43)
    1. INFO: this is marked ON_QA as osbuild team believes they have resolved the issue. we will fire the next compose when we're ready, and find out. :D no action required ATM (@adamwill:fedora.im, 17:27:03)
  16. TOPIC:(2318710) updating F41 Beta in offline mode reboots into maintenance mode due to "ext4 bad orphan inode" errors (@adamwill:fedora.im, 17:27:11)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1697 (@adamwill:fedora.im, 17:27:11)
    2. INFO: Accepted Blocker, kernel, ON_QA (@adamwill:fedora.im, 17:27:11)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2318710 (@adamwill:fedora.im, 17:27:11)
    4. INFO: there's some uncertainty about whether this is fully fixed yet, kparal and adamw are seeing differing results in testing. we will continue to test, if others want to help out that'd be great (@adamwill:fedora.im, 17:33:50)
    5. INFO: we now have a BETTER suspect for the discrepancy here: the official update build did not apply the patch that fixes the bug (@adamwill:fedora.im, 17:37:58)
    6. ACTION: adamw to fix that up, kparal to re-test (@adamwill:fedora.im, 17:38:04)
  17. TOPIC:(2318559) Fedora media writer downloads wrong iso when kde spin is selected (@adamwill:fedora.im, 17:42:19)
    1. INFO: Accepted 0-day Blocker, mediawriter, ASSIGNED (@adamwill:fedora.im, 17:42:19)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2318559 (@adamwill:fedora.im, 17:42:19)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1695 (@adamwill:fedora.im, 17:42:19)
    4. INFO: this is more or less dealt with, though we need the websites updated to point to the new release of fmw, and there's some oddness to how the metadata got to be wrong that we should work out (@adamwill:fedora.im, 17:47:48)
  18. TOPIC:Open floor (@adamwill:fedora.im, 17:49:54)


Meeting ended at 18:01:09 UTC

Action items

  1. adamw to fix that up, kparal to re-test


People present (lines said)

  1. @adamwill:fedora.im (229)
  2. @conan_kudo:matrix.org (53)
  3. @nielsenb:fedora.im (32)
  4. @nirik:matrix.scrye.com (32)
  5. @sgallagh:fedora.im (30)
  6. @decathorpe:fedora.im (24)
  7. @frantisekz:fedora.im (24)
  8. @zodbot:fedora.im (13)
  9. @kparal:matrix.org (12)
  10. @derekenz:fedora.im (11)
  11. @meetbot:fedora.im (2)
  12. @siosm:matrix.org (1)
  13. @lbrabec:matrix.org (1)
  14. @dustymabe:matrix.org (1)