2024-08-26 @ 16:00 UTC - Fedora 41 Blocker Review Meeting

Project Discussion
, ,
1

Hi folks! It’s time for another blocker review meeting. We have 1 proposed blocker and 1 proposed freeze exception for Beta, and 2 proposed blockers for Final.

Here is a handy link which should show you the meeting time in your local time.

The meeting will be on Matrix. Click the link above to join in a web client - you can authenticate with your FAS account - or use a dedicated client of your choosing.

If you have time this weekend, you can take a look at the proposed or accepted blockers before the meeting - the full lists can be found here.

Remember, you can also now vote on bugs outside of review meetings! If you look at the bug list in the blockerbugs app, you’ll see links labeled “Vote!” next to all proposed blockers and freeze exceptions. Those links take you to tickets where you can vote. This page has instructions on how exactly you do it. We usually go through the tickets shortly before the meeting and apply any clear votes, so the meeting will just cover bugs where there wasn’t a clear outcome in the ticket voting yet. THIS MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!

We’ll be evaluating these bugs to see if they violate any of the Release Criteria and warrant the blocking of a release if they’re not fixed. Information on the release criteria for F40 can be found on the wiki.

For more information about the Blocker and Freeze exception process, check out these links:

And for those of you who are curious how a Blocker Review Meeting works - or how it’s supposed to go and you want to run one - check out the SOP on the wiki.

Have a good day and see you tomorrow!

2

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:17)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:06:34)
    1. 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:06:42)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:06:44)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:06:47)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:06:50)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:06:52)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:06:55)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:06:57)
    8. LINK: https://fedoraproject.org/wiki/Fedora_41_Beta_Release_Criteria (@adamwill:fedora.im, 16:07:00)
    9. LINK: https://fedoraproject.org/wiki/Fedora_41_Final_Release_Criteria (@adamwill:fedora.im, 16:07:02)
    10. INFO: for Beta, we have 1 proposed blocker and 1 proposed FE (@adamwill:fedora.im, 16:07:20)
    11. INFO: for Final, we have 2 proposed blockers (@adamwill:fedora.im, 16:07:37)
    12. INFO: František Zatloukal will secretarialize, thanks (@adamwill:fedora.im, 16:08:04)
  3. TOPIC:Proposed Beta blockers (@adamwill:fedora.im, 16:08:10)
  4. TOPIC:(2270430) Raspberry Pi 4: KDE initial setup is broken without nomodeset, KDE desktop won't load with nomodeset (@adamwill:fedora.im, 16:08:19)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270430 (@adamwill:fedora.im, 16:08:23)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1621 (@adamwill:fedora.im, 16:08:26)
    3. INFO: Proposed Blocker, mesa, NEW (@adamwill:fedora.im, 16:08:28)
    4. AGREED: 2270430 - AcceptedBlocker (Beta) - this is accepted as a violation of Basic criterion "A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility", for the now release-blocking configuration of KDE on the Raspberry PI (@adamwill:fedora.im, 16:22:18)
  5. TOPIC:Proposed Beta freeze exception (@adamwill:fedora.im, 16:22:34)
  6. TOPIC:(2307728) gtk4 4.15.5 breaks display change confirmation dialog on X11 (@adamwill:fedora.im, 16:22:36)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2307728 (@adamwill:fedora.im, 16:22:39)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1624 (@adamwill:fedora.im, 16:22:43)
    3. INFO: Proposed Freeze Exceptions, gtk4, NEW (@adamwill:fedora.im, 16:22:45)
    4. AGREED: 2307728 - AcceptedFreezeException (Beta) - this is accepted as it breaks significant functionality on non-release-blocking desktops (including Budgie). we will check with GTK folks that the fix should be safe before landing it (@adamwill:fedora.im, 16:28:27)
  7. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:28:43)
  8. TOPIC:(2307278) ABRT does not catch app crashes on Fedora 41 (@adamwill:fedora.im, 16:28:45)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2307278 (@adamwill:fedora.im, 16:28:48)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1622 (@adamwill:fedora.im, 16:28:50)
    3. INFO: Proposed Blocker, abrt, NEW (@adamwill:fedora.im, 16:28:52)
    4. AGREED: 2307278 - AcceptedBlocker (Final) AcceptedFreezeException (Beta) - this is accepted as a violation of the "basic functionality" criterion for the crash reporter app. We also accept it as a Beta FE as this is significant functionality for Beta testing, the value of Beta testing is lessened if this does not work (@adamwill:fedora.im, 16:35:27)
  9. TOPIC:(2303813) With 6.10 kernels before 6.10.5 and 6.11 kernels before rc4, gnome-disks is partly nonfunctional (@adamwill:fedora.im, 16:36:09)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2303813 (@adamwill:fedora.im, 16:36:11)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1616 (@adamwill:fedora.im, 16:36:14)
    3. INFO: Proposed Blocker, kernel, POST (@adamwill:fedora.im, 16:36:16)
    4. AGREED: 2303813 - punt (delay decision) - we're still not really clear on the contours of this or whether it's already fixed, due to differing hardware and lack of input from the reporter (@adamwill:fedora.im, 16:48:32)
  10. TOPIC:Accepted Beta blockers (@adamwill:fedora.im, 16:49:51)
    1. INFO: reminder: we are not revoting here, just checking status (@adamwill:fedora.im, 16:49:58)
  11. TOPIC:(2305763) Orca crashes on Fedora 41 Pre-beta due to a Python "AttributeError". (@adamwill:fedora.im, 16:50:10)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2305763 (@adamwill:fedora.im, 16:50:13)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1620 (@adamwill:fedora.im, 16:50:15)
    3. INFO: Accepted Blocker, at-spi2-core, ON_QA (@adamwill:fedora.im, 16:50:17)
    4. INFO: this ought to be fixed, would be good if we can get confirmation (@adamwill:fedora.im, 16:50:29)
  12. TOPIC:(2276839) Fedora 41: Workstation live x86_64 image exceeds maximum size (@adamwill:fedora.im, 16:51:48)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2276839 (@adamwill:fedora.im, 16:51:50)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1602 (@adamwill:fedora.im, 16:51:53)
    3. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 16:51:55)
    4. INFO: the plan here is "Let's try dropping botocore, and if that's not enough, the Workstation WG is okay to raise to 2.5GiB." unclear on the status of the botocore change (@adamwill:fedora.im, 16:52:22)
    5. ACTION: Conan Kudo to try and implement dropping botocore from the image (@adamwill:fedora.im, 16:54:30)
  13. TOPIC:(2305291) GRUB 2.12 generated grub.cfg does not work with GRUB 2.06 (@adamwill:fedora.im, 16:54:42)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2305291 (@adamwill:fedora.im, 16:54:46)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1618 (@adamwill:fedora.im, 16:54:49)
    3. INFO: Accepted Blocker, grub2, NEW (@adamwill:fedora.im, 16:54:52)
    4. INFO: we could use some testing to clarify if IoT is affected by this (@adamwill:fedora.im, 16:59:55)
  14. TOPIC:(2282171) gsk: vulkan renderer breaks gtk4 apps on Raspberry Pi 4 and 400 (@adamwill:fedora.im, 17:01:35)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2282171 (@adamwill:fedora.im, 17:01:38)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1605 (@adamwill:fedora.im, 17:01:40)
    3. INFO: Accepted Blocker, gtk4, NEW (@adamwill:fedora.im, 17:01:42)
    4. INFO: we seem to be making some progress with getting the different upstreams to collaborate on this, will keep monitoring it (@adamwill:fedora.im, 17:09:09)
  15. TOPIC:(2283978) Raspberry Pi 4 automatically suspends when idle, claims to support suspend, but can't be woken up (@adamwill:fedora.im, 17:10:13)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2283978 (@adamwill:fedora.im, 17:10:16)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1607 (@adamwill:fedora.im, 17:10:18)
    3. INFO: Accepted Blocker, kernel, NEW (@adamwill:fedora.im, 17:10:20)
    4. INFO: we still will probably have to document or waive this, it doesn't look like anyone came up with any bright ideas (@adamwill:fedora.im, 17:10:39)
  16. TOPIC:Open floor (@adamwill:fedora.im, 17:14:19)


Meeting ended at 17:22:18 UTC

Action items

  1. Conan Kudo to try and implement dropping botocore from the image


People present (lines said)

  1. @adamwill:fedora.im (141)
  2. @frantisekz:fedora.im (40)
  3. @conan_kudo:matrix.org (30)
  4. @nirik:matrix.scrye.com (17)
  5. @nhanlon:beeper.com (6)
  6. @zodbot:fedora.im (5)
  7. @robatino:fedora.im (3)
  8. @naraiank:fedora.im (3)
  9. @salimma:fedora.im (2)
  10. @meetbot:fedora.im (2)