2024-04-08 @ 16:00 UTC - Fedora 40 Blocker Review Meeting

Hi folks! It’s time for another blocker review meeting. We have 4 proposed blockers and 5 proposed freeze exceptions 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 weekend and see you on Monday!

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

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

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:00:06)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:04:38)
    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:04:47)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:04:51)
    3. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:04:54)
    4. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:04:57)
    5. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:05:01)
    6. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:05:04)
    7. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:05:06)
    8. LINK: https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria (@adamwill:fedora.im, 16:05:09)
    9. LINK: https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria (@adamwill:fedora.im, 16:05:12)
    10. INFO: for Fedora 40 Final, we have: (@adamwill:fedora.im, 16:05:23)
    11. INFO: 4 Proposed Blockers (@adamwill:fedora.im, 16:05:31)
    12. INFO: 1 Accepted Blockers (@adamwill:fedora.im, 16:05:34)
    13. INFO: 1 Accepted Previous Release Blockers (@adamwill:fedora.im, 16:05:36)
    14. INFO: 1 Proposed Freeze Exceptions (@adamwill:fedora.im, 16:05:38)
    15. INFO: 7 Accepted Freeze Exceptions (@adamwill:fedora.im, 16:05:41)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:05:50)
  4. TOPIC:(2273497) 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" (Logitech C920 camera) (@adamwill:fedora.im, 16:05:58)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2273497 (@adamwill:fedora.im, 16:06:00)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1560 (@adamwill:fedora.im, 16:06:03)
    3. INFO: Proposed Blocker, gtk4, NEW (@adamwill:fedora.im, 16:06:05)
    4. INFO: Ticket vote: FinalBlocker (+2,0,-0) (+frantisekz, +geraldosimiao) (@adamwill:fedora.im, 16:06:08)
    5. AGREED: 2273497 - AcceptedBlocker (Final) - this is accepted both because a crash on a widely-used camera model (we found three affected people easily) is bad enough to block on its own, and we found other issues in snapshot in testing (for nirik it doesn't crash but never shows anything, and many folks found it shows 'No Camera Found' when run from overview). we recommend that we revert to Cheese again for F40 final (@adamwill:fedora.im, 16:21:33)
  5. TOPIC:(2274006) [Fedora KDE] Unable to Boot - no kernel-core installed thus no bootloader entry (@adamwill:fedora.im, 16:22:35)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2274006 (@adamwill:fedora.im, 16:22:40)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1575 (@adamwill:fedora.im, 16:22:43)
    3. INFO: Proposed Blocker, kernel, NEW (@adamwill:fedora.im, 16:22:45)
    4. AGREED: 2274006 - punt (delay decision) - we are waiting for further logs from the reporter to determine what happened to them here, it seems to have been a bootloader install failure. We need to know that to fully evaluate this (@adamwill:fedora.im, 16:33:32)
  6. TOPIC:(2273737) [abrt] plasma-systemmonitor: QHashPrivate::iterator<QHashPrivate::Node<QModelIndex, QSortFilterProxyModelPrivate::Mapping*> >::node(): plasma-systemmonitor killed by SIGSEGV (@adamwill:fedora.im, 16:33:39)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2273737 (@adamwill:fedora.im, 16:33:42)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1572 (@adamwill:fedora.im, 16:33:45)
    3. INFO: Proposed Blocker, plasma-systemmonitor, NEW (@adamwill:fedora.im, 16:33:48)
    4. INFO: Ticket vote: FinalBlocker (+1,0,-0) (+geraldosimiao) (@adamwill:fedora.im, 16:33:51)
    5. AGREED: 2273737 - AcceptedBlocker (Final) - this is accepted as a violation of Final criterion "For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test: ...". system monitor is not in the current list, but there is a strong consensus at the meeting (including KDE SIG folks) that this was an oversight in drafting the list and it should always have been there. We will amend the list, and accept this bug in the meantime (@adamwill:fedora.im, 17:01:50)
  7. TOPIC:(2273942) SDDM also displays users with disabled logins (@adamwill:fedora.im, 17:02:00)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2273942 (@adamwill:fedora.im, 17:02:02)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1574 (@adamwill:fedora.im, 17:02:05)
    3. INFO: Proposed Blocker, sddm, NEW (@adamwill:fedora.im, 17:02:07)
    4. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+geraldosimiao) (@adamwill:fedora.im, 17:02:10)
    5. AGREED: 2273942 - RejectedBlocker (Final) AcceptedFreezeException (Final) - this is rejected as a blocker; it's arguably a conditional criterion violation, but only with a fairly unusual condition (manually-created user account with UID >1000 and no login shell). We do grant it an FE, though; if we do want to change the default list of shells that cause a user to be hidden it seems reasonable to do that for release (@adamwill:fedora.im, 17:09:45)
  8. TOPIC:Proposed Final freeze exceptions (@adamwill:fedora.im, 17:10:10)
  9. TOPIC:(2270397) container images built from unsigned packages (@adamwill:fedora.im, 17:10:17)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2270397 (@adamwill:fedora.im, 17:10:19)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1573 (@adamwill:fedora.im, 17:10:21)
    3. INFO: Proposed Freeze Exceptions, distribution, ASSIGNED (@adamwill:fedora.im, 17:10:24)
    4. INFO: Ticket vote: FinalFreezeException (+1,0,-0) (+ngompa) (@adamwill:fedora.im, 17:10:26)
    5. AGREED: 2270397 - RejectedFreezeException (Final) - this is clearly an important problem and we want to fix it, but an F40 Final freeze exception is no use in doing that, as the fix needs to be applied to the builders, which run Fedora 39. What we need is an infrastructure freeze break request, nirik has proposed one on the mailing list, we need releng/sysadmin-main members to vote on that at https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/XFJATU5DDOUDLF7DCBY6JG5CNLKQ4MAT/ (@adamwill:fedora.im, 17:32:36)
  10. TOPIC:Open floor (@adamwill:fedora.im, 17:33:12)
    1. INFO: the one previously-accepted blocker is ON_QA already, the ones accepted during the meeting will need addressing by relevant teams (KDE and GNOME) (@adamwill:fedora.im, 17:33:37)
    2. INFO: we are still waiting for someone to come up with a bright idea to fix 2242759 (or implement one of the current potential bright ideas and show that it's workable). Aoife Moloney will try another email to poke that along (@adamwill:fedora.im, 17:40:16)

Meeting ended at 17:44:45 UTC

Action items

  1. (none)

People present (lines said)

  1. @adamwill:fedora.im (189)
  2. @conan_kudo:matrix.org (84)
  3. @geraldosimiao:matrix.org (50)
  4. @nirik:matrix.scrye.com (30)
  5. @nielsenb:fedora.im (26)
  6. @lruzicka:matrix.org (23)
  7. @frantisekz:fedora.im (17)
  8. @decathorpe:fedora.im (12)
  9. @amoloney:fedora.im (11)
  10. @marcdeop:matrix.org (8)
  11. @zodbot:fedora.im (6)
  12. @aleasto:matrix.org (3)
  13. @meetbot:fedora.im (2)
  14. @1vx:matrix.org (1)