16:00:26 <adamw> #startmeeting F39-blocker-review
16:00:26 <zodbot> Meeting started Mon Oct 16 16:00:26 2023 UTC.
16:00:26 <zodbot> This meeting is logged and archived in a public location.
16:00:26 <zodbot> The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:00:26 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:26 <zodbot> The meeting name has been set to 'f39-blocker-review'
16:00:27 <adamw> #meetingname F39-blocker-review
16:00:27 <zodbot> The meeting name has been set to 'f39-blocker-review'
16:00:27 <adamw> #topic Roll Call
16:00:31 <adamw> ahoyhoyhoy folks
16:00:32 <Son_Goku> .hello ngompa
16:00:33 <zodbot> Son_Goku: ngompa 'Neal Gompa' <ngompa13@gmail.com>
16:00:33 <lruzicka> .hello lruzicka
16:00:35 <Son_Goku> aloha!
16:00:35 <neil> .hi
16:00:36 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
16:00:36 <frantisekz> .hello2
16:00:38 <rishi> .hello2 rishi
16:00:39 <zodbot> neil: neil 'Neil Hanlon' <neil@shrug.pw>
16:00:42 <zodbot> frantisekz: frantisekz 'František Zatloukal' <fzatlouk@redhat.com>
16:00:42 <thebeanogamer> .hello thebeanogamer
16:00:44 <neil> mornin' folks - afternoon, others
16:00:44 <zodbot> rishi: rishi 'Debarshi Ray' <debarshir@redhat.com>
16:00:47 <zodbot> thebeanogamer: thebeanogamer 'Daniel Milnes' <daniel@daniel-milnes.uk>
16:00:48 * lruzicka has only 30 minutes, so please let's hurry
16:01:05 * thebeanogamer has some hurtful things to say about the Raspberry Pi 4
16:01:19 <nielsenb> .hello
16:01:19 <zodbot> nielsenb: (hello <an alias, 1 argument>) -- Alias for "hellomynameis $1".
16:01:23 <nielsenb> .hello2
16:01:24 <zodbot> nielsenb: nielsenb 'Brandon Nielsen' <nielsenb@jetfuse.net>
16:01:26 <nielsenb> Derp
16:01:37 <nielsenb> I'll cover my Pi 4's ears
16:02:07 <Son_Goku> my Pis need to hear it, so I'm fine with that :P
16:02:16 <thebeanogamer> Could you cover them with a real time clock?
16:02:38 <nielsenb> Sure, how do you propose it be powered?
16:02:39 <thebeanogamer> Haven't even had time to try that new boot issue, that's my fun project for this evening...
16:02:45 <adamw> let's do nothing for thirty minutes then we can get started after lruzicka leaves
16:03:03 <adamw> #chair nielsenb son_goku
16:03:03 <zodbot> Current chairs: adamw nielsenb son_goku
16:03:08 <thebeanogamer> @nielsenb I'm British, so it will be powered by hash language
16:03:08 <lruzicka> haha, you know how to make someone happy for sure, adamw
16:03:12 * kparal is here
16:03:16 <adamw> impending boilerplate alert!
16:03:19 <adamw> #topic Introduction
16:03:19 <adamw> Why are we here?
16:03:19 <adamw> #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:03:19 <adamw> #info We'll be following the process outlined at:
16:03:19 <adamw> #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
16:03:20 <adamw> #info The bugs up for review today are available at:
16:03:22 <adamw> #link http://qa.fedoraproject.org/blockerbugs/current
16:03:24 <adamw> #info The criteria for release blocking bugs can be found at:
16:03:26 <adamw> #link https://fedoraproject.org/wiki/Basic_Release_Criteria
16:03:30 <adamw> #link https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria
16:03:32 <adamw> #link https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria
16:03:39 <adamw> #info for Final, we have:
16:03:40 <adamw> #info 1 Proposed Blockers
16:03:40 <adamw> #info 5 Accepted Blockers
16:03:44 <coremodule> .hello2
16:03:45 <zodbot> coremodule: coremodule 'Geoffrey Marr' <gmarr@redhat.com>
16:03:45 <adamw> #info 1 Accepted Previous Release Blockers
16:03:45 <adamw> #info 2 Proposed Freeze Exceptions
16:03:45 <adamw> #info 7 Accepted Freeze Exceptions
16:03:57 * coremodule willing to act as secretary.
16:03:59 <adamw> thanks!
16:04:03 <adamw> #info coremodule will secretarialize
16:04:49 <Son_Goku> previous release blocker?
16:04:53 <adamw> the upgrade one
16:04:55 <Son_Goku> ah
16:05:00 <adamw> seems like that one would likely need to be addressed in 38, not 39
16:05:26 <Son_Goku> is that the one for fedora-appstream-metadata?
16:05:36 <Son_Goku> so that discover upgrades are enabled?
16:05:43 <adamw> no
16:05:47 <adamw> the one where upgrades on pi 4 are broken
16:05:51 <Son_Goku> ah that one
16:06:22 <adamw> alrighty, let's get into it
16:06:27 <adamw> #topic Proposed Final blockers
16:06:44 <adamw> #topic (2244305) Fedora Server 39 does not boot on Raspberry Pi 4 (RPi4) from microSD card slot
16:06:44 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2244305
16:06:44 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1411
16:06:44 <adamw> #info Proposed Blocker, uboot-tools, NEW
16:06:55 <geraldosimiao> .hello geraldosimiao
16:06:56 <zodbot> geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' <geraldo.simiao.kutz@gmail.com>
16:07:07 <adamw> we...really don't have much here yet. it's only just been filed/proposed. i thought it was likely a dupe of 2241252 but it seems possibly not
16:07:17 <adamw> would really help if more folks can test on pi 4, i guess
16:07:21 <adamw> i don't have one
16:07:29 <Son_Goku> mine are burned out
16:07:34 <Son_Goku> so I don't have any that work anymore
16:07:45 <thebeanogamer> Provided I can find a MicroSD -> USB adapter, I should be able to test this one later today
16:07:53 <thebeanogamer> Will comment my findings on Bugzilla
16:08:21 <kparal> looks like a blocker to me at this moment
16:08:54 <adamw> i mean, as described it clearly is one, yeah
16:09:07 <adamw> i guess we can accept it while investigation continues, we can always change our minds later
16:09:16 <Son_Goku> yup
16:09:18 <frantisekz> yeah, in that case, +1
16:09:22 <Son_Goku> +1 FinalBlocker
16:09:26 <thebeanogamer> +1 FinalBlocker
16:09:26 <coremodule> +1 blocker
16:09:32 <geraldosimiao> +1 FinalBlocker
16:09:33 <nielsenb> FinalBlocker +1
16:09:40 <kparal> +1 fb
16:09:43 <jednorozec> +1 fb
16:11:23 <adamw> proposed #agreed 2244305 - AcceptedBlocker (Final) - this is a relatively new bug and we don't know the details or how (if at all) it's related to 2241252 yet, but as described, it's clearly a violation of "system must boot" on Pi 4, a supported aarch64 platform. we accept it on its face for now and will continue to research
16:11:27 <lruzicka> ack
16:11:36 <nielsenb> ack
16:11:36 <coremodule> ack
16:11:43 <jednorozec> ack
16:11:45 <thebeanogamer> ack
16:11:46 <geraldosimiao> ack
16:11:47 <Son_Goku> ack
16:13:08 <adamw> #agreed 2244305 - AcceptedBlocker (Final) - this is a relatively new bug and we don't know the details or how (if at all) it's related to 2241252 yet, but as described, it's clearly a violation of "system must boot" on Pi 4, a supported aarch64 platform. we accept it on its face for now and will continue to research
16:13:17 <adamw> and that was the only proposed blocker. so, let's go for:
16:13:28 <adamw> #topic Proposed Final freeze exceptions
16:13:35 <adamw> #topic (2242641) kdenlive crashes everytime on launch
16:13:35 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2242641
16:13:35 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1410
16:13:35 <adamw> #info Proposed Freeze Exceptions, kdenlive, VERIFIED
16:13:35 <adamw> #info Ticket vote: FinalFreezeException (+3,0,-0) (+frantisekz, +lruzicka, +thebeanogamer)
16:13:45 <adamw> so this has +3 in the ticket but i still wanted to bring it up here as i'm not clear on the rationale
16:13:56 <adamw> kdenlive is not pre-installed and the bug does not affect the upgrade proces
16:14:01 <adamw> what's the justification for an FE here?
16:14:11 <frantisekz> seen my comment there adamw?
16:14:19 <Son_Goku> qadwaitadecorations is new to F39
16:14:20 <frantisekz> just... to be nicer for our pre-release users
16:14:30 <nielsenb> Isn't there a media spin or something?
16:14:51 <Son_Goku> it's a top level change that is being done by Workstation WG
16:14:56 <Son_Goku> having it broken OOTB is not great
16:15:00 <nielsenb> Jam, I guess it's a lab
16:15:19 <nielsenb> And that's focused on audio
16:15:23 <nielsenb> So ignore me
16:15:26 <Son_Goku> this doesn't affect anything using KDE, just anything that doesn't support SSDs (which is only GNOME)
16:15:48 <lruzicka> but Gnome is quite a big part of the environment
16:15:54 <kparal> in my opinion, pre-release testers are expected to be able to handle this situation (check updates-testing if needed)
16:16:03 <Son_Goku> u-t is disabled by default now
16:16:13 <kparal> so my initial instinct is -1 fe
16:16:25 <lruzicka> Btw. when updates-testing got switched off, I was not even able to install Kdenlive.
16:16:49 <kparal> I know it's disabled now, that doesn't really change the fact that they are expected to be able to enable it if needed :)
16:16:55 <Son_Goku> I am surprised that the broken qadwaitadecorations didn't break FMW
16:17:37 <kparal> but I don't really care, I just view this as non-systemic way and asking for many more FEs in the future, which I don't want to handle
16:17:46 <Son_Goku> but with my Workstation WG hat on, I'd really rather not have a broken qadwaitadecorations module in GA since it's a top line feature for Workstation 39
16:20:20 <lruzicka> it breaks more apps, not just Kdenlive according to the bug.
16:20:26 <Son_Goku> yeah
16:20:33 <Son_Goku> kdenlive was just the first reproducer
16:21:02 <lruzicka> and I believe people might be hitting this, as Kdenlive is a favourite video creating app
16:21:36 <adamw> qadwaitadecorations isn't in the KDE live either, though. just checked.
16:21:48 <adamw> so i'm still not actually seeing the concrete benefit of pushing this through freeze, really
16:22:20 <adamw> as kparal said, there has to be a limit to how far we stretch the 'make things easier for people upgrading early' justification. we have release dates for a reason. logically speaking, that justification can apply to literally any bug fix update.
16:22:49 <Son_Goku> adamw: it's in the Workstation live
16:22:55 <adamw> oh. duh.
16:23:27 <Son_Goku> only GNOME is affected as nobody else needs a replacement for server-side decorations
16:23:30 <adamw> ehhh. i guess i could reluctantly give it a +1 then...
16:23:47 <nielsenb> Is anything actually broken in the Live?
16:24:37 <adamw> theoretically, i guess, you can run something qt-based...somehow...without doing an update...i dunno
16:24:56 <nielsenb> I realize the library is broken in the global sense, but if no application is broken, just get the 0 day update while you're installing your Qt apps
16:25:29 <adamw> would it affect qt apps in flatpaks? meh. on the whole i want to be -1 just to try and regain some sense of control over the FE flood, like kparal. :P
16:25:33 <nielsenb> FinalFE -1
16:25:41 <nielsenb> Mostly on the principle of the thing
16:25:55 <Son_Goku> adamw: that is very easy to do
16:26:19 <adamw> what is?
16:26:28 <Son_Goku> get something qt based without doing an update
16:26:28 <kparal> if we can identify a use case for Live, it makes sense to take it in
16:26:57 <kparal> my asssumption was that only kdenlive is affected
16:26:59 <Son_Goku> nothing makes you do an update when you install a Qt-based app from software
16:27:10 <Son_Goku> kparal: no, kdenlive was the first discovered one
16:27:23 <Son_Goku> it's a general problem in qadwaitadecorations
16:27:54 <adamw> yeah, the bug report mentions that other apps crashed too
16:27:57 <adamw> at least by implication
16:28:13 <adamw> you could, i guess, install an affected app on the workstation live to use live for whatever reason
16:28:22 <adamw> i think i'm arguing myself into +1 here, heh
16:28:28 <Son_Goku> without the fix, any qt app will crash if you change color schemes
16:28:36 <Son_Goku> eg switch from dark to light or back
16:28:40 <kparal> I'm fine with +1 with this justification
16:29:01 <Son_Goku> and some apps will just crash at launch (like kdenlive)
16:29:35 <adamw> okay, fine
16:29:50 <nielsenb> Feels super edge case-y, but I guess if nothing but a rebuild is really needed...
16:29:50 <Son_Goku> FinalFE +1
16:29:54 <nielsenb> FinalFE +1
16:30:22 <adamw> proposed #agreed 2242641 - AcceptedFreezeException (Final) - this is accepted on the basis you can plausibly trigger it trying to use any Qt app on Workstation live environment or before performing an update after first install
16:30:30 <lruzicka> ack
16:30:33 <Son_Goku> ack
16:30:34 <thebeanogamer> ack
16:30:35 <jednorozec> ack
16:30:37 <nielsenb> ack
16:30:48 <geraldosimiao> ack
16:31:02 <adamw> #agreed 2242641 - AcceptedFreezeException (Final) - this is accepted on the basis you can plausibly trigger it trying to use any Qt app on Workstation live environment or before performing an update after first install
16:31:42 <adamw> #topic (2244503) Fixes for various regressions related to i18n/l10n regression, missing Recommends, and typos
16:31:42 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2244503
16:31:42 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1413
16:31:42 <adamw> #info Proposed Freeze Exceptions, fedora-toolbox, NEW
16:31:57 <adamw> +1, i guess. we ought to have the release day container fixed
16:32:05 * rishi waves
16:32:09 <jednorozec> yeah this one is +1
16:32:18 <nielsenb> FinalFE +1
16:32:39 <Son_Goku> FinalFE +1
16:32:43 <thebeanogamer> FinalFE +1
16:33:08 <rishi> My apologies, I wanted to submit this earlier, but it took a while to validate everything.  :/
16:33:17 <geraldosimiao> FinalFE +1
16:33:24 <lruzicka> FinalFE +1
16:33:47 <thebeanogamer> > ks file has an obvious typo where the %end and %post markers went missing
16:33:54 <thebeanogamer> Is there a reason we're not running ksvalidator on those in CI?
16:34:21 <Son_Goku> it needs to be wired up
16:34:21 <adamw> proposed #agreed 2244503 - AcceptedFreezeException (Final) - these are obviously issues we want fixed for the Final toolbx image
16:34:21 <frantisekz> FinalFE +!
16:34:26 <adamw> a) nobody got around to it yet
16:34:35 <frantisekz> +1, damn, adam, did you overflow on my ! ?
16:34:35 <adamw> b) that probably wouldn't catch this? the ks file was still *valid*
16:34:55 <Son_Goku> it definitely didn't when I did that screwup during the livesys-scripts change :)
16:34:57 <adamw> bzzzt bzzzt error error ERROR
16:34:59 <adamw> resetting universe
16:35:26 <rishi> I do have some tests in the pipeline to catch the other problems in future.
16:35:50 <rishi> The Container/Dockerfile version had tests built-into them.  Need to migrate those over at some point.
16:38:37 <lruzicka> Must go, take care.
16:38:43 <adamw> any acks?
16:38:56 <adamw> or nacks, or patches?
16:39:11 <rishi> adamw: Some patches are already posted.
16:39:16 <nielsenb> Oh, it moved so fast I missed it
16:39:17 <rishi> One more is in flight.
16:39:18 <nielsenb> ack
16:39:21 <Son_Goku> ack
16:39:23 <frantisekz> ack
16:39:25 <geraldosimiao> ack
16:39:28 <adamw> rishi: no, patches to the proposed #agreed line.
16:39:47 <rishi> Ok, sorry.
16:40:15 <adamw> #agreed 2244503 - AcceptedFreezeException (Final) - these are obviously issues we want fixed for the Final toolbx image
16:41:13 <adamw> #topic (2244471) No support for $releasever for gpgkey URLs (affects Fedora Asahi Remix image builds)
16:41:13 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2244471
16:41:13 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1412
16:41:13 <adamw> #info Proposed Freeze Exceptions, kiwi, MODIFIED
16:42:03 <adamw> sigh
16:42:06 <adamw> more asahi fun
16:42:17 <adamw> i'm assuming asahi doesn't have a way to override the kiwi version it uses for building images?
16:42:21 <Son_Goku> not yet
16:42:36 <Son_Goku> this was not a case we thought about before 😅
16:43:14 <Son_Goku> we did start making one for the inputs for builds, but we don't have one for the build environment itself yet
16:44:32 <adamw> current stable is 9.25.13
16:44:45 <adamw> there's quite a lot of commits from there to 9.25.16: https://paste.centos.org/view/759d5e68
16:44:49 <adamw> do we use kiwi for anything in core fedora?
16:45:37 <Son_Goku> not yet
16:45:49 <Son_Goku> Fedora Cloud is working on it for F40
16:46:01 <Son_Goku> but for F39, it's just Fedora Asahi Remix
16:46:15 <adamw> erf. well, if it's asahi only i guess it's...fine
16:46:17 <adamw> reluctant +1
16:46:24 <Son_Goku> FinalFE +1
16:46:43 <Son_Goku> fwiw, for Fedora Cloud, it'd be in the Fedora buildsystem environment anyway
16:46:53 <geraldosimiao> FinalFE +1
16:46:56 <Son_Goku> so all the normal tools we have for build environment overrides are already possible
16:47:00 <frantisekz> FinalFE +1
16:47:09 <nielsenb> FinalFE +1
16:47:36 <jednorozec> also reluctant +1
16:47:53 <adamw> proposed #agreed 2244471 - AcceptedFreezeException (Final) - this is accepted as it will help Asahi builds and cannot break anything in Fedora proper as we don't use kiwi for anything there yet
16:47:57 <Son_Goku> ack
16:48:08 <frantisekz> ack
16:48:11 <thebeanogamer> ack
16:48:12 <jednorozec> ack
16:48:13 <nielsenb> ack
16:48:29 <geraldosimiao> ack
16:48:39 <adamw> #agreed 2244471 - AcceptedFreezeException (Final) - this is accepted as it will help Asahi builds and cannot break anything in Fedora proper as we don't use kiwi for anything there yet
16:48:55 <adamw> #info that's all the proposals
16:49:01 <Son_Goku> that was quick
16:49:10 <adamw> yup
16:49:13 <Son_Goku> no overlap with the fedora-kde meeting today :D
16:49:17 <frantisekz> quick? let's got to F40!
16:49:18 <frantisekz> :D
16:49:18 <adamw> #topic Accepted Final blocker review
16:49:19 <Son_Goku> does that mean we're doing a good job(tm)?
16:49:25 <adamw> let's do a quick update on the accepted blockers
16:49:32 <adamw> it at least means people are doing a good job of voting!
16:49:43 <adamw> #topic (2243034) Fedora 39: Server boot aarch64 image exceeds maximum size
16:49:43 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2243034
16:49:43 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1396
16:49:43 <adamw> #info Accepted Blocker, distribution, ASSIGNED
16:49:58 <adamw> #info we're probably just going to wind up bumping the max size here to at least 1G, so the problem will go away
16:50:06 <adamw> anything else to note on this one?
16:50:58 <Son_Goku> nah
16:50:59 <nielsenb> Some day firmware size will become untenable, but I don't know what else we do
16:51:33 <adamw> complain! i'm good at that
16:51:35 <Son_Goku> we're going to have to do what openSUSE does and split it up and use modaliases to install them properly, but that's a big refactor
16:51:38 <geraldosimiao> yeah, nowadays everyone can get at least a 8 GB pendrive
16:51:41 <adamw> #topic (2241274) initial-setup text fails on hardware
16:51:42 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2241274
16:51:42 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1353
16:51:42 <adamw> #info Accepted Blocker, initial-setup, ON_QA
16:51:50 <Son_Goku> ugh
16:51:53 <adamw> Son_Goku: that does nothing about the installer images, anyway. they have to have all the firmware.
16:51:59 <Son_Goku> oh fair
16:52:05 <adamw> i don't normally bring up ON_QA bugs, but just wanted to note this needs karma
16:52:17 <adamw> anyone who at least can do an install that triggers initial-setup, which is mostly ARM installs...
16:52:18 <coremodule> I'll add mine shortly
16:52:37 <adamw> #info this needs testing and karma from anyone who can do an install that brings up initial-setup
16:53:42 <adamw> #topic (2241632) Netinstall ISO renders a black screen when using kickstart install (bare metal and VM)
16:53:43 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2241632
16:53:43 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1354
16:53:43 <adamw> #info Accepted Blocker, mutter, ASSIGNED
16:53:59 <adamw> #info we are just waiting on desktop team to address this one, it's pretty precisely triaged
16:54:00 <Son_Goku> still no fix yet?
16:54:14 <Son_Goku> I saw an MR associated with the upstream gnome bug...
16:54:53 <Son_Goku> oh that's just gitlab linking the MR that broke it
16:54:55 <Son_Goku> nvm
16:54:57 <adamw> the related MR is the one that broke it. yes
16:55:13 <Son_Goku> have we poked jadahl or fnmueller about it?
16:56:14 <adamw> jadahl has commented on the ticket
16:56:19 <adamw> https://gitlab.gnome.org/GNOME/mutter/-/issues/3089#note_1868812
16:56:41 <Son_Goku> that doesn't really count as a comment
16:56:55 <Son_Goku> in my book
16:57:07 <adamw> it demonstrates that he's aware of it, though.
16:57:11 <Son_Goku> fair
16:58:24 <adamw> i'm asking about it in the workstation channel
16:58:39 <adamw> 2113005 we are planning to waive, of course
16:58:47 <adamw> #topic (2241252) Fedora-Workstation-39_Beta-1.1 boots to a black screen on Raspberry Pi 4
16:58:47 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2241252
16:58:47 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1352
16:58:47 <adamw> #info Accepted Blocker, uboot-tools, ASSIGNED
16:58:53 <Son_Goku> le sigh
16:58:56 <adamw> #info again we're waiting on devs here. pbrobinson says he's making progress on it
16:59:30 <Son_Goku> oh fyi, the other rpi boot bug, there might be a fix in the fedora-asahi uboot
16:59:40 <Son_Goku> since we fixed a huge chunk of bugs around usb in uboot
17:00:31 <adamw> yes, that's mentioned in a comment.
17:00:40 <Son_Goku> oh good
17:01:50 <adamw> #topic Open floor
17:02:14 <adamw> one note: it looks like FESCo is gonna declare https://bugzilla.redhat.com/show_bug.cgi?id=2243068 a blocker in https://pagure.io/fesco/issue/3083
17:02:30 <coremodule> I have something
17:02:32 <adamw> that shouldn't cause any major issues since there's already a proposed fix, just noting it
17:02:36 <adamw> go ahead, coremodule
17:02:59 <coremodule> .bug 2244305
17:03:01 <zodbot> coremodule: 2244305 – Fedora Server 39 does not boot on Raspberry Pi 4 (RPi4) from microSD card slot - https://bugzilla.redhat.com/2244305
17:03:27 <coremodule> in reference to the above, I tested this issue on Fedora-Server-39-20231016 and Fedora-Server-39-20231010 during the meeting and had no issues at all...
17:03:43 <coremodule> On an RPi4 with an sd boot
17:04:54 <frantisekz> could it be board HW revision depndent?
17:05:07 <coremodule> I have seen issues with this in the past when an SD write goes wrong
17:06:12 <coremodule> frantisekz, sure, I guess it could be.
17:06:15 <adamw> pbrobinson says he sees it 'sometimes'
17:06:28 <adamw> oh, wait, that's the other one. confusion!
17:06:34 <coremodule> that said, we don't have the bandwidth to test all the different hw revs if that *is* what's causing it.
17:06:47 <adamw> on the whole i'm kinda inclined to leave this up to pbrobinson, since he clearly thinks there is a bug there and is bisecting it...
17:06:47 <coremodule> just wanted to share, I have tested this twice, no problems.
17:06:55 <hricky> Since I reported this, can I help here?
17:06:55 <nielsenb> I'll hopefully get a chance to try later today
17:07:13 <nielsenb> But I have $DAY_JOB and $HOME_LIFE stuff on the calendar too
17:07:21 <frantisekz> I'll give it a shot tomorrow, I think we have two different revs in the office, lruzicka, did you leave the rPI Desktop there too?
17:07:33 <adamw> peter said "I'm seeing this problem on occasion, it's causing me issues bisecting the screen problem, I *think* it's fixed in the upstream 2023.10 GA release."
17:08:02 <frantisekz> and I guess backporting the GA now is too big and too late?
17:08:14 <frantisekz> we have rc3 I think, which is two tags before the GA
17:08:39 <adamw> dunno
17:08:52 <adamw> i would just be happy with any kind of fix at this point
17:09:10 <frantisekz> I'll try to test the ga the different revs tomorrow
17:10:32 <adamw> thanks
17:10:36 <frantisekz> okey, need to run now, thanks for the mtg!
17:10:38 <adamw> more data would definitely be helpful i guess
17:10:48 <adamw> i assume all revs run into the *other* bug if you don't use nomodeset?
17:11:34 <coremodule> yeah, from what I
17:11:38 <coremodule> 've seen anyway
17:12:46 <adamw> rgr
17:13:04 <adamw> alrighty, i guess we're done here...
17:14:04 <adamw> thanks for coming, everybody
17:14:16 <adamw> #endmeeting