16:03:01 #startmeeting F32-blocker-review 16:03:01 Meeting started Mon Mar 16 16:03:01 2020 UTC. 16:03:01 This meeting is logged and archived in a public location. 16:03:01 The chair is adamw. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:03:01 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:03:01 The meeting name has been set to 'f32-blocker-review' 16:03:01 #meetingname F32-blocker-review 16:03:01 The meeting name has been set to 'f32-blocker-review' 16:03:01 #topic Roll Call 16:03:06 .hello2 16:03:07 bcotton: bcotton 'Ben Cotton' 16:03:12 .hello2 16:03:14 morning folks, who's around for blocker fun 16:03:14 lruzicka: lruzicka 'Lukáš Růžička' 16:03:20 .hello2 16:03:21 coremodule: coremodule 'Geoffrey Marr' 16:03:29 .hello2 16:03:30 frantisekz: frantisekz 'František Zatloukal' 16:03:33 Ready for secretary duty. 16:03:35 .hello2 16:03:36 * pwhalen is here 16:03:36 kalev: kalev 'Kalev Lember' 16:04:00 .hello2 16:04:01 kparal: kparal 'Kamil Páral' 16:04:15 .hello jbwillia 16:04:18 Southern_Gentlem: jbwillia 'Ben Williams' 16:06:47 wow, good turnout 16:07:00 it's almost like more people are staying home than normal! 16:07:13 #chair pwhalen kalev 16:07:13 Current chairs: adamw kalev pwhalen 16:07:19 boiler plate alert 16:07:20 #topic Introduction 16:07:21 Why are we here? 16:07:21 #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:07:22 #info We'll be following the process outlined at: 16:07:22 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:07:24 #info The bugs up for review today are available at: 16:07:25 #link http://qa.fedoraproject.org/blockerbugs/current 16:07:27 #info The criteria for release blocking bugs can be found at: 16:07:29 #link https://fedoraproject.org/wiki/Basic_Release_Criteria 16:07:33 #link https://fedoraproject.org/wiki/Fedora_32_Beta_Release_Criteria 16:07:35 #link https://fedoraproject.org/wiki/Fedora_32_Final_Release_Criteria 16:08:15 #info coremodule will secretarialize 16:08:44 #info for Beta, we have: 16:08:44 #info 2 Accepted Previous Release Blockers 16:08:55 #info for Final, we have: 16:08:55 #info 4 Proposed Blockers 16:08:56 #info 1 Accepted Blockers 16:09:10 #topic Beta previous release blockers 16:09:13 just want to check in on these first 16:09:26 #topic (1767351) Cannot upgrade to Fedora 32: Modules blocking the upgrade path 16:09:26 #link https://bugzilla.redhat.com/show_bug.cgi?id=1767351 16:09:26 #info Accepted Previous Release Blocker, dnf-plugins-extras, ON_QA 16:09:47 for F31 the fix is karma'ed and pushed stable 16:10:09 for F30, it's built and kparal has confirmed the fix, but it needs more karma: https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c 16:10:20 it'd be great if more folks could test F30->F32 upgrades with that update in place and karma it 16:10:59 #info F31 fix is stable, F30 fix still needs more karma - we need folks to test F30 to F32 upgrades with https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c installed and provide karma so it can be released today 16:12:00 I wonder if we should try to change supported fedora lifecycles. almost nobody seems to be using F30 at this point 16:12:02 #topic (1804564) Cannot upgrade to Fedora 32: Modules blocking the upgrade path 16:12:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=1804564 16:12:03 #info Accepted Previous Release Blocker, PackageKit, ON_QA 16:12:39 kalev: i dunno what the numbers are on that. it could also be that they're just more passive users, less likely to post update feedback. 16:12:46 * kalev nods. 16:12:58 we do tend to get *negative* feedback when the -2 release breaks 16:13:02 there are definitely users 16:13:03 yeah, i think it's more likely that "almost no active fedora contributors seem to be using F30" 16:13:11 dunno how many will be doing upgrades to f32 beta from it, but hey 16:13:21 we've made it super easy to do in place upgrades to newer fedoras (and gnome-software is nagging about it a lot) so I'd assume it's made a lot of people upgrade early 16:13:33 yeah, for workstation the numbers might skew to n-1 as well 16:13:40 probably a lot of n-2 users are running servers 16:14:01 ah yes, that sounds likely 16:14:10 so, status on this one is exactly the same, it's the same fix 16:14:34 (well, different code, but all the fixes for both issues are in the same update at this point) 16:14:42 #info F31 fix is stable, F30 fix still needs more karma - we need folks to test F30 to F32 upgrades with https://bodhi.fedoraproject.org/updates/FEDORA-2020-02ee4b1a1c installed and provide karma so it can be released today (yes, same status as the other bug) 16:15:05 any other notes on these paired issues or shall we go on to Final? 16:15:09 adamw, I have set up a Fedora 30 VM and I am going to try that upgrade 16:15:15 lruzicka: thanks! 16:15:19 i also plan to test it today 16:17:00 if you really really want it go out before the beta announcement tomorrow then it probably needs a special push from releng late tonight 16:17:16 yeah, i'll bug mboddu for that 16:17:20 once we have karma 16:17:24 great :) 16:17:43 ok, moving on to... 16:17:47 #topic Proposed Final blockers 16:18:04 #topic (1811382) anaconda failed to login to the iscsi target if attachment takes longer than ~15 seconds 16:18:04 #link https://bugzilla.redhat.com/show_bug.cgi?id=1811382 16:18:04 #info Proposed Blocker, anaconda, ASSIGNED 16:18:19 so, this is a conditional violation, the condition is right there in the bug topic :) 16:18:25 oh just one last thing on the previous topic -- if anyone is testing gnome-software updates, can you leave karma to the F30 gnome-software build in updates-testing as well, please? 16:18:36 kalev: aha, thanks, will do 16:18:39 thanks 16:19:12 i'm probably -1 on this, on balance, it works if your network connection is decent, and you're probably not going to have a good experience with iSCSI in general if the connection is this slow... 16:19:16 +1 FE though 16:19:17 adamw, all DEs or just work and kde 16:19:36 on the upgrade tests 16:19:40 adamw: If you can give karma to it (again since the builds got changed), I can push it once the current push is done 16:19:44 Southern_Gentlem: just testing dnf system-upgrade and GNOME Software should suffice 16:19:53 testing 16:19:58 Southern_Gentlem: dnf is the recommended upgrade tool for all but Workstation, i don't know if KDE tools can actually do an upgrade 16:20:10 mboddu: yes, that's the plan 16:20:55 -1 blocker, +1 FE 16:21:13 -1 Blocker, +1 FE 16:21:33 -1 blocker, +1 FE 16:21:53 adamw, is there a decent failure message for the problem? 16:22:05 lruzicka: no, that's one of the things anaconda team says they will fix 16:22:09 that's certainly FE worthy for me 16:22:17 see comment #21 (most recent comment) 16:22:21 isn't it blockworthy? 16:22:41 mmm, is it? 16:22:59 this isn't new behaviour, f31 is the same, see #c18 16:23:14 well, maybe your connection only temporarily sucks so you cannot expect a failure and you still get it 16:23:21 we noticed this now because lili's network got slower, it seems - see https://bugzilla.redhat.com/show_bug.cgi?id=1811382#c18 16:23:50 see, you do not expect a slow network if you normally do not have it, so it can be really frustrating if you hit it 16:24:51 -1 blocker, +1 FE 16:25:36 but it looks that folks are not convinced, so at least +1 FE 16:27:59 proposed #agreed 1811382 - RejectedBlocker AcceptedFreezeException (Final) - this is rejected as it's only a conditional violation in an unusual condition (in the normal case, iSCSI works fine) and it's not new behaviour (F31 behaves the same). Accepted as an FE issue as it cannot be addressed with an update and a fix or mitigation (better error message for e.g.) would be welcome for the Final release 16:28:38 ack 16:29:18 ack 16:29:27 ack 16:29:32 #agreed 1811382 - RejectedBlocker AcceptedFreezeException (Final) - this is rejected as it's only a conditional violation in an unusual condition (in the normal case, iSCSI works fine) and it's not new behaviour (F31 behaves the same). Accepted as an FE issue as it cannot be addressed with an update and a fix or mitigation (better error message for e.g.) would be welcome for the Final release 16:29:39 #topic (1812896) No help is shown in Anaconda during installation. 16:29:39 #link https://bugzilla.redhat.com/show_bug.cgi?id=1812896 16:29:39 #info Proposed Blocker, anaconda, POST 16:29:44 pretty straightforward +1 16:29:50 criteria say this has to work, it doesn't work :) 16:29:55 +1 16:29:58 i keep meaning to automate this test, though... 16:30:09 Hello? 16:30:16 Am I too late? 16:30:27 I'm Lailah 16:30:31 hi 16:30:40 no, we're about halfway in 16:30:47 Oh, okay. 16:30:49 we're on https://bugzilla.redhat.com/show_bug.cgi?id=1812896 right now 16:30:57 .fas lailah 16:30:58 regenbogen: lailah 'Sylvia Sánchez' 16:31:12 +1 blocker 16:31:14 +1 Blocker 16:31:28 +1 Blocker 16:31:35 +1 Blocker 16:32:19 +1 block 16:32:37 +1 blocker 16:33:11 proposed #agreed 1812896 - AcceptedBlocker (Final) - accepted as a clear violation of Final criterion "Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated." 16:33:36 yeah, my blocker 16:33:44 ack 16:33:48 ack 16:33:51 ack 16:33:54 ack 16:34:13 ack 16:34:34 ack 16:34:48 #agreed 1812896 - AcceptedBlocker (Final) - accepted as a clear violation of Final criterion "Any element in the installer interface(s) which is clearly intended to display 'help' text must do so correctly when activated." 16:35:01 #topic (1803996) systemd-ask-password-console.service: Unit configuration has fatal error 16:35:01 #link https://bugzilla.redhat.com/show_bug.cgi?id=1803996 16:35:01 #info Proposed Blocker, dracut, MODIFIED 16:36:15 so, we considered this last week 16:36:28 https://bugzilla.redhat.com/show_bug.cgi?id=1803996#c7 has the decision, we punted it 16:36:37 it doesn't seem like any new information was added, and cmurf isn't around 16:36:43 maybe punt again... 16:37:15 lruzicka: you said "my blocker" and I imagined you hugging your blocker and running away with it so nobody else can have it. 16:37:51 regenbogen, :D it was a blocker I proposed. :D 16:38:27 lruzicka: I know :-D 16:38:40 should we needinfo cmurf or someone? 16:39:25 given the fact we are out of freeze with some time left, we can punt again 16:39:26 regenbogen: i give all of mine names 16:39:28 :P 16:39:39 sweet :D 16:39:45 bcotton: my secret plan is that we push an update and it's all fine! 16:39:54 but yeah, probably 16:39:57 i like that plan! 16:40:05 and maybe check anaconda team is okay with dracut 050 now we solved the anaconda bug (we hope) 16:40:52 proposed #agreed 1803996 - punt (delay decision) again - we punted this last week for more information on various things, and we don't have all that info yet. we will check in with cmurf on the details of the bug, and anaconda team on whether they're happy with the current dracut 050 update as it stands 16:41:00 adamw: :-P 16:41:19 adamw: I like that plan too! 16:41:23 ack 16:41:28 ack 16:41:33 ack 16:41:40 ack 16:42:15 ack 16:42:22 ack 16:42:36 ack 16:42:47 #agreed 1803996 - punt (delay decision) again - we punted this last week for more information on various things, and we don't have all that info yet. we will check in with cmurf on the details of the bug, and anaconda team on whether they're happy with the current dracut 050 update as it stands 16:42:57 #topic (1812293) F32 background not used on desktop by default (but is used on login screen, lock screen) 16:42:57 #link https://bugzilla.redhat.com/show_bug.cgi?id=1812293 16:42:57 #info Proposed Blocker, kde-settings, NEW 16:43:32 so, the Final criterion is "The proposed final Fedora artwork must be included and used as the background on release-blocking desktops." 16:43:38 so, this didn't block Beta, but clearly blocks Final. 16:43:58 KDE Settings seems to have more weird errors in the last times. From what I experienced. 16:44:18 adamw: I agree. 16:44:38 +1 final 16:44:46 +1 blocker 16:44:48 +1 blocker 16:44:59 regenbogen: it turns out the problem is upstream moved the setting, basically 16:45:05 we now need to set it in some plasma subpackage or other 16:45:08 +1 blocker 16:45:16 +1 Blocker 16:45:19 adamw: Oh. Okay. 16:45:25 rdieter figured it out before beta, but the problem is that plasma in dist-git had been bumped ahead of the version that's in stable 16:45:37 so in order to just fix the background setting, we would have had to pull a whole new Plasma version through the freeze 16:45:41 that didn't make sense, so we didn't do it 16:46:04 So... now... what do we do? 16:46:06 once beta freeze is lifted, we'll get an update with the new Plasma version and the background fix 16:46:25 Oh, okay. So this is already fixed? 16:46:41 well, we have a plan to fix it, let's say :) 16:46:55 proposed #agreed 1812293 - AcceptedBlocker (Final) - accepted as a clear violation of "The proposed final Fedora artwork must be included and used as the background on release-blocking desktops." 16:47:06 ack 16:47:35 ack 16:47:43 ack 16:47:48 #agreed 1812293 - AcceptedBlocker (Final) - accepted as a clear violation of "The proposed final Fedora artwork must be included and used as the background on release-blocking desktops." 16:48:00 and that is actually everything on my list! 16:48:21 #topic Open floor 16:48:30 that's all we have on the list for today - any other concerns etc.? 16:49:08 Uhm... I'd like to comment a couple of issues I've been experiencing with KDE 16:49:28 go right ahead 16:49:28 I didn't file a bug yet, because I'm not sure _where_ to file it. 16:50:03 * kparal notes a fairly visible one: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d 16:50:09 With the last updates, it seems like a lot of KDE apps misbehave. 16:50:46 For example, I close a programme. *I closed it* But it immediately returns a "this app crashed, want to report?" 16:51:12 It didn't crash. I closed/quit the programme. 16:51:31 That's one. 16:51:36 it's likely crashing during shutdown 16:51:49 What shutdown? 16:51:52 app shutdown 16:52:01 when you exit the app, it will run through some code to close down in an orderly way 16:52:04 likely something there is crashing 16:52:13 we had a similar bug in hexchat for years - every time you quit, the app crashed 16:52:13 Uhm. Okay. 16:52:24 what's the other issue? 16:52:45 It's baffling because it's not just one app, it's different ones. 16:52:54 need to run, thanks for the meeting adamw & others! 16:53:00 it's probably a common library 16:53:01 thanks frantisekz 16:53:03 right 16:53:11 Have a nice day frantisekz! 16:53:13 it's likely gonna be some bit of plasma 16:53:18 good luck guessing *which* bit, though :) 16:53:31 what i would suggest is joining #fedora-kde and asking rdieter, when he is around 16:53:32 Yeah... Should I file it? 16:53:35 he should be able to help pin point it 16:53:37 It's very annoying. 16:53:45 Oh, okay, I will 16:53:47 if you can't catch him, just file a bug and pick some plasma component, like plasma-desktop 16:54:00 There's another issue, but with System Settings. 16:54:07 it probably won't be the right one, but it doesn't matter too much - as long as you pick a plasma component the right people should see the bug and be able to help figure out the correct component 16:54:13 adamw: Okay, I will. 16:54:26 thanks! 16:54:31 what's the system settings issue? 16:54:46 Well, there are several. 16:55:20 One is that for some reason deleting a theme or colour scheme doesn't delete the file. 16:55:49 In the best of cases, the offending item goes away from the list but the file is still there, in the folder, hidden from view. 16:56:05 In the worst of cases, it just doesn't work and deletes nothing. 16:56:27 You click on delete but the item remains there. 16:56:46 hum, okay. i'm not sure what the expected behaviour is there, to be honest 16:57:01 it may depend whether it's a system-supplied or user-installed theme/scheme 16:57:09 Just delete the theme/icon/whatever ? 16:57:19 No, they're user themes. 16:57:32 The system wide themes have their buttons greyed out. 16:57:39 It's just not an option. 16:57:40 hum, okay 16:57:44 then yeah, sounds like deleting should work 16:57:52 i *think* the component for that should be plasma-systemsettings 16:57:52 It was working! 16:57:55 Until now. 16:57:58 Oh, okay. 16:58:08 There's another one in System Settings. 16:58:15 fire away! 16:59:14 Let's say you choose a theme in SDDM. Apply changes, introduce your password, everything is fine. Reboot, fine. Go to settings for whatever reasons, look into SDDM, the selection goes back to the default theme. 16:59:16 Why? 16:59:19 No idea. 16:59:37 But if you don't choose again, it will sit on default and show the default next time. 17:00:25 It happens sometimes with other items, but SDDM is the most outstanding example. 17:00:45 Not sure if this is Settings fault or SDDM or a combination, or something else. 17:01:02 i don't know either! 17:01:05 but i'd definitely report it 17:01:07 those all sound like bugs 17:01:46 Okay, I'll report them to System Settings and see what happens. And drop a line in #fedora-kde 17:01:54 Maybe Dieter can help me. 17:01:58 regenbogen, please report it, some of it may even be your blockers :D 17:02:20 And I'll hug them and run away with them so no one else can have them! 17:02:22 :-D 17:02:28 regenbogen: it's 'rex' - he's called 'rex dieter' :) 17:02:34 Ah. 17:02:37 Thanks adamw 17:02:40 yeah, when he's around he should be able to help you investigate 17:02:53 thanks for testing :) 17:03:00 My pleasure! 17:03:01 okay, anything else, folks? 17:03:19 Oh, yes, I just recalled another weirdness. 17:03:28 go ahead 17:03:30 Nothing important. But it's weird. 17:03:40 Well, I have Latte as a dock. 17:04:15 And it always happens that the first time I use it, right after logging in, the screen or the desktop seems to have a hiccup. 17:04:37 It shows a very ugly horizontal bar, a few centimetres under the dock. 17:04:52 It goes away when I click on whatever icon I wanted on Latte. 17:05:04 But it's awkward. It shouldn't be there. 17:05:47 Oh, I forgot to mention, I have the Latte dock hanging from the top, not on the bottom. 17:06:02 That's why the artifact happens below the dock. 17:06:03 huh. sorry, don't know about that either =) 17:06:08 sounds like it's specific to this dock, though 17:06:16 so file a bug against it? is it packaged or did you install it a different way? 17:06:19 Yeah, maybe Plasma in general? 17:06:30 Yeah, Latte is in repos. 17:06:43 What you install from KDE store are the extensions for it. 17:06:47 If you want any. 17:07:06 okay. i don't run KDE much, so i just don't have a lot of helpful knowledge here :) rdieter and kevin_kofler are the KDE folks 17:07:09 adamw: I installed it from repos. 17:07:16 so, i'd file a bug against hte package for it, then 17:07:24 Okay. I'll ping them. 17:07:28 thanks! 17:07:40 Sure, anytime! 17:08:17 Oh, there's another one but it's also KDE related, so I'll keep it for next time. 17:08:29 :-) 17:09:14 hehe 17:09:14 okay 17:09:17 thanks, everyone 17:09:32 #endmeeting