16:00:06 #startmeeting F39-blocker-review 16:00:06 Meeting started Mon Oct 30 16:00:06 2023 UTC. 16:00:06 This meeting is logged and archived in a public location. 16:00:06 The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 16:00:06 Useful Commands: #action #agreed #halp #info #idea #link #topic. 16:00:06 The meeting name has been set to 'f39-blocker-review' 16:00:06 #meetingname F39-blocker-review 16:00:06 The meeting name has been set to 'f39-blocker-review' 16:00:06 #topic Roll Call 16:00:17 ahoyhoy, folks 16:00:20 .hello thebeanogamer 16:00:22 thebeanogamer: thebeanogamer 'Daniel Milnes' 16:00:23 .hello2 16:00:25 nielsenb: nielsenb 'Brandon Nielsen' 16:00:29 .hi 16:00:30 pboy: pboy 'Peter Boy' 16:00:36 * thebeanogamer regrets opening the BlockerBugs page, as it seems to have doubled 16:00:48 eh? not really 16:01:27 Right, from 0 to 1 proposed blockers is technically undefined 16:01:29 :D 16:02:40 heh 16:02:48 .chair nielsenb pboy 16:02:48 nielsenb pboy is seated in a chair with a nice view of a placid lake, unsuspecting that another chair is about to be slammed into them. 16:03:09 Bot is sassy 16:03:19 I like it 16:03:23 i dunno who wrote that one, heh 16:03:23 .hello geraldosimiso 16:03:25 geraldosimiao: Sorry, but user 'geraldosimiso' does not exist 16:03:30 .hello2 16:03:31 coremodule: coremodule 'Geoffrey Marr' 16:03:32 .hello geraldosimiao 16:03:34 geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' 16:03:51 * coremodule willing to act as secretary. 16:03:53 .hello ngompa 16:03:55 Son_Goku: ngompa 'Neal Gompa' 16:03:58 * kparal is here 16:06:32 hihi 16:06:40 okay, let's get rolling 16:06:50 boilerplate alert 16:06:51 #topic Introduction 16:06:52 Why are we here? 16:06:52 #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:52 #info We'll be following the process outlined at: 16:06:52 #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting 16:06:54 #info The bugs up for review today are available at: 16:06:56 #link http://qa.fedoraproject.org/blockerbugs/current 16:06:58 #info The criteria for release blocking bugs can be found at: 16:07:00 #link https://fedoraproject.org/wiki/Basic_Release_Criteria 16:07:02 #link https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria 16:07:04 #link https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria 16:07:06 #info for Final, we have: 16:07:08 #info 1 Proposed Blockers 16:07:12 #info 5 Accepted Blockers 16:07:14 #info 1 Accepted Previous Release Blockers 16:07:16 #info 3 Proposed Freeze Exceptions 16:07:18 #info 4 Accepted Freeze Exceptions 16:07:20 #info coremodule will secretarialize 16:07:25 *for real* this time right :P 16:07:29 let's get started with: 16:07:34 #topic Proposed Final blocker 16:07:40 #topic (2247033) GNOME crashes after 1 second when trying to record screencast on an AMD GPU 16:07:40 #link https://bugzilla.redhat.com/show_bug.cgi?id=2247033 16:07:40 #link https://pagure.io/fedora-qa/blocker-review/issue/1428 16:07:40 #info Proposed Blocker, gnome-shell, NEW, depends on other bugs 16:07:45 in conclusion, mehhh. 16:08:27 It's technically a default app, doing its primary job 16:09:11 yes yes, for real this time 16:10:10 It's not an app, it has no launcher 16:10:12 .hi 16:10:13 neil: neil 'Neil Hanlon' 16:10:19 g'day folks 16:11:01 the only inconvenient thing here is that it might be useful on a Live image 16:11:08 otherwise an update would be fine 16:11:20 yeah, that's what makes me a bit sad 16:11:46 i think we have kinda stretched the definition of 'app' a bit in the past, to be fair, but... 16:12:07 I don't think we block on this, currently 16:12:12 oh 16:12:15 it *is* an app 16:12:22 "Take a Screenshot" 16:12:25 you can put that in camera mode 16:12:31 heh, you're right 16:12:34 assuming that crashes, then...oof 16:12:38 it's an "app" :D 16:12:54 and from the upstream description, clearly that's actually what lukas was testing 16:13:01 "There is no difference, if cursor is set to enabled or disabled. Also, it crashes for both the entire screen and a selection." 16:13:06 those are options in the app version 16:13:22 yes, he always confuses mutter internal screenshotting and gnome-screenshot 16:13:35 he means mutter 16:13:52 and I confirmed it 16:13:59 refresh the ticket, if you haven't recently 16:16:19 what, the scratch build? 16:16:30 i can have openqa do a live image from that scratch build if you like 16:16:34 or, well, *you* can too, now :P 16:16:45 haha, haven't studied that yet 16:17:11 so...if this was affecting all hardware i'd feel kinda blockery 16:17:17 only on (some?) AMD hardware, not sure... 16:17:23 right 16:17:46 * kparal shrugs 16:18:24 if people voted -1, I wouldn't object 16:19:24 so if nobody has any opinion, I wouldn't block on it, I guess 16:19:56 i'm kinda unsure 16:19:59 it does seem quite bad. 16:20:05 just a minute, call of nature 16:20:09 debate among yourselves! 16:20:21 me and me? 16:20:33 or is here anyone else with a voice too? :) 16:20:41 I'm here 16:20:46 I wish I knew if it was AMD only 16:21:21 I'm unsure it it is a blocker. Installatioopn works. So it is an application bug? 16:21:32 the linked MR also mentions "AMD GPUs" 16:21:46 pboy: yes, https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria#Default_application_functionality 16:22:12 coremodule: what's your opinion? 16:22:35 Ok, if it is a default application 16:23:06 it's integral to mutter, so yes 16:23:13 Sad "it's gonna be a blocker" noises 16:23:36 Do we still have an easy "start an X session" thing in GDM? Maybe that's an easy enough workaround? 16:24:04 I think I agree with it being a blocker, if it's in the default apps and non-functional 16:24:12 We do, but how easy is that to use on live media 16:24:27 That's fair 16:24:40 on Live, you first need to give liveuser a password 16:24:45 then you can select a session 16:25:03 it's a workaround, not completely simple, but it is 16:25:30 I'm not a fan of having to give a workaround to someone who is probably screenshotting to help troubleshooting 16:25:53 thebeanogamer +1 16:25:58 I've not got much experience with Gnome upstream, is this something they're likely to turnaround quickly? 16:26:31 yeah, can confirm it's showing on my amd hardware. that said, I don't see screencapture, particularly screen capture as video, as being basic functionality 16:26:34 they think it may already be fixed and we just need to backport a patch 16:26:56 coremodule: what, in that case, would you argue *is* the basic functionality of the screen capturing application? :D 16:27:03 in fact, when you search for "screenshot", it comes up as "Take a Screenshot" 16:27:10 (okay, if you want to argue only still screen capture is basic functionality, we can try that) 16:27:11 not "Take a Screecast" 16:27:25 awwww, look at my lil criteria lawyer 16:27:29 they grow up so fast *sniff*\ 16:27:45 I do feel like a lot of GUI issues now included a video 16:28:07 So I really don't like the idea of a tool used to improve bug reporting being broken 16:28:25 adamw: ;-D 16:28:34 Yes, and Video is not so exotic nowadays. 16:30:20 I'm -1 blocker, +1 commonbugs, fix it after release. This isn't worth blocking on in my opinion. I can talk with Mario at AMD (the Framework guy) and see if he can look into it for a fix after release. 16:30:21 I'm going to go ahead and say it 16:30:25 FinalBlocker +1 16:31:03 i'm at least finalfe +1 16:31:09 It's a default app, useful for issue reporting, and likely to be used by anyone going "look at this cool thing F39 can do, oh wait, it's broken" 16:31:09 i'm really on the fence about blocking... 16:31:14 sure, I'm +1FE 16:31:50 FE is nice and everything, but we really need to decide the blocker today :) 16:31:56 FinalBlocker +1, but if we find it's the last blocker I'm open to reconsidering 16:32:48 FinalBlocker +1 16:32:53 does the whole gnome session crash or what? 16:33:06 If the name of the app showed as "Take a Screen*capture*" or something like that then I'd probably be +1 in principle that it *is* a violation of the basic app functionality. But being as it shows as "Take a Screenshot" but includes screenrecording ability, I would say the basic functionality is there. It *does* take a screenshot. The screenrecording is extra. 16:33:12 i.e. is this a "desktop crashes" issue or a "program no work" issue 16:33:43 aleasto, no, gnome continues running 16:33:44 Have we checked all the i18n? Is the name the equivalent of "screen shot" in all languages? 16:34:07 coremodule: ok, cause the title of the rhbz is "GNOME crashes after [...]" 16:34:28 If I type "screen capture" into search, it's the app it gives me 16:34:39 yeah, specifically it's gjs that crashes 16:34:42 the session doesn't crash, just the video capture fails 16:34:54 nielsenb, yeah, but what is the name of the app shown there? 16:36:13 If totem can't play audio files, do we not block because it's called "Video"? 16:36:43 maybe? 16:37:07 Do we not block if Cheese can't give me a cracker, because it's called Cheese? :D 16:38:07 Interesting, seaching "Take a Screenshot" doesn't give me "Take a Screenshot" 16:39:17 you're right, that is interesting... 16:39:51 No, bad 16:39:55 Stop finding more bugs 16:40:21 Not so easy, unfortunately 16:42:12 if we can just keep arguing about this for another half hour or so, https://openqa.stg.fedoraproject.org/tests/3302117#live will complete and kparal can test it 16:42:35 Did you pay for the whole hour? 16:44:14 Well, do we have a decision? 16:44:29 * nirik arrives late, reads up. 16:44:56 FB +1 16:45:07 Considering the number of other FEs to consider adamw, that might not be the worst idea 16:46:33 * nirik is now tempted to try this here and see if it crashes in rawhide. 16:47:04 Gooed idea :-) 16:47:08 nirik: no worry, the session doesn't crash 16:47:15 nielsenb: my time in this channel is sponsored by SlapChop(TM) 16:47:26 ah, I misread, only the "app" crashes? 16:47:28 on an unrelated note, do you find chopping vegetables a tiresome kitchen chore?! 16:48:02 SlapChop, apply directly to the forehead, SlapChop, apply directly to the forehead, SlapChop, apply directly to the forehead 16:48:15 adamw: I wouldn't wait for the ISO. I'll need to download it, which will take time, and my family will be back any time, which means I can't guarantee I'll be still online 16:48:21 okay 16:48:28 well, we're at +4 / -1 I think? 16:48:30 anyhow, -1 FinalBlocker... 16:48:40 well, so much for that. :P 16:48:44 :D 16:48:45 ha. 16:48:48 .fire nirik 16:48:48 adamw fires nirik 16:48:59 * nirik heads to the beach 16:49:16 * nirik looks at the critera 16:49:33 nirik: https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria#Default_application_functionality 16:49:54 it's an app (we found out), because it has an app icon. But it's conditional - AMD only. 16:50:10 Are we sure it's AMD only? Or has only AMD been tested? 16:50:12 and coremodule claims that video capture is not default functionality, screenshots are 16:50:19 and also only the screencast part? 16:50:29 only screencasts crash 16:50:32 s/default functionality/basic functionality 16:50:36 and only on AMD, it seems 16:50:45 adamw: thanks 16:51:02 the MR speak about AMD only as well 16:51:10 and it works just fine on my Intel gpu 16:51:10 it's only the screencast part that causes the crash 16:51:18 works fine here on intel. 16:51:25 I just tested on ARM and it works as expected. dont have an intel machine to test on 16:51:37 Okay, I'll accept that as AMD only 16:52:58 You know what, given that it's vendor specific, I think I'm willing to change my vote 16:53:19 FinalBlocker -1 16:53:43 there's likely a fair pile of amd systems out there... 16:54:06 Yes 16:54:24 I don't necessarily love that I changed my vote 16:54:45 vote regret! 16:54:48 Steam hardware survey says 70% of Linux users on AMD 16:55:02 (Though Steamdeck is skewing that) 16:55:22 What percentage use "Take a Screenshot" to do screencasts? 16:55:46 well, the case we're worried about is people running into a problem when running live and trying to record it 16:56:17 nielsenb: Let me start a few mailing list arguments about telementry and I can tell you 16:56:18 Indeed! It's a kind of support tool, isn't it? 16:56:20 yeah, I suppose thats a fair thing to do... 16:56:32 ohh, think on the headlines: Fedora 39 workstation live won't work for you if you're a AMD user... ;D 16:56:41 I'm gearing up to test on my AMD system, which will determine how I feel when I go to sleep tonight 16:56:48 ant whanna take a screencast. 16:56:55 *and 16:57:12 ant can do it for yo :-) 16:57:40 ;D 16:58:05 * nirik definitely sees it here on rawhide. 16:58:28 Just for the books, I would like to discuss another one 16:58:32 nirik: can you test with https://koji.fedoraproject.org/koji/taskinfo?taskID=108326940 ? 16:58:40 it's an f39 build but, er, might work on rawhide if you bodge it in... 16:58:46 i think the sonames are still the same... 16:58:55 let me see. 17:00:45 cute, downgrading to that causes dnf5 to upgrade glibc. ;) 17:00:55 but let me logout and back and see... 17:02:21 huhhh. 17:02:46 still here :-) 17:03:25 nirik suffers the screen cast crash, propably 17:04:28 I have 3 AMD systems here, and one thumbdrive 17:04:47 First one is booting now, am I gonna go 3 for 3 and regret everything? 17:05:05 still fails for me here with that mutter 17:05:57 Media check passed, lets gooo 17:05:58 Might be a rawhide / 39 mismatch tho 17:06:05 Oct 30 09:47:54 logain.scrye.com gnome-shell[2943]: JS ERROR: Error: Expected type string for argument 'path' but got type undefined 17:07:00 hum, or was that the previous one. 17:07:29 yeah, i guess that might be an incompatibility thing 17:07:44 Works on this system 17:07:44 * kparal is partly afk 17:07:52 But it's not radeonsi, just old school radeon 17:07:53 although, hmm, rawhide's mutter isn't that different 17:08:19 The bug report was for a 580, so I'll skip that system for now 17:09:19 well, we seem a bit stuck on this 17:09:24 oh, I am dumb. 17:09:26 it works 17:09:28 oh yay 17:09:40 can we at least say this is accepted as an FE? 17:09:44 then we can pull the fix in and make it go away 17:09:55 Works on this system with a 6700XT 17:09:59 So, #notallAMD 17:10:03 +1 FE 17:10:05 FE +1 17:10:05 nielsenb: when you say "works", you mean the bug doesn't happen? 17:10:09 FreezeException +1 17:10:13 adamw: yes 17:10:29 Takes screencasts just fine 17:10:33 Unless I'm missing something 17:11:08 proposed #agreed 2247033 - punt (delay decision) on blocker, AcceptedFreezeException (Final) - we couldn't come to a clear decision on whether this is a blocker, given it only affects certain hardware. But it is accepted as an FE and nirik says the proposed fix seems to work, so we should be able to fix it for the next compose 17:11:37 agreed 17:11:56 ack 17:12:01 ack 17:12:15 ack 17:12:24 ack 17:13:10 ack 17:13:34 #agreed 2247033 - punt (delay decision) on blocker, AcceptedFreezeException (Final) - we couldn't come to a clear decision on whether this is a blocker, given it only affects certain hardware. But it is accepted as an FE and nirik says the proposed fix seems to work, so we should be able to fix it for the next compose 17:13:42 Works in this system with an RX580 17:13:44 ack 17:13:45 *shrug* 17:13:46 OK, moving on to 17:13:51 #topic Proposed Final freeze exceptions 17:14:10 Wink wink I wojuld like to discuss another bug! 17:14:15 It may be only super new amd cpus? not sure. 17:14:31 But only the first time 17:14:35 That's interesting 17:14:38 nielsenb: maybe newer hardware is accepted? both those boards are kinda old 17:14:40 anyhoo 17:14:52 #topic (2246800) Having Kitty Installed Prevents Upgrade to Fedora 39 17:14:52 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246800 17:14:52 #link https://pagure.io/fedora-qa/blocker-review/issue/1426 17:14:52 #info Proposed Freeze Exceptions, kitty, NEW 17:14:53 #info Ticket vote: FinalFreezeException (+0,0,-2) (-nielsenb, -lruzicka) 17:15:29 we normally give these FEs 17:15:39 i'd be +1 17:15:43 fixing upgrade issues is usually a good idea 17:15:48 It's so late though 17:16:00 It would be fixed if it's a 0 day too tho right? 17:16:37 but sure, it seems pretty harmless to just take it... +1 FE 17:16:37 it'd be fixed on release day 17:17:05 or whenever we did the 0-day push 17:17:08 +1 FE 17:17:09 with an FE it's fixed sooner 17:17:36 in general i like to fix upgrade issues to discourage people upgrading with allowerasing and stuff 17:17:43 but, eh. it's not super important either way 17:18:04 live image is available for testing the screencapture bug now 17:18:10 https://openqa.stg.fedoraproject.org/tests/3302117/asset/iso/03302117-Fedora-Workstation-Live-x86_64-108326940.iso 17:18:55 Fine 17:19:00 FinalFE +1 17:19:04 Since I'm all about changing votes today 17:19:09 heh 17:19:49 proposed #agreed 2246800 - AcceptedFreezeException (Final) - this is accepted as an FE to prevent problems for early upgraders, it's not an important package so can't really break anything important 17:19:58 ack 17:20:08 ack 17:20:26 ack 17:20:35 ack 17:20:44 ack 17:20:46 #agreed 2246800 - AcceptedFreezeException (Final) - this is accepted as an FE to prevent problems for early upgraders, it's not an important package so can't really break anything important 17:20:47 I can grow and change 17:20:56 #topic (2225688) Macaulay2: FTBFS in Fedora rawhide/f39 17:20:56 #link https://bugzilla.redhat.com/show_bug.cgi?id=2225688 17:20:56 #link https://pagure.io/fedora-qa/blocker-review/issue/1425 17:20:56 #info Proposed Freeze Exceptions, Macaulay2, NEW 17:20:56 #info Ticket vote: FinalFreezeException (+1,0,-2) (+zbyszek, -nielsenb, -lruzicka) 17:21:23 ehhh, not really buying this one much 17:21:24 I'm sorta thinking about changing my vote on this one too, since it feels very self contained 17:21:48 If we vote this one down, I think FESCo might push it through anyway 17:21:54 you're already not supposed to change interfaces at this point, fesco gave an exception which presumably applies to a 0-day. it's probably not important as touching it shouldn't break anything, but eh. 17:22:10 fesco didn't vote it as a freeze exception, just an updates policy exception. 17:22:34 although, ticket says fesco wanted an FE... 17:22:54 https://pagure.io/fesco/issue/3088#comment-880845 17:22:59 "The advantage is that there will not be an older version of this forever available for dnf to consider for resolving dependencies." 17:23:00 ehhh 17:23:02 i guess 17:23:09 reluctant +1 17:24:18 FinalFE +1 17:24:32 anyone else? 17:24:35 +3/-1 currently 17:24:36 FE +1 17:24:37 FE+1 17:24:38 yeah sure +1 FE 17:24:52 +1 FE 17:26:02 +1 FE 17:26:17 proposed #agreed 2225688 - AcceptedFreezeException (Final) - this is accepted on churchyard's justification: avoid the old interface provides being permanently available in the frozen release repo 17:26:30 ack 17:26:32 ack 17:26:58 ack 17:27:00 ack 17:27:02 ack 17:27:38 #agreed 2225688 - AcceptedFreezeException (Final) - this is accepted on churchyard's justification: avoid the old interface provides being permanently available in the frozen release repo 17:27:54 oh, the next one has +5 already and i forgot to process it, my bad 17:28:10 #info 2246428 has sufficient ticket votes to be accepted, we will process it outside the meeting 17:28:16 so, let's move on to 17:28:22 #topic Accepted Blocker status review 17:28:41 #info the config issue that caused 2246385 is fixed, so that should be resolved whenever we create the next RC 17:28:57 yeah, so sorry about that. ;( 17:29:00 #info 2113005 is on track to be waived 17:29:06 #topic (2246410) Failed media check immediately disappears on bare metal, shows a black screen instead 17:29:06 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246410 17:29:06 #link https://pagure.io/fedora-qa/blocker-review/issue/1423 17:29:06 #info Accepted Blocker, dracut, NEW 17:29:09 uggggh, this one 17:29:29 i have been fighting it all weekend, and only just realized there may actually be a second codepath that non-live images hit 17:29:39 i've got another test build running 17:30:06 I also spent thu+fri on it, just to realize all my testing was wrong :-) 17:30:15 it's very annoying to test 17:30:20 no shortcuts, really 17:30:33 i suppose if i could figure out how to unpack and edit the iso and then repack it, but ehhh 17:32:44 hopefully we get something workable soon 17:32:54 #info we kinda understand what's going on here, but it's proving to be a pain to fix 17:33:10 #info i'm hoping to have some kind of fix/workaround available for testing today 17:34:41 adamw: regarding the screencasting fix, the new mutter works fine 17:35:04 kparal: cool. can you grab the live image and confirm with that too? 17:35:18 then we'll get an official update done... 17:35:34 #topic (2241252) U-Boot fails to load kernel provided DTs from /boot (RPi4 boots to blank screen) 17:35:34 #link https://bugzilla.redhat.com/show_bug.cgi?id=2241252 17:35:34 #link https://pagure.io/fedora-qa/blocker-review/issue/1352 17:35:34 #info Accepted Blocker, uboot-tools, VERIFIED 17:35:37 adamw: I did, used that live image 17:35:41 ah great 17:35:53 so, I think we are kinda good here? did folks get to do any more ARM testing over the weekend? 17:36:03 I did 17:36:23 Fedora Sercer is unusable on SBCs 17:36:48 PRobinson asked me to create a new bug: https://bugzilla.redhat.com/show_bug.cgi?id=2246871 to be a release blocker 17:36:51 pboy: I replied to your bug, that should be fixed. 17:37:23 * kparal has to leave, bye everyone 17:37:43 Well, itested the latest version of arm-image-insttalller 17:38:07 w/o success so far 17:38:28 pboy: you have to actually nominate it as a blocker for it to appear at this meeting 17:38:33 it's just a regular bug right now 17:38:37 we have lots of those... 17:39:41 it seems pwhalen cannot reproduce your problem? your output does kinda read a lot like you're still using the old version of the script 17:40:20 OK, no I used 3.9.2 17:40:45 The image is missing a VG, so yu can't do anything with it. 17:41:58 pboy: its not missing, just not renamed in your case. 17:42:16 You might need a reboot, but if you could add the logs that would help me 17:42:19 No, it is missing. Try to expand the VG. 17:42:46 Yes, I'll do the --debug asap :-) 17:43:40 And the problem is the same, wheether you rename or not. 17:45:06 pwhalen: did you test the image your wrote actually boots and works ok? 17:45:34 yes 17:46:40 * nirik has no pi's here. ;( 17:46:59 pboy: if you could reboot and post the output of `rpm -q arm-image-installer` and then running it with `--debug`, that'd help clarify the situation, i guess... 17:47:59 adamw yes, I#ll do that later today. I have to run arm.-installer, that takes some time ... 17:48:26 so, as far as the graphics bug goes, we seem to be OK? 17:48:38 coremodule: pwhalen: have we tested on a few different devices? 17:48:53 You mean the nomodeset? 17:49:08 if coremodule could test with server and the new version that would be great 17:49:14 no, i mean the bug we are actually discussing 17:49:15 pwhalen, can do 17:49:17 :D 17:49:18 adamw, which bug? 17:49:19 thx! 17:49:19 oh 17:49:38 I didn't do any testing over the weekend 17:49:59 All these bugs are kind of interwoven. 17:50:14 I tested RC1.2 on RPi4 2GB, RPi4 4GB, and RPi400 4GB with no issues found. 17:51:34 it'd be good if we could test some not-Pis 17:51:36 I tested RC 1.2 with 3.9.2 on RPi4, RockPro, LibreComp Roc-pc und Rock-pi 4 17:51:40 since the 'fix' was a big rollback 17:51:48 adamw, that would be good, wouldn't it? :D 17:52:22 I think the Brno guys tested PineBook 17:52:27 actually, I know they did 17:53:56 okay 17:54:17 #info testing of various Pis and non-Pis over the weekend hasn't turned up any graphics issues, so this is looking good 17:54:43 #topic (2244305) Fedora Server 39 does not boot on Raspberry Pi 4 (RPi4) from microSD card slot 17:54:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=2244305 17:54:43 #link https://pagure.io/fedora-qa/blocker-review/issue/1411 17:54:43 #info Accepted Blocker, uboot-tools, VERIFIED 17:55:12 so, this one feels a bit messy. hector reckons u-boot has all kinds of bugs in this area and the rollback probably didn't "fix" it, but in practice, this seems to be uncommon enough not to lose any sleep over 17:55:40 there's also now a pile of patches submitted upstream for resolving a chunk of these 17:55:42 Just, that Fedora Server is unsable. 17:55:59 unusable 17:57:05 Do we have a new image post 1.2? 17:57:11 not yet. 17:57:41 but nothing will change in that image that will have anything to do with the issue you are seeing. but i really think you probably were somehow using an old version of the script, or something, 17:57:48 well, we have nightlies 17:58:06 Son_Goku: i don't think we want to go pulling those in at that point. 17:58:19 probably not 17:58:31 but I really don't like that we now have the epoch on uboot 17:58:39 :( 17:58:49 Unfortunately, I ddidn't use old versions. 17:59:40 I think, we can clarify this 18:00:16 nighlies won't have the older/epoched uboot yet right? 18:00:35 and discuss all the details on the ticket 18:00:54 nirik: I would really rather fix the newer version and not ship the epoched uboot 18:01:01 because we still don't have a policy for erasing epocs 18:01:03 because we still don't have a policy for erasing epochs 18:01:18 it's just an integer. ;) 18:01:23 yeah, it's just a number. 18:01:32 nirik: not yet, no 18:01:35 a very annoying one 18:01:48 but i don't think pbrobinson is a big fan of bumping back to 2023.10 and trying to patch it six ways from sunday just to avoid an epoch 18:01:52 pbrobinson: around, by any chance? 18:05:09 seems he didn't epoch rawhide yet. 18:05:36 anyhow, hopefully we can get all the arm stuff tested in a new rc 18:06:16 * Son_Goku grumbles that we should just change the policy to make Epochs less permanent 18:06:46 #info this area is a bit messy, but we believe the issue happens rarely enough with rc1.2 to consider it addressed 18:06:52 #topic Proposed blocker redux 18:06:56 so, for the sake of completeness 18:07:03 #topic (2246871) F39 Server Edition for aarch64 SBC disk image is not bootable 18:07:03 #link https://bugzilla.redhat.com/show_bug.cgi?id=2246871 18:07:03 #link https://pagure.io/fedora-qa/blocker-review/issue/1429 18:07:03 #info Proposed Blocker, arm-image-installer, NEW 18:07:09 this is pboy's issue, which pwhalen cannot reproduce 18:07:22 i am in favor of punting till we can sort out whether there is actually a bug here 18:07:27 (and if so, if it's in the image) 18:07:28 +1 18:07:39 yeah, need more testing 18:07:40 +1 18:09:32 +1 18:10:11 proposed #agreed 2246871 - punt (delay decision) - it is unclear if there is actually a bug here (and if so, if it is in the image or the script) as pboy and pwhalen do not get the same results. decision is delayed until the situation can be clarified 18:10:41 could it be a revision diff between the two hardwares? 18:10:42 ack -- I am testing this now, will report in-channel and in-bug 18:10:44 ack 18:10:49 but anyhow, hopefully it can get sorted. 18:10:53 ack 18:11:23 nirik: i don't think so. this is just in the process of writing an image to a usb stick, I think. 18:11:33 ok 18:11:36 ack 18:11:44 It may be in the image, because vscan nor vgchange can fint a VG 18:14:04 #agreed 2246871 - punt (delay decision) - it is unclear if there is actually a bug here (and if so, if it is in the image or the script) as pboy and pwhalen do not get the same results. decision is delayed until the situation can be clarified 18:14:06 #topic Open floor 18:14:09 ...and I think that's everything 18:14:13 well not quite 18:14:26 i'm going to keep cranking on the media check bug, then hopefully get a candidate built sometime today with that and the screencast fix 18:14:29 yes? 18:14:30 it's not on the roster yet, but fesco was alerted to this over the weekend: https://pagure.io/fesco/issue/3089 18:14:59 redhat-lsb is still broken in Fedora too 18:15:54 mehhhh 18:15:57 with my fesco hat on, I'm planning to propose that fesco recommends this package be removed from f39 18:17:08 technically f39 GA isn't totally locked down yet, so this is our last chance to do so 18:17:18 * nirik isn't sure how this would affect the release. I guess if you want it not in final it would need to be removed before we do a rc. 18:17:19 well, you can go ahead and try 18:17:26 i'll check where you're up to before doing a candidate 18:17:32 but i'm not going to hold the candidate for a package retirement 18:17:33 👍 18:17:36 that's fine 18:17:41 I just wanted to give the headsup 18:18:14 So, one thing I wanted to bring up somewhere (but doesn't have to be here): 18:18:46 we still have a number of things failing in nightlys (and probibly would in a rc). Not sure if we can address any of them, but we should perhaps look. 18:19:47 ie, kionite aarch64 failed due to size, etc. 18:19:55 anyhow, that can be out of this meeting. :) 18:20:04 okay 18:20:09 we can chat before the candidate 18:20:59 anything else? 18:23:23 okay then, thanks folks 18:23:25 #endmeeting