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

Meeting started by @adamwill:fedora.im at 16:01:19 UTC

Meeting summary

  1. TOPIC:Roll Call (@adamwill:fedora.im, 16:01:24)
    1. INFO: The bugs up for review today are available at: (@adamwill:fedora.im, 16:07:15)
  2. TOPIC:Introduction (@adamwill:fedora.im, 16:07:15)
    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:07:15)
    2. INFO: We'll be following the process outlined at: (@adamwill:fedora.im, 16:07:15)
    3. INFO: The criteria for release blocking bugs can be found at: (@adamwill:fedora.im, 16:07:15)
    4. LINK: https://fedoraproject.org/wiki/Basic_Release_Criteria (@adamwill:fedora.im, 16:07:15)
    5. LINK: https://fedoraproject.org/wiki/Fedora_43_Beta_Release_Criteria (@adamwill:fedora.im, 16:07:15)
    6. LINK: https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria (@adamwill:fedora.im, 16:07:15)
    7. LINK: http://qa.fedoraproject.org/blockerbugs/current (@adamwill:fedora.im, 16:07:15)
    8. LINK: https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting (@adamwill:fedora.im, 16:07:15)
    9. INFO: for Fedora 43 Final, we have: 10 proposed blockers and 2 proposed freeze exceptions (I'll cut that down a bit as we go) (@adamwill:fedora.im, 16:07:45)
    10. INFO: lruzicka will secretarialize later (@adamwill:fedora.im, 16:08:02)
  3. TOPIC:Proposed Final blockers (@adamwill:fedora.im, 16:08:17)
  4. TOPIC:(2397086) Drop-down menus not working over RDP in Anaconda (@adamwill:fedora.im, 16:08:33)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2397086 (@adamwill:fedora.im, 16:08:33)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1943 (@adamwill:fedora.im, 16:08:33)
    3. INFO: Ticket vote: FinalBlocker (+5,0,-0) (+boniboyblue, +kparal, +lruzicka, +derekenz, +geraldosimiao) (@adamwill:fedora.im, 16:08:33)
    4. INFO: Proposed Blocker, anaconda, NEW (@adamwill:fedora.im, 16:08:33)
    5. AGREED: 2397086 - AcceptedBlocker (Final) - this is accepted as a conditional violation of Basic criterion "When using a dedicated installer image, the installer must be able to complete an installation using the text, graphical and RDP installation interfaces.". while it's technically possible to complete an install, this makes it hard if you need for any reason to use any dropdown menu (in gtkui), which is pretty common, and we agree that's common enough to constitute a blocker (@adamwill:fedora.im, 16:17:15)
    6. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1938 (@adamwill:fedora.im, 16:17:26)
    7. INFO: Ticket vote: FinalBlocker (+5,1,-0) (+chrismurphy, +nielsenb, +boniboyblue, +lruzicka, +derekenz, kparal) (@adamwill:fedora.im, 16:17:26)
    8. INFO: Proposed Blocker, anaconda-webui, POST (@adamwill:fedora.im, 16:17:26)
  5. TOPIC:(2396646) The web UI doesn't warn users when reusing a /home partition on an encrypted disk. (@adamwill:fedora.im, 16:17:26)
    1. INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+geraldosimiao, +nielsenb, +kparal) (@adamwill:fedora.im, 16:17:26)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2396646 (@adamwill:fedora.im, 16:17:26)
    3. AGREED: 2396646 - AcceptedBlocker (Final) - this is accepted as a violation of "the installer must be able to: ... Assign mount points to existing storage volumes", noting the "Re-using /home" footnote below, in the specific case that the /home to be reused is both encrypted and a direct-on-disk filesystem (not a partition). this is a fairly uncommon case but we decided it was potentially common enough (given the webui's ability to create such a layout) that we should block on it (@adamwill:fedora.im, 16:40:32)
    4. INFO: Ticket vote: FinalFreezeException (+3,0,-0) (+kparal, +lruzicka, +geraldosimiao) (@adamwill:fedora.im, 16:40:42)
    5. INFO: Proposed Blocker, authselect, ASSIGNED (@adamwill:fedora.im, 16:40:42)
    6. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1936 (@adamwill:fedora.im, 16:40:42)
    7. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2396016 (@adamwill:fedora.im, 16:40:42)
  6. TOPIC:(2396016) Authselect doesn't regenerate new profile with pam_lastlog2 support in Fedora Silverblue 43 (@adamwill:fedora.im, 16:40:42)
    1. INFO: Ticket vote: FinalBlocker (+0,0,-6) (-boniboyblue, -nielsenb, -kparal, -lruzicka, -catanzaro, -geraldosimiao) (@adamwill:fedora.im, 16:40:42)
    2. AGREED: 2396016 - RejectedBlocker (Final) - so far we think it's pretty clear this doesn't meet the criteria ("For each one of the release-blocking package sets, it must be possible to successfully complete a direct upgrade from a fully updated, clean default installation of each of the last two stable Fedora releases with that package set installed.") We're not sure the issue is restricted to Silverblue, but openQA testing at least indicates it's not affecting a clean F41 -> F43 upgrade (@adamwill:fedora.im, 16:51:41)
    3. INFO: Proposed Blocker, distribution, NEW (@adamwill:fedora.im, 16:51:50)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1941 (@adamwill:fedora.im, 16:51:50)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2397163 (@adamwill:fedora.im, 16:51:50)
    6. INFO: Ticket vote: FinalBlocker (+5,0,-1) (+leigh123linux, +catanzaro, +imsedgar, +nielsenb, +lruzicka, -kevin) (@adamwill:fedora.im, 16:51:50)
  7. TOPIC:(2397163) openh264 repository issues (like geoblocking) prevent various package management operations (@adamwill:fedora.im, 16:51:50)
    1. AGREED: 2397163 - RejectedBlocker (Final) - we agree this is a very awkward state for folks in affected locations, but as there is no entirely Fedora-controlled "fix" possible and the issue is not entirely limited to Fedora 43, we agreed it doesn't make sense to block on it. we will wait on cisco to complete the process of refining their geoblock, then see where we stand and if we need to consider any changes on the fedora side (@adamwill:fedora.im, 17:25:29)
    2. INFO: Ticket vote: FinalBlocker (+3,0,-0) (+kparal, +lruzicka, +derekenz) (@adamwill:fedora.im, 17:25:50)
    3. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1944 (@adamwill:fedora.im, 17:25:50)
    4. INFO: Proposed Blocker, gnome-shell, POST (@adamwill:fedora.im, 17:25:50)
  8. TOPIC:(2397256) gnome-shell crashes when dragging a Chromium tab into a new window (@adamwill:fedora.im, 17:25:50)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2397256 (@adamwill:fedora.im, 17:25:50)
    2. AGREED: 2397256 - AcceptedBlocker (Final) - this is accepted as a violation of the cited criterion, counting 'drag tab to create a new window') as a "regular operation" for a browser, and noting that while chromium/chrome is not the default browser in any Fedora edition, they are very widely used so we can expect this bug will be commonly encountered, and the consqeuence is very bad (full desktop crash) (@adamwill:fedora.im, 17:34:50)
    3. INFO: Proposed Blocker, gnome-software, VERIFIED (@adamwill:fedora.im, 17:35:03)
    4. INFO: Ticket vote: FinalFreezeException (+6,0,-0) (+boniboyblue, +adamwill, +geraldosimiao, +nielsenb, +kparal, +kashyapc) (@adamwill:fedora.im, 17:35:03)
    5. INFO: Ticket vote: FinalBlocker (+3,0,-4) (+asciiwolf, +lruzicka, +derekenz, -boniboyblue, -nielsenb, -kparal, -kashyapc) (@adamwill:fedora.im, 17:35:03)
  9. TOPIC:(2395811) libreoffice language packs not found in gnome-software (@adamwill:fedora.im, 17:35:03)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2395811 (@adamwill:fedora.im, 17:35:03)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1930 (@adamwill:fedora.im, 17:35:03)
    3. AGREED: 2395811 - RejectedBlocker (Final) - this is rejected as, while it's unfortunate, it doesn't obviously break any criteria (and we note it's just the same as the longstanding experience on KDE). It's already accepted as an FE (@adamwill:fedora.im, 17:44:09)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1937 (@adamwill:fedora.im, 17:44:20)
    5. INFO: Proposed Blocker, uboot-tools, NEW (@adamwill:fedora.im, 17:44:20)
    6. INFO: Ticket vote: FinalBlocker (+3,0,-0) (+nielsenb, +lruzicka, +derekenz) (@adamwill:fedora.im, 17:44:20)
    7. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2396309 (@adamwill:fedora.im, 17:44:20)
  10. TOPIC:(2396309) Radxa Rock Pi 4 and Pine64 RockPro64 boards fail to boot, probably all RockChip models (@adamwill:fedora.im, 17:44:20)
    1. AGREED: 2396309 - AcceptedBlocker (Final) - this is accepted as a violation of "All release-blocking images must boot in their supported configurations" on all (we believe) Rockchip SBCs, with the Workstation and KDE aarch64 disk images (which are release-blocking and produced by Kiwi so affected by the bug) (@adamwill:fedora.im, 17:53:04)
    2. INFO: there are no proposed FEs (@adamwill:fedora.im, 17:53:26)
  11. TOPIC:Accepted Final blockers (@adamwill:fedora.im, 17:53:36)
  12. TOPIC:(2360054) Fedora 43: Everything boot x86_64 image exceeds maximum size (@adamwill:fedora.im, 17:54:03)
    1. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 17:54:03)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1857 (@adamwill:fedora.im, 17:54:03)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2360054 (@adamwill:fedora.im, 17:54:03)
    4. INFO: adamw did an investigation at https://bugzilla.redhat.com/show_bug.cgi?id=2360054#c40 . based on that we may be able to get the size under 1.2G. under 1G is unlikely. this applies to the Server x86_64 netinst as well, and likely also mostly applies to the aarch64 Server and Everything images (@adamwill:fedora.im, 17:54:50)
    5. ACTION: adamw to see if he can propose some trims, then likely also propose bumping the limits which are still at 1G to 1.2G (@adamwill:fedora.im, 17:55:24)
    6. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 18:02:59)
    7. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1859 (@adamwill:fedora.im, 18:02:59)
    8. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2360056 (@adamwill:fedora.im, 18:02:59)
  13. TOPIC:(2360056) Fedora 43: Workstation live x86_64 image exceeds maximum size (@adamwill:fedora.im, 18:02:59)
    1. INFO: adamwill also investigated this one, although not in as much detail because...erofs is weird or something? https://bugzilla.redhat.com/show_bug.cgi?id=2360056#c38 (@adamwill:fedora.im, 18:03:26)
  14. TOPIC:(2394358) Fedora 43: Container_Toolbox container x86_64 image exceeds maximum size (@adamwill:fedora.im, 18:06:22)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2394358 (@adamwill:fedora.im, 18:06:22)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1918 (@adamwill:fedora.im, 18:06:22)
    3. INFO: Accepted Blocker, distribution, ASSIGNED (@adamwill:fedora.im, 18:06:22)
    4. INFO: this is kinda on the toolbox team (debarshi) now we figured out more or less the background (see https://bugzilla.redhat.com/show_bug.cgi?id=2393443 ), we have needinfo'd him (@adamwill:fedora.im, 18:08:14)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2394213 (@adamwill:fedora.im, 18:08:25)
  15. TOPIC:(2394213) default hostonly-mode "sloppy" results in significant increase in initramfs size (@adamwill:fedora.im, 18:08:25)
    1. INFO: Accepted Blocker, dracut, MODIFIED (@adamwill:fedora.im, 18:08:25)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1925 (@adamwill:fedora.im, 18:08:25)
    3. INFO: this is gradually getting worked out between upstream and downstream, seems like it's actively being worked on and we should have a good resolution (@adamwill:fedora.im, 18:08:52)
    4. ACTION: pvalena to continue working out the best backport strategy for F43 release and post-release updates (@adamwill:fedora.im, 18:13:10)
    5. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2391242 (@adamwill:fedora.im, 18:13:38)
    6. INFO: Accepted Blocker, firefox, NEW (@adamwill:fedora.im, 18:13:38)
  16. TOPIC:(2391242) Graphical glitches, slow performance and/or crashes using Firefox on AMD graphics adapters (@adamwill:fedora.im, 18:13:38)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1896 (@adamwill:fedora.im, 18:13:38)
    2. INFO: a lot of progress has been made on this one at various levels and we now have a pretty clear understanding of the bug. it looks like it is ultimately firefox doing something wrong. we have pretty high confidence this can be addressed somehow soon. appropriate maintainers are aware of the problem at all levels (@adamwill:fedora.im, 18:14:27)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2394950 (@adamwill:fedora.im, 18:14:39)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1926 (@adamwill:fedora.im, 18:14:39)
    5. INFO: Accepted Blocker, glycin, NEW, depends on other bugs (@adamwill:fedora.im, 18:14:39)
  17. TOPIC:(2394950) No thumbnails for video, music, epub and pdf formats (@adamwill:fedora.im, 18:14:39)
    1. INFO: there is a plan outlined at https://bugzilla.redhat.com/show_bug.cgi?id=2394950#c8 , so this is in the desktop team's court ATM (@adamwill:fedora.im, 18:15:23)
    2. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2395957 (@adamwill:fedora.im, 18:15:38)
    3. INFO: Accepted Blocker, gnome-initial-setup, NEW (@adamwill:fedora.im, 18:15:38)
  18. TOPIC:(2395957) Incorrect keyboard layout in Initial Setup (@adamwill:fedora.im, 18:15:38)
    1. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1932 (@adamwill:fedora.im, 18:15:38)
    2. INFO: we need the desktop team to take a look at this. mcatanzaro has CCed himself so they should be aware. we could also try to pin the cause down a little more, possibly (@adamwill:fedora.im, 18:16:46)
    3. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2372978 (@adamwill:fedora.im, 18:16:59)
    4. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1927 (@adamwill:fedora.im, 18:16:59)
    5. INFO: Accepted Blocker, libdnf, POST (@adamwill:fedora.im, 18:16:59)
  19. TOPIC:(2372978) packagekitd shows "failed to add subkeys for /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-XX-secondary" errors every second and consumes a lot of CPU if google-chrome repository is enabled (@adamwill:fedora.im, 18:16:59)
    1. INFO: this one has been fully worked out and a fix proposed and tested, we just need to wait for a new libdnf release or backport it. adamw may backport the fix soon since it's quite a bad bug (@adamwill:fedora.im, 18:17:30)
    2. INFO: Accepted Blocker, selinux-policy, ASSIGNED (@adamwill:fedora.im, 18:17:49)
  20. TOPIC:(2394561) SELinux is preventing systemd from 'open' accesses on the file /tmp/webui-cockpit-ws.env. (@adamwill:fedora.im, 18:17:49)
    1. LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2394561 (@adamwill:fedora.im, 18:17:49)
    2. LINK: https://pagure.io/fedora-qa/blocker-review/issue/1922 (@adamwill:fedora.im, 18:17:49)
    3. ACTION: adamw and lruzicka to work with pvalena and cockpit team to explain why this is a blocker and figure out a way forward (@adamwill:fedora.im, 18:18:55)
  21. TOPIC:Open floor (@adamwill:fedora.im, 18:20:50)


Meeting ended at 18:30:05 UTC

Action items

  1. adamw to see if he can propose some trims, then likely also propose bumping the limits which are still at 1G to 1.2G
  2. pvalena to continue working out the best backport strategy for F43 release and post-release updates
  3. adamw and lruzicka to work with pvalena and cockpit team to explain why this is a blocker and figure out a way forward


People present (lines said)

  1. @adamwill:fedora.im (274)
  2. @kparal:matrix.org (53)
  3. @supakeen:fedora.im (38)
  4. @nielsenb:fedora.im (31)
  5. @nirik:matrix.scrye.com (20)
  6. @derekenz:fedora.im (19)
  7. @geraldosimiao:matrix.org (15)
  8. @conan_kudo:matrix.org (13)
  9. @zodbot:fedora.im (13)
  10. @kashyapc:fedora.im (11)
  11. @decathorpe:fedora.im (11)
  12. @cmurf:fedora.im (11)
  13. @boniboyblue:fedora.im (8)
  14. @pboy:fedora.im (7)
  15. @pvalena:fedora.im (7)
  16. @aggraxis:fedora.im (7)
  17. @jlinton:fedora.im (3)
  18. @meetbot:fedora.im (2)
  19. @pvalena:matrix.org (2)
  20. @jsteffan:fedora.im (1)