16:01:26 #startmeeting F33-blocker-review 16:01:26 Meeting started Mon Sep 28 16:01:26 2020 UTC. 16:01:26 This meeting is logged and archived in a public location. 16:01:26 The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:26 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:01:26 The meeting name has been set to 'f33-blocker-review' 16:01:27 #meetingname F33-blocker-review 16:01:27 The meeting name has been set to 'f33-blocker-review' 16:01:29 #topic Roll Call 16:01:34 anyone here today? 16:01:46 nope 16:01:50 dang! 16:02:02 .hello2 good morning bcotton, if we reach quorum, I'll secretarialize. 16:02:04 coremodule: coremodule 'Geoffrey Marr' 16:02:09 coremodule: ack! 16:02:14 #chair coremodule 16:02:14 Current chairs: bcotton_ coremodule 16:04:14 .hello2 16:04:15 nb: nb 'Nick Bebout' 16:04:37 welcome nb 16:04:40 that makes four of us 16:05:18 technically quorum is 3, so i guess that works 16:05:31 wfm! 16:05:52 but we'll be free with the punt today i think, in cases where there's not overwhelming agreement 16:06:08 #topic Introduction 16:06:09 Why are we here? 16:06:11 #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. 16:06:12 #info We'll be following the process outlined at: 16:06:14 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:06:16 #info The bugs up for review today are available at: 16:06:17 #link http://qa.fedoraproject.org/blockerbugs/current 16:06:19 #info The criteria for release blocking bugs can be found at: 16:06:20 #link https://fedoraproject.org/wiki/Basic_Release_Criteria 16:06:22 #link https://fedoraproject.org/wiki/Fedora_33_Beta_Release_Criteria 16:06:23 #link https://fedoraproject.org/wiki/Fedora_33_Final_Release_Criteria 16:06:34 #info 5 Proposed Blockers 16:06:35 #info 4 Accepted Blockers 16:06:37 #info 0 Accepted 0-day Blockers 16:06:38 #info 0 Accepted Previous Release Blockers 16:06:40 #info 1 Proposed Freeze Exceptions 16:06:41 #info 0 Accepted Freeze Exceptions 16:06:49 #topic (1881234) Resizing doesn't work right in anaconda blivet-gui mode: "AttributeError: 'BlivetStorageHandler' object has no attribute '_resizable_filesystems'" 16:06:51 #link https://bugzilla.redhat.com/show_bug.cgi?id=1881234 16:06:52 #link https://pagure.io/fedora-qa/blocker-review/issue/122 16:06:54 #info Proposed Blocker, blivet-gui, POST 16:07:06 #info In the ticket: FinalBlocker (+2, 0, -0) 16:07:40 ill refrain from voting here since I voted on pagure, unless you want to double up and call it a day bcotton_ 16:07:55 kparal nominated it under the "Any installer mechanism for resizing storage volumes must correctly attempt the requested operation." criterion 16:08:13 coremodule: just /nick to someone else for another vote :-) 16:08:21 hahahaha 16:08:29 +1 16:08:32 +1 16:08:44 coremodule++ 16:09:23 proposed #agreed 1881234 - AcceptedBlocker (Final) - Violates the final criterion "Any installer mechanism for resizing storage volumes must correctly attempt the requested operation." 16:09:32 ack 16:09:35 ack 16:09:50 #agreed 1881234 - AcceptedBlocker (Final) - Violates the final criterion "Any installer mechanism for resizing storage volumes must correctly attempt the requested operation." 16:10:07 #topic (1868141) Select Printer Driver hangs 16:10:08 #link https://bugzilla.redhat.com/show_bug.cgi?id=1868141 16:10:10 #link https://pagure.io/fedora-qa/blocker-review/issue/124 16:10:11 #info Proposed Blocker, gnome-control-center, ON_QA 16:10:25 #info In the ticket: FinalBlocker (+7, 0, -0) 16:10:30 that seems pretty strong 16:10:45 agreed 16:11:07 * pwhalen joins 16:11:20 welcome pwhalen 16:11:36 good morning pwhalen 16:11:55 +1 16:11:56 proposed #agreed 1868141 - AcceptedBlocker (Final) - Violates the criterion "Printing must work in release-blocking desktops on at least one printer available to those performing validation testing." 16:11:59 ack 16:12:01 ack 16:12:04 +1, ack 16:12:10 #agreed 1868141 - AcceptedBlocker (Final) - Violates the criterion "Printing must work in release-blocking desktops on at least one printer available to those performing validation testing." 16:12:27 #topic (1882718) Can't login if the session is locked 16:12:29 #link https://bugzilla.redhat.com/show_bug.cgi?id=1882718 16:12:30 #link https://pagure.io/fedora-qa/blocker-review/issue/131 16:12:32 #info Proposed Blocker, gnome-remote-desktop, NEW 16:12:46 ooh, no votes in the ticket yet. guess i have to read now 16:13:00 I am +1 final blocker to this, but would be okay with punting for more info/testing 16:13:51 yeah, i'm not sure if we intend VNC to be included in the "default panel must work" criterion 16:14:20 woops, sorry i'm late 16:14:30 oh look, workstation wg shows up just on time ;-) 16:14:39 haha 16:14:44 i am not the wg 16:14:53 you represent the wg, though :-) 16:15:00 certainly more than the rest of us do 16:15:03 that's a stretch 16:15:09 :) 16:15:17 i have no backscroll btw 16:15:31 so we're talking about https://bugzilla.redhat.com/show_bug.cgi?id=1882718 16:15:42 coremodule is +1 FB but okay with punting 16:15:57 and i'm not entirely sure VNC was intended to be included in the cited criterion 16:16:02 does this only happen in vnc? 16:16:27 that's the implication, although it's not said explicitly 16:17:22 yeah i want more information 16:17:35 so there's possibly two passwords (?) 16:18:01 proposed #agreed 1882718 - Defer decision (punt) - We want confirmation that 1. this bug only occurs with VNC sessions and 2. That VNC is intended to be covered in the "default panel must function correctly" criterion 16:18:05 the user account password, which also removes the screen unlock 16:18:16 and a VNC password which is a different thing... 16:18:20 cmurf: right 16:18:23 i don't know how they are intended to interact 16:18:55 my gut instinct is, if a user intentionally sets them differently and they lock their screen or the timeout for screen lock happens, then VNC should not work 16:18:59 but then, that's my opinion 16:19:07 i could be 100% wrong 16:19:12 so yeah we need more info 16:19:39 how it's intended to work vs how it does work is more important to figure out 16:20:28 agreed 16:21:20 yeah from the upstream bug, something is busted regardless 16:21:31 any feelings about my proposed #agreed above? 16:21:39 whoops, missed that 16:21:40 ack 16:21:41 ack 16:21:55 ack 16:22:06 #agreed 1882718 - Defer decision (punt) - We want confirmation that 1. this bug only occurs with VNC sessions and 2. That VNC is intended to be covered in the "default panel must function correctly" criterion 16:22:23 #topic (1882863) gnome-software 3.38.0 does not list all software in Add-ons 16:22:24 #link https://bugzilla.redhat.com/show_bug.cgi?id=1882863 16:22:26 #link https://pagure.io/fedora-qa/blocker-review/issue/127 16:22:27 #info Proposed Blocker, gnome-software, NEW 16:22:45 #info In the ticket: FinalBlocker (+0, 1, -0) 16:23:36 +1 punt for more info, personally 16:23:50 what info, specifically? 16:24:31 is this basic functionality 16:24:39 i think probably it is, i mean 16:24:47 well, I'm not totally convinced this is a gnome-software bug, but don't have all the info to figure out if I'm correct in my assumption there. 16:24:48 i can't install the nvidia driver? 16:24:54 unless i go to cli? 16:25:08 cmurf, yeah, that's what i was trying to do when i hit this. so... i mean, yeah. I see that. 16:25:53 it seeeeeeems like a blocker to me 16:26:17 i'm inclined to block 16:26:26 like if the nvidia driver is broken, sorry about your luck, but we should at least show it if it's available 16:26:29 it seems weird to block on being unable to install proprietary software but that's a detail 16:26:58 it probably happens to other things also 16:27:15 is there an upstream bug for this? 16:27:20 that was my other thought, but if you think it's an appropriate enforcement of the "default functionality" criterion, my vote could be swayed. 16:27:22 i mean i suppose we could punt until we have a better understanding of the cause. if it's just nvidia for some reason, then it may still be a blocker, but that's different if it's an entire repo 16:27:42 or lack of vote 16:28:12 needinfo 16:28:14 punt 16:28:27 +1 punt for more info 16:28:30 but we should be aggressive about it, final freeze in 7 days 16:28:51 cmurf, who would you cc on the bug to get some more info on it? 16:29:14 they're already cc'd 16:29:18 proposed #agreed 1882863 - Defer decision (punt) - It's not clear what the scope of this bug is, so it's hard to make a blocker decision at this time. 16:29:47 cool 16:29:48 ack 16:30:14 ack 16:31:11 ack 16:31:16 #agreed 1882863 - Defer decision (punt) - It's not clear what the scope of this bug is, so it's hard to make a blocker decision at this time. 16:31:38 #topic (1880833) Massive memory leak on AMD cards 16:31:39 #link https://bugzilla.redhat.com/show_bug.cgi?id=1880833 16:31:41 #link https://pagure.io/fedora-qa/blocker-review/issue/116 16:31:43 #info Proposed Blocker, mesa, NEW 16:31:59 #info In the ticket: FinalBlocker (+1, 0, -0) 16:32:54 this seems like a continued punt 16:33:27 ew 16:33:29 agreed, according to pagure its a kernel issue, but no "evidence" as mentioned in the bugzilla report 16:33:34 has this been bisected? 16:34:02 cmurf: if it has, nobody has mentioned it 16:34:07 -1 blocker 16:34:23 kernel bisects are tedious but it's the only way to be sure 16:35:05 this is where i'm headed in comment 4 16:35:17 as soon as it's working in one and not another, kernel bisect is in order 16:36:13 * cmurf has done his fair share of i915 bug bisection 16:36:48 so punt again until someone can conclusively show where the problem is (and the scope of affected hardware)? 16:36:55 yep 16:37:01 +1 punt for info 16:37:09 ack 16:37:17 I was -1. but punt sounds good too 16:37:46 if no one can do a bisect or figure out where the bug is, there's nothing to block on :) 16:37:52 proposed #agreed 1880833 - Defer decision (punt) - We will defer this again until it's clear how wide a range of hardware may be affected and where the bug lies 16:37:59 ack 16:38:16 ack 16:38:17 ack 16:38:24 #agreed 1880833 - Defer decision (punt) - We will defer this again until it's clear how wide a range of hardware may be affected and where the bug lies 16:39:10 so that's the end of the proposed blockers. i propose we call it a day. we still have one more meeting before the freeze begins and i'm not sure there's much to talk about on the accepted blockers 16:39:51 wow that was fast! Ill take it! 16:40:20 bcotton_: no complaints here 16:40:21 we should send a get well card to adamw 16:40:31 * nb wonders what is going on with adamw? 16:40:43 #topic Open floor 16:41:09 #info We'll skip proposed freeze exceptions since we have one more meeting before freeze begins 16:41:12 anything for open floor? 16:41:22 nothing here 16:41:40 cmurf: +1 to that 16:43:18 okay, thanks everyone! 16:43:21 #endmeeting