2024-04-15 16:00:01 <@adamwill:fedora.im> !startmeeting F40-blocker-review
2024-04-15 16:00:02 <@meetbot:fedora.im> Meeting started at 2024-04-15 16:00:01 UTC
2024-04-15 16:00:02 <@meetbot:fedora.im> The Meeting name is 'F40-blocker-review'
2024-04-15 16:00:04 <@adamwill:fedora.im> !topic Roll Call
2024-04-15 16:00:07 <@adamwill:fedora.im> !topic Introduction
2024-04-15 16:00:14 <@adamwill:fedora.im> !topic Roll Call
2024-04-15 16:00:18 <@adamwill:fedora.im> oops, went too far. :D
2024-04-15 16:00:24 <@adamwill:fedora.im> morning folks, who's here for blocker review fun?
2024-04-15 16:00:26 <@tablepc:matrix.org> !Hi
2024-04-15 16:00:31 <@salimma:fedora.im> back to roll call?
2024-04-15 16:00:40 <@nhanlon:beeper.com> !hi
2024-04-15 16:00:41 <@davdunc:fedora.im> .hi
2024-04-15 16:00:42 <@zodbot:fedora.im> Neil Hanlon (neil) - he / him / his
2024-04-15 16:00:43 <@salimma:fedora.im> adamw: you should probably change the topic back first
2024-04-15 16:01:02 <@tablepc:matrix.org> I've tried Screencast several times with different app's and it works.
2024-04-15 16:01:20 <@salimma:fedora.im> !topic Roll Call
2024-04-15 16:01:23 <@salimma:fedora.im> !hi
2024-04-15 16:01:24 <@zodbot:fedora.im> Michel Lind (salimma) - he / him / his
2024-04-15 16:01:32 <@nielsenb:fedora.im> !hi
2024-04-15 16:01:35 <@zodbot:fedora.im> Brandon Nielsen (nielsenb)
2024-04-15 16:01:52 <@adamwill:fedora.im> Michel Lind 🎩: i already did it
2024-04-15 16:01:54 <@adamwill:fedora.im> but hey, can't hurt
2024-04-15 16:01:55 <@tablepc:matrix.org> !Hi
2024-04-15 16:02:05 <@tablepc:matrix.org> Do I need to type it agasin
2024-04-15 16:02:11 <@salimma:fedora.im> doh, I'm blind, didn't see the third one == the first one
2024-04-15 16:02:21 <@salimma:fedora.im> I think it's case sensitive
2024-04-15 16:02:35 <@geraldosimiao:matrix.org> !hi
2024-04-15 16:02:37 <@zodbot:fedora.im> Geraldo S. Simião Kutz (geraldosimiao) - he / him / his
2024-04-15 16:02:41 <@salimma:fedora.im> starts with ! now ;) (tripped me up the first few months)
2024-04-15 16:02:54 <@coremodule:fedora.im> !hi
2024-04-15 16:02:55 <@zodbot:fedora.im> Geoffrey Marr (coremodule)
2024-04-15 16:02:56 <@davdunc:fedora.im> hah. 
2024-04-15 16:02:59 <@davdunc:fedora.im> !hi
2024-04-15 16:03:01 <@zodbot:fedora.im> David Duncan (davdunc) - he / him / his
2024-04-15 16:03:12 <@davdunc:fedora.im> Thank you!
2024-04-15 16:03:36 <@tablepc:matrix.org> How  come zodbot doesn't see me?
2024-04-15 16:03:46 <@adamwill:fedora.im> try a lower-case h
2024-04-15 16:03:47 <@adamwill:fedora.im> !hi
2024-04-15 16:03:49 <@zodbot:fedora.im> Adam Williamson (adamwill) - he / him / his
2024-04-15 16:03:57 <@conan_kudo:matrix.org> !hi
2024-04-15 16:03:59 <@zodbot:fedora.im> Neal Gompa (ngompa) - he / him / his
2024-04-15 16:04:03 <@tablepc:matrix.org> !hi
2024-04-15 16:04:05 <@zodbot:fedora.im> No Fedora Accounts users have the @tablepc:matrix.org Matrix Account defined
2024-04-15 16:04:16 <@adamwill:fedora.im> ah, there, you need to tell FAS about your matrix account, i guess
2024-04-15 16:04:20 <@salimma:fedora.im> your matrix account must be listed on accounts.fedoraproject.org
2024-04-15 16:04:47 <@decathorpe:fedora.im> !hi
2024-04-15 16:04:49 <@zodbot:fedora.im> Fabio Valentini (decathorpe) - he / him / his
2024-04-15 16:04:52 <@adamwill:fedora.im> hi fabio
2024-04-15 16:04:56 <@adamwill:fedora.im> okey dokey, let's get some boilerplate
2024-04-15 16:05:06 <@adamwill:fedora.im> !topic Introduction
2024-04-15 16:05:10 <@adamwill:fedora.im> Why are we here?
2024-04-15 16:05:13 <@adamwill:fedora.im> !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.
2024-04-15 16:05:16 <@adamwill:fedora.im> !info We'll be following the process outlined at:
2024-04-15 16:05:18 <@adamwill:fedora.im> !link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
2024-04-15 16:05:20 <@adamwill:fedora.im> !info The bugs up for review today are available at:
2024-04-15 16:05:22 <@adamwill:fedora.im> !link http://qa.fedoraproject.org/blockerbugs/current
2024-04-15 16:05:26 <@adamwill:fedora.im> !info The criteria for release blocking bugs can be found at:
2024-04-15 16:05:29 <@adamwill:fedora.im> !link https://fedoraproject.org/wiki/Basic_Release_Criteria
2024-04-15 16:05:31 <@adamwill:fedora.im> !link https://fedoraproject.org/wiki/Fedora_40_Beta_Release_Criteria
2024-04-15 16:05:36 <@adamwill:fedora.im> !link https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria
2024-04-15 16:05:45 <@adamwill:fedora.im> !info for Fedora 40 Final, we have:
2024-04-15 16:05:48 <@adamwill:fedora.im> !info 2 Proposed Blockers
2024-04-15 16:05:51 <@adamwill:fedora.im> !info 1 Accepted Previous Release Blockers
2024-04-15 16:05:53 <@adamwill:fedora.im> !info 4 Proposed Freeze Exceptions
2024-04-15 16:05:56 <@adamwill:fedora.im> !info 8 Accepted Freeze Exceptions
2024-04-15 16:06:00 <@adamwill:fedora.im> who wants to secretarialize?
2024-04-15 16:06:56 <@coremodule:fedora.im> I'll do it.
2024-04-15 16:07:20 <@adamwill:fedora.im> !info coremodule will secretarialize
2024-04-15 16:07:27 <@adamwill:fedora.im> alrighty, let's get going with
2024-04-15 16:07:30 <@adamwill:fedora.im> !topic Proposed Final blockers
2024-04-15 16:07:36 <@adamwill:fedora.im> !topic (2275099) Recording the screencast does not work properly.
2024-04-15 16:07:39 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2275099
2024-04-15 16:07:39 <@zodbot:fedora.im> neil gave a cookie to coremodule. They now have 69 cookies, 2 of which were obtained in the Fedora 39 release cycle
2024-04-15 16:07:42 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1596
2024-04-15 16:07:44 <@adamwill:fedora.im> !info Proposed Blocker, gnome-shell, NEW
2024-04-15 16:07:46 <@adamwill:fedora.im> !info Ticket vote: FinalBlocker (+1,0,-0) (+lruzicka)
2024-04-15 16:07:53 <@adamwill:fedora.im> so, this seems to be a developing situation...
2024-04-15 16:08:02 <@adamwill:fedora.im> i've tried four times on two systems and haven't reproduced yet, how's everyone else doing?
2024-04-15 16:09:01 <@nielsenb:fedora.im> I can't make it happen.
2024-04-15 16:09:14 <@nielsenb:fedora.im> I guess I haven't tried a VM.
2024-04-15 16:09:17 <@geraldosimiao:matrix.org> At rc 1.13 I have the same results Lukas have. At 1.14 it crashed 
2024-04-15 16:09:18 <@salimma:fedora.im> this is the one that tablepc said worked for them too I think
2024-04-15 16:09:20 <@tablepc:matrix.org> I've tried Screencast several times with different applications and it always works.
2024-04-15 16:09:49 <@frantisekz:fedora.im> !hi
2024-04-15 16:09:50 <@zodbot:fedora.im> František Zatloukal (frantisekz)
2024-04-15 16:11:01 <@adamwill:fedora.im> hum, the only major difference between 1.13 and 1.14 here should be mesa and the kernel...
2024-04-15 16:11:56 <@geraldosimiao:matrix.org> So mesa then? 
2024-04-15 16:12:02 <@frantisekz:fedora.im> seems like the affected systems are all vms? 
2024-04-15 16:12:06 <@tablepc:matrix.org> Same test machine I always test on bare metal
2024-04-15 16:12:11 <@frantisekz:fedora.im> if i am not missing anything 
2024-04-15 16:13:52 <@adamwill:fedora.im> not sure about lruzicka's initial report
2024-04-15 16:14:01 <@frantisekz:fedora.im> @lruzicka 
2024-04-15 16:14:19 <@adamwill:fedora.im> let me try in a VM
2024-04-15 16:14:28 <@salimma:fedora.im> lruzicka: 
2024-04-15 16:15:24 <@adamwill:fedora.im> eh, have to download 1.14 first
2024-04-15 16:15:25 <@nielsenb:fedora.im> My VM is installing, just did another bare metal test with everything updated and it was fine
2024-04-15 16:15:28 <@geraldosimiao:matrix.org> Yeah mine is vm
2024-04-15 16:15:30 <@adamwill:fedora.im> on the whole i'm -1 or punt on this, i think
2024-04-15 16:16:04 <@frantisekz:fedora.im> can we cycle back to this at the end of the meeting maybe? 
2024-04-15 16:16:19 <@frantisekz:fedora.im> we'll have more vm results by then? 
2024-04-15 16:16:27 <@salimma:fedora.im> yeah, this close to the release if there's no clear repro or it only affects a few systems... but right maybe if someone want to test now and report at the end, we should vote then
2024-04-15 16:16:47 <@adamwill:fedora.im> sure...
2024-04-15 16:17:00 <@adamwill:fedora.im> !info we will table this bug for more testing during the meeting and proceed for now
2024-04-15 16:17:06 <@adamwill:fedora.im> !topic (2274830) Reinstate network service for Fedora 40
2024-04-15 16:17:09 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2274830
2024-04-15 16:17:11 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1593
2024-04-15 16:17:14 <@adamwill:fedora.im> !info Proposed Blocker, initscripts, NEW
2024-04-15 16:17:17 <@adamwill:fedora.im> !info Ticket vote: FinalBlocker (+2,0,-0) (+geraldosimiao, +ngompa)
2024-04-15 16:17:19 <@adamwill:fedora.im> no votes!
2024-04-15 16:17:21 <@adamwill:fedora.im> nobody vote.
2024-04-15 16:17:25 <@frantisekz:fedora.im> 😁😁
2024-04-15 16:17:32 <@frantisekz:fedora.im> +fesco
2024-04-15 16:17:41 <@adamwill:fedora.im> !info this bug is proposed as a blocker for FESCo to considering nominating it, it does not qualify as a blocker under the release criteria, so we will not vote on it
2024-04-15 16:17:42 <@nielsenb:fedora.im> He's suppressing our votes! Vote! Vote!
2024-04-15 16:18:01 <@frantisekz:fedora.im> democracy!!! 
2024-04-15 16:18:10 <@adamwill:fedora.im> whew, it's a good thing I asked the Democratic National Committee for this phone number
2024-04-15 16:18:12 <@adamwill:fedora.im> ...i mean uh
2024-04-15 16:18:39 <@nielsenb:fedora.im> What do we want? Suffrage! When do we want it? Not for this bug!
2024-04-15 16:18:47 <@salimma:fedora.im> I know we're not voting for this but... it worries me how we almost did not notice
2024-04-15 16:19:04 <@adamwill:fedora.im> i kinda agree, but otoh, there's just a whole lot of *stuff* in fedora, if you hadn't noticed :P
2024-04-15 16:19:09 <@salimma:fedora.im> adamw: would having a test instance of openqa on the beta release help?
2024-04-15 16:19:34 <@adamwill:fedora.im> openqa already tests the beta
2024-04-15 16:19:37 <@salimma:fedora.im> similar to how my company dogfoods ELN at work so we are not blindsided if some packages disappear
2024-04-15 16:19:38 <@adamwill:fedora.im> and all f40 nightlies
2024-04-15 16:19:41 <@adamwill:fedora.im> and all critical path updates
2024-04-15 16:19:50 <@adamwill:fedora.im> it is not set to fail if a random init.d service disappears
2024-04-15 16:19:53 <@salimma:fedora.im> oh no, I mean, run one instance of openqa itself on beta so you know if one of your dependencies is yanked
2024-04-15 16:19:55 <@tablepc:matrix.org> No opinion on the mmatter
2024-04-15 16:20:00 <@adamwill:fedora.im> heck, network-scripts isn't in a default install, so openqa hasn't seen it for years
2024-04-15 16:20:05 <@adamwill:fedora.im> oh, i see
2024-04-15 16:20:08 <@salimma:fedora.im> yeap
2024-04-15 16:20:25 <@salimma:fedora.im> like "are all the infra we run on fedora installable on the upcoming fedora"
2024-04-15 16:20:33 <@adamwill:fedora.im> i mean, in theory, sure, in practice, i don't really have time
2024-04-15 16:20:46 <@adamwill:fedora.im> openqa is honestly already ahead of the rest of infra, tbh
2024-04-15 16:20:49 <@nielsenb:fedora.im> I feel like it's the kind of thing you would only notice if you had a special need
2024-04-15 16:20:57 <@adamwill:fedora.im> openqa stg is usually one of the first things to go to a new release
2024-04-15 16:20:59 <@nielsenb:fedora.im> And if you have a special need, you probably aren't running prerelease
2024-04-15 16:21:11 <@salimma:fedora.im> adamw: if you point me to the ansible playbooks for deploying openqa maybe I can cook up something
2024-04-15 16:21:35 <@salimma:fedora.im> (also short on time, but this is one of the issues that bugs me so maybe I'll scratch that itch)
2024-04-15 16:21:56 <@adamwill:fedora.im> Michel Lind 🎩: https://pagure.io/fedora-infra/ansible/blob/main/f/roles/openqa , https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa.yml , https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa-workers.yml
2024-04-15 16:22:00 <@adamwill:fedora.im> it is a fairly complex deployment, unfortunately
2024-04-15 16:22:18 <@adamwill:fedora.im> https://pagure.io/fedora-infra/ansible/blob/main/f/playbooks/groups/openqa-onebox-test.yml is a single system playbook which we used for testing some stuff a while back, it should still mostly work
2024-04-15 16:22:20 <@salimma:fedora.im> thanks! yeah I am thinking of parsing it, grabbing the packages, then try installing in mock and flag if it fails
2024-04-15 16:22:57 <@decathorpe:fedora.im> either way, I think a change like this should *at least* have been coordinated with maintainers of dependent packages (i.e. libteam?), or even have been a full Change Proposal. it was *mentioned* in previous change proposals, but always as something that will happen *later*
2024-04-15 16:23:06 <@adamwill:fedora.im> yeah
2024-04-15 16:23:19 <@adamwill:fedora.im> anyhow, not really ours to vote on, so...let's move on, if there's nothing else?
2024-04-15 16:24:10 <@salimma:fedora.im> yeah we should definitely bring this up at FESCo later today
2024-04-15 16:27:27 <@adamwill:fedora.im> alrgihty
2024-04-15 16:27:38 <@adamwill:fedora.im> !topic Proposed Final freeze exceptions
2024-04-15 16:27:41 <@adamwill:fedora.im> !topic (2274740) fdo-client-linuxapp.service is not enabled by default on IoT
2024-04-15 16:27:44 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2274740
2024-04-15 16:27:47 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1591
2024-04-15 16:27:49 <@adamwill:fedora.im> !info Proposed Freeze Exceptions, fedora-release, ON_QA
2024-04-15 16:27:51 <@adamwill:fedora.im> !info Ticket vote: FinalFreezeException (+4,0,-0) (+adamwill, +geraldosimiao, +salimma, +pbrobinson)
2024-04-15 16:28:05 <@adamwill:fedora.im> so i was kinda holding this one for it to go through the policy requirements for a new default service
2024-04-15 16:30:10 <@tablepc:matrix.org> I don't test IOT
2024-04-15 16:30:34 <@nirik:matrix.scrye.com> I don't know if there's a way for iot to pull this without another RC... but in any case a FE seems reasonable.
2024-04-15 16:31:27 <@adamwill:fedora.im> I think if we push it stable, IoT can nominate a compose done tomorrow or wednesday for release
2024-04-15 16:32:52 <@nielsenb:fedora.im> FinalFE +1
2024-04-15 16:32:56 <@nielsenb:fedora.im> Though it already has the votes?
2024-04-15 16:33:00 <@adamwill:fedora.im> ok, Stephen Gallagher asked questions at https://src.fedoraproject.org/rpms/fedora-release/pull-request/329#comment-194357 and zbyszek answered at https://src.fedoraproject.org/rpms/fedora-release/pull-request/329#comment-194593
2024-04-15 16:33:04 <@adamwill:fedora.im> given the answers, I'm +1
2024-04-15 16:33:15 <@adamwill:fedora.im> Brandon Nielsen: yeah, i wanted to make sure the policy was complied with before approving this
2024-04-15 16:33:26 <@frantisekz:fedora.im> anyhow, +1 FE
2024-04-15 16:34:32 <@adamwill:fedora.im> proposed !agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it' affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
2024-04-15 16:34:40 <@adamwill:fedora.im> proposed !agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
2024-04-15 16:35:07 <@nielsenb:fedora.im> ack
2024-04-15 16:35:10 <@frantisekz:fedora.im> ack
2024-04-15 16:35:27 <@nhanlon:beeper.com> ack
2024-04-15 16:35:39 <@umu:catnip.ee> ack
2024-04-15 16:35:48 <@adamwill:fedora.im> !agreed 2274740 - AcceptedFreezeException (Final) - this is accepted as an FE as it affects the intended configuration of the IoT edition and cannot be fixed with a post-release update
2024-04-15 16:36:04 <@adamwill:fedora.im> !topic (2263334) F40FailsToInstall: network-scripts-teamd
2024-04-15 16:36:06 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2263334
2024-04-15 16:36:08 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1592
2024-04-15 16:36:11 <@adamwill:fedora.im> !info Proposed Freeze Exceptions, libteam, ON_QA, depends on other bugs 
2024-04-15 16:36:13 <@adamwill:fedora.im> !info Ticket vote: FinalFreezeException (+1,0,-0) (+geraldosimiao)
2024-04-15 16:36:30 <@adamwill:fedora.im> this kinda is related to the network service one (it's how we found it), but regardless, i think we should give this an FE, fixing FTI is good
2024-04-15 16:37:03 <@nirik:matrix.scrye.com> +1 FE
2024-04-15 16:37:09 <@nielsenb:fedora.im> I agree
2024-04-15 16:37:11 <@nielsenb:fedora.im> FinalFE +1
2024-04-15 16:37:17 <@salimma:fedora.im> q: if network-scripts come back, we still don't want to restore network-scripts-teamd right?
2024-04-15 16:37:19 <@nhanlon:beeper.com> +1 FE 
2024-04-15 16:37:40 <@salimma:fedora.im> since we don't really need it, and I suspect network-scripts will eventually go away (but with a proper Change Proposal ideally)
2024-04-15 16:37:57 <@nirik:matrix.scrye.com> probibly not? although it could come back and be retired when network-scripts is.
2024-04-15 16:38:07 <@salimma:fedora.im> very low-risk fix, this one - it's literally the same build with one subpackage removed
2024-04-15 16:38:36 <@salimma:fedora.im> right. if the upstream developer wants to re-maintain the package I'll leave that decision up to him (pending what fesco decides)
2024-04-15 16:38:51 <@adamwill:fedora.im> i'd say that's up to the maintainer and upstream
2024-04-15 16:39:48 <@decathorpe:fedora.im> have they fixed their account email address so they'll get future fedora emails? :)
2024-04-15 16:41:10 <@salimma:fedora.im> idk. they were in touch with Carlos it seems, so I asked him in devel to follow up
2024-04-15 16:41:31 <@adamwill:fedora.im> proposed !agreed 2263334 - AcceptedFreezeException (Final) - this is accepted on the general principle that we accept clean FTI fixes to ease the upgrade process
2024-04-15 16:42:01 <@geraldosimiao:matrix.org> Ack
2024-04-15 16:42:07 <@frantisekz:fedora.im> ack
2024-04-15 16:42:16 <@nielsenb:fedora.im> ack
2024-04-15 16:42:46 <@adamwill:fedora.im> !agreed 2263334 - AcceptedFreezeException (Final) - this is accepted on the general principle that we accept clean FTI fixes to ease the upgrade process
2024-04-15 16:42:48 <@nhanlon:beeper.com> ack
2024-04-15 16:43:10 <@adamwill:fedora.im> !topic (2274724) [abrt] nautilus: ptr_array_free(): nautilus killed by SIGABRT
2024-04-15 16:43:14 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2274724
2024-04-15 16:43:16 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1590
2024-04-15 16:43:18 <@adamwill:fedora.im> !info Proposed Freeze Exceptions, nautilus, VERIFIED
2024-04-15 16:43:21 <@adamwill:fedora.im> !info Ticket vote: FinalBlocker (+0,0,-3) (-geraldosimiao, -adamwill, -catanzaro)
2024-04-15 16:43:23 <@adamwill:fedora.im> !info Ticket vote: FinalFreezeException (+3,0,-0) (+adamwill, +geraldosimiao, +kparal)
2024-04-15 16:43:31 <@adamwill:fedora.im> did i vote +1 on this? huh.
2024-04-15 16:43:53 <@adamwill:fedora.im> it actually feels a bit borderline to me, not sure how much file+folder compression people are doing on live images. but otoh, fix looks clear and it's been well tested
2024-04-15 16:44:10 <@nirik:matrix.scrye.com> I think it's ok for a FE, I don't think it's a blocker.
2024-04-15 16:44:35 <@nielsenb:fedora.im> I feel like it could be pretty easily fixed post release
2024-04-15 16:44:57 <@adamwill:fedora.im> i meant borderline FE
2024-04-15 16:45:30 <@adamwill:fedora.im> just because fixing it 0-day is probably fine. but ehh, maybe someone wants to compress things on the live desktop. i'm probably like 0.2. :D
2024-04-15 16:45:33 <@nirik:matrix.scrye.com> true... not too many people would be doing this on a live.
2024-04-15 16:45:37 <@adamwill:fedora.im> just because fixing it 0-day is probably fine. but ehh, maybe someone wants to compress things on the live desktop. i'm probably like +0.2. :D
2024-04-15 16:46:25 <@nielsenb:fedora.im> FinalFE +0
2024-04-15 16:46:32 <@tablepc:matrix.org> I just tried the compress twice and it worked fine.
2024-04-15 16:46:32 <@nielsenb:fedora.im> The fix is out there and tested
2024-04-15 16:46:37 <@nielsenb:fedora.im> But I don't see the point of pushing it really
2024-04-15 16:46:56 <@tablepc:matrix.org> Yes I did the update
2024-04-15 16:48:05 <@salimma:fedora.im> oh, speaking of upgrade process, right now the removed network-scripts-teamd is not properly obsoleted by a remaining subpackage. should I fix it real quick? or just leave it since I suspect it's not widely installed anyway, and maybe people who do have it installed should take manual action if they really need it
2024-04-15 16:48:19 <@adamwill:fedora.im> by policy it should be obsoleted
2024-04-15 16:48:27 <@adamwill:fedora.im> i would probably do it if it were me
2024-04-15 16:48:37 <@adamwill:fedora.im> but, well
2024-04-15 16:48:41 <@nielsenb:fedora.im> Do it
2024-04-15 16:48:52 <@adamwill:fedora.im> unless you plan to put it back if we put network-scripts back
2024-04-15 16:49:00 <@salimma:fedora.im> ok, let me pause the auto push to stable and fix this real quick
2024-04-15 16:49:03 <@salimma:fedora.im> we don't need to revote right?
2024-04-15 16:49:10 <@nirik:matrix.scrye.com> might wait to hear if they want it back or not
2024-04-15 16:49:18 <@zodbot:fedora.im> salimma has already given cookies to adamwill during the F39 timeframe
2024-04-15 16:49:32 <@salimma:fedora.im> yeah, so disable the auto push for now so it does not go to stable
2024-04-15 16:50:51 <@adamwill:fedora.im> no need to revote, no
2024-04-15 16:51:08 <@adamwill:fedora.im> okay, so for this one...
2024-04-15 16:51:15 <@adamwill:fedora.im> ehh, let's just accept it to move things along...:P
2024-04-15 16:51:56 <@adamwill:fedora.im> proposed !agreed 2274724 - AcceptedFreezeException (Final) - this is accepted as a crasher bug people could at least potentially run into on the Workstation live image. The fix is targeted and well tested.
2024-04-15 16:52:10 <@nielsenb:fedora.im> ack
2024-04-15 16:52:17 <@geraldosimiao:matrix.org> Ack 
2024-04-15 16:52:32 <@nhanlon:beeper.com> ack
2024-04-15 16:54:20 <@adamwill:fedora.im> !agreed 2274724 - AcceptedFreezeException (Final) - this is accepted as a crasher bug people could at least potentially run into on the Workstation live image. The fix is targeted and well tested.
2024-04-15 16:54:25 <@adamwill:fedora.im> !topic (2274171) parsec 1.4.0
2024-04-15 16:54:27 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2274171
2024-04-15 16:54:29 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1580
2024-04-15 16:54:32 <@adamwill:fedora.im> !info Proposed Freeze Exceptions, parsec, ON_QA
2024-04-15 16:54:35 <@adamwill:fedora.im> !info Ticket vote: FinalFreezeException (+2,0,-0) (+geraldosimiao, +pwhalen)
2024-04-15 16:54:43 <@adamwill:fedora.im> i'm not really a huge fan of this proposal, it just says "new version! we want it!"
2024-04-15 16:54:52 <@adamwill:fedora.im> well...why? what's it do? what's the justification for breaking freeze?
2024-04-15 16:54:57 <@adamwill:fedora.im> Peter Robinson: are you around for more details?
2024-04-15 16:55:24 <@nielsenb:fedora.im> Where's your spirit of adventure?
2024-04-15 16:55:54 <@adamwill:fedora.im> Brandon Nielsen: nailed to the wall, alongside my sunny, youthful nature
2024-04-15 16:55:56 <@tablepc:matrix.org> We want it is dangerous justification
2024-04-15 16:56:55 <@nhanlon:beeper.com> also; for what it's worth... 1.4.0 parsec failed in upstream CI...
2024-04-15 16:56:58 <@nhanlon:beeper.com> https://app.circleci.com/pipelines/github/parallaxsecond/parsec/267/workflows/72728aae-1e29-4be5-bf05-b227133859ab/jobs/242/tests
2024-04-15 16:57:01 <@nhanlon:beeper.com> soooo
2024-04-15 16:57:31 <@salimma:fedora.im> oof
2024-04-15 16:57:39 <@geraldosimiao:matrix.org> 😯
2024-04-15 16:57:40 <@salimma:fedora.im> and yeah the changelog is unclear about any breaking change https://github.com/parallaxsecond/parsec/blob/main/CHANGELOG.md
2024-04-15 16:58:04 <@adamwill:fedora.im> that is one hell of a CI failure
2024-04-15 16:58:10 <@adamwill:fedora.im> def test_answer():
>       assert 1 + 1 == 3
2024-04-15 16:58:13 <@adamwill:fedora.im> i have questions
2024-04-15 16:58:23 <@geraldosimiao:matrix.org> Weel ill revert my vote to
FE +0
2024-04-15 16:58:43 <@nhanlon:beeper.com> I'm FE-1 and investigation+2
2024-04-15 16:58:43 <@geraldosimiao:matrix.org> Wel ill revert my vote to
FE +0
2024-04-15 16:59:08 <@geraldosimiao:matrix.org> Wel I'll revert my vote to
FE +0
2024-04-15 16:59:14 <@nielsenb:fedora.im> FinalFE -1
2024-04-15 16:59:23 <@salimma:fedora.im> 🤦‍♂️
2024-04-15 16:59:43 <@adamwill:fedora.im> i mean, maybe there's a reason for that, but it sure *looks* weird. :D
2024-04-15 17:00:27 <@salimma:fedora.im> checking the dependencies, looks like dbus-parsec depends on parsec and does not specify any version range. so... yeah it should probably be tested 
2024-04-15 17:00:32 <@nhanlon:beeper.com> ngl, so does this https://github.com/parallaxsecond/parsec/commit/9aeb04bed071eaa87aa5a18df837a11e64d219f6
2024-04-15 17:02:02 <@salimma:fedora.im> that part seems reasonable though - depends on if you can still run it. tests that depend on specific hardware are annoying when they fail
2024-04-15 17:02:18 <@adamwill:fedora.im> proposed !agreed 2274171 - RejectedFreezeException (Final) - the proposal here provides no real justification for a freeze exception, and the request is to pull in a major new release with an unclear backwards compatibility status and some slightly odd test results. This is rejected for now, can be proposed again with a clearer justification
2024-04-15 17:02:40 <@nielsenb:fedora.im> ack
2024-04-15 17:02:44 <@nhanlon:beeper.com> ack
2024-04-15 17:02:49 <@adamwill:fedora.im> oh, that's counting me as FinalFE -1, sorry
2024-04-15 17:02:52 <@adamwill:fedora.im> which i didn't explicitly say
2024-04-15 17:02:53 <@salimma:fedora.im> ack
2024-04-15 17:03:08 <@frantisekz:fedora.im> ack
2024-04-15 17:03:47 <@adamwill:fedora.im> !agreed 2274171 - RejectedFreezeException (Final) - the proposal here provides no real justification for a freeze exception, and the request is to pull in a major new release with an unclear backwards compatibility status and some slightly odd test results. This is rejected for now, can be proposed again with a clearer justification
2024-04-15 17:03:54 <@nhanlon:beeper.com> yeah, it's probably innocuous, just in light of... recent events... I question everything :)
2024-04-15 17:04:20 <@salimma:fedora.im> fair
2024-04-15 17:04:42 <@nhanlon:beeper.com> on the less paranoid hand ... it's probably for a CVE that they're trying to not disclose yet
2024-04-15 17:05:24 <@tablepc:matrix.org> Please don't even think that
2024-04-15 17:06:05 <@nhanlon:beeper.com> i mean, the changelog notes "- Vulnerability in SQLite [\#648](https://github.com/parallaxsecond/parsec/issues/648)" so, there is at least that. Still, would like to have more justification.
2024-04-15 17:06:49 <@salimma:fedora.im> oh boy if this is some undisclosed bug... the fallout could be huge once we finally know the details
2024-04-15 17:06:53 <@salimma:fedora.im> sqlite...
2024-04-15 17:07:05 <@salimma:fedora.im> oh boy if this is some embargoed bug... the fallout could be huge once we finally know the details
2024-04-15 17:07:10 <@salimma:fedora.im> s/undisclosed/embargoed
2024-04-15 17:07:20 <@decathorpe:fedora.im> note that dbus-parsec has been FTBFS for a while, so fixing it if necessary would be more work than just adding a patch 
2024-04-15 17:07:38 <@salimma:fedora.im> ah yes, I was wondering why the NVR in Rawhide is still from fc39
2024-04-15 17:10:10 <@adamwill:fedora.im> alrighty, that's all the proposals
2024-04-15 17:10:17 <@adamwill:fedora.im> let's circle back to the tabled one
2024-04-15 17:10:26 <@adamwill:fedora.im> !info let's circle back to our tabled blocker proposal
2024-04-15 17:10:32 <@adamwill:fedora.im> !topic (2275099) Recording the screencast does not work properly.
2024-04-15 17:10:39 <@adamwill:fedora.im> so, I did reproduce this in a VM, did everyone else try?
2024-04-15 17:10:48 <@nielsenb:fedora.im> Just tried again on a fresh 1.14 install, worked fine on my laptop
2024-04-15 17:11:02 <@nielsenb:fedora.im> In a VM, it also worked, but blue is orange
2024-04-15 17:11:13 <@nielsenb:fedora.im> It's been awhile since I worked in video, so I don't remember what that might mean
2024-04-15 17:12:04 <@decathorpe:fedora.im> bit swizzling problem? or YUV / RGB issue?
2024-04-15 17:12:37 <@nielsenb:fedora.im> "Color is messed up"
2024-04-15 17:13:11 <@nielsenb:fedora.im> But yeah, I'm guessing colorspace is set wrong somehow
2024-04-15 17:13:18 <@tablepc:matrix.org> I haven't had any color issue with my bare metal.
2024-04-15 17:14:43 <@tablepc:matrix.org> Haven't been fiddling with color either
2024-04-15 17:15:47 <@adamwill:fedora.im> did anyone try in a VM? can folks try that?
2024-04-15 17:15:55 <@adamwill:fedora.im> if we can say 'this pretty much always reproduces in a VM but not on metal', that seems helpful
2024-04-15 17:16:14 <@nielsenb:fedora.im> Worked for me, except the color issue noted
2024-04-15 17:16:59 <@nielsenb:fedora.im> I have yet to see the crash
2024-04-15 17:17:09 <@nielsenb:fedora.im> Feel like I'm missing out
2024-04-15 17:17:58 <@nirik:matrix.scrye.com> upstream report suggests latest pipewire/mesa could fix this...
2024-04-15 17:19:25 <@adamwill:fedora.im> well, we're on mesa 24.0.5 at least
2024-04-15 17:19:35 <@adamwill:fedora.im> weird note: i just tried on vmware and it doesn't offer screen recording *at all*
2024-04-15 17:19:45 <@tablepc:matrix.org> When you're testing with a vm do you use cockpit or boxes to set it up for test
2024-04-15 17:19:51 <@adamwill:fedora.im> must be some kind of detection going on there? but i dunno what about the VM would make gnome decide not to offer screen recording. huh.
2024-04-15 17:20:04 <@adamwill:fedora.im> tablepc: i'm using virt-manager , but they all use libvirt behind the scenes so it shouldn't matter much
2024-04-15 17:20:04 <@nielsenb:fedora.im> Boxes, with GPU acceleration otherwise performance is unbearable
2024-04-15 17:20:33 <@nielsenb:fedora.im> It checks the license fee
2024-04-15 17:20:46 <@nhanlon:beeper.com> insert coin to record
2024-04-15 17:21:07 <@nirik:matrix.scrye.com> PC LOAD LETTER
2024-04-15 17:22:04 <@salimma:fedora.im> gives a new meaning to token-passing
2024-04-15 17:22:37 <@tablepc:matrix.org> But where do you get the tokens?
2024-04-15 17:22:56 <@nhanlon:beeper.com> wherever gold coins are sold
2024-04-15 17:23:18 <@tablepc:matrix.org> But my PCs don't have coin slots
2024-04-15 17:23:33 <@salimma:fedora.im> put it in the HDMI port
2024-04-15 17:23:38 <@nhanlon:beeper.com> CMOS 😈
2024-04-15 17:26:35 <@adamwill:fedora.im> sooo...
2024-04-15 17:27:20 <@adamwill:fedora.im> i dunno, let's see if i can reliably reproduce in the vm, then try with newer pipewire...
2024-04-15 17:28:20 <@adamwill:fedora.im> yeah, triggered it second try too, 2/2
2024-04-15 17:28:22 <@adamwill:fedora.im> let's try once more
2024-04-15 17:28:34 <@nhanlon:beeper.com> i'm trying now too
2024-04-15 17:28:44 <@nielsenb:fedora.im> Must be some strange confluence of hardware and VM
2024-04-15 17:28:52 <@adamwill:fedora.im> "Because that fixed a timeout bug that could occur, especially without proper 3d drivers."
2024-04-15 17:29:39 <@nielsenb:fedora.im> I can't select the "Window" option, which is odd
2024-04-15 17:29:56 <@adamwill:fedora.im> yep, 3/3
2024-04-15 17:30:01 <@adamwill:fedora.im> always seems to happen at 25 seconds
2024-04-15 17:30:19 <@nielsenb:fedora.im> Oh, they need to be that long?
2024-04-15 17:31:32 <@nielsenb:fedora.im> 50 seconds, no problem
2024-04-15 17:32:09 <@adamwill:fedora.im> vm or metal?
2024-04-15 17:32:30 <@nielsenb:fedora.im> VM that time
2024-04-15 17:32:33 <@nielsenb:fedora.im> Trying now on metal
2024-04-15 17:32:33 <@tablepc:matrix.org> Trying long
2024-04-15 17:32:37 <@adamwill:fedora.im> hmm
2024-04-15 17:32:41 <@adamwill:fedora.im> try without 3D passthru?
2024-04-15 17:32:57 <@nielsenb:fedora.im> 50 seconds, fine on metal
2024-04-15 17:33:12 <@nielsenb:fedora.im> I genuinely can barely even use the desktop without that
2024-04-15 17:33:33 <@nielsenb:fedora.im> I'm a pretty tolerant user, but...
2024-04-15 17:33:46 <@adamwill:fedora.im> i mean, it's just for testing
2024-04-15 17:33:58 <@adamwill:fedora.im> (also i never use it because it doesn't seem to work on my system, so if i have to suck it up so do you :>)
2024-04-15 17:34:15 <@nielsenb:fedora.im> I'm just saying, I'm not sure I really consider that a valid use case?
2024-04-15 17:34:16 <@nhanlon:beeper.com> yeah just repro'd here in kvm
2024-04-15 17:34:18 <@nhanlon:beeper.com> 25 seconds
2024-04-15 17:34:23 <@nielsenb:fedora.im> "Look at how bad this performs!"
2024-04-15 17:35:13 <@nielsenb:fedora.im> Oh yeah, look at that
2024-04-15 17:35:14 <@adamwill:fedora.im> okay, pipewire doesn't fix it
2024-04-15 17:35:17 <@nielsenb:fedora.im> Explodes right at 25s
2024-04-15 17:35:21 <@adamwill:fedora.im> okay
2024-04-15 17:35:49 <@adamwill:fedora.im> so, seems like we can say this is pretty consistently happening on VMs with 3D passthrough disabled (I think someone said they saw it even with 3d passthrough enabled, but i guess it might depend on performance or phase of the moon or something)(
2024-04-15 17:35:57 <@adamwill:fedora.im> i don't think anyone reproduced on metal yet
2024-04-15 17:36:11 <@adamwill:fedora.im> do we wanna block on that?
2024-04-15 17:36:20 <@adamwill:fedora.im> i kinda feel like 'no'...
2024-04-15 17:36:30 <@nielsenb:fedora.im> I don't, I can see the argument for it, but I don't
2024-04-15 17:37:03 <@adamwill:fedora.im> i guess we're technically arguing whether this is a broad enough violation of the default app and/or panel criteria
2024-04-15 17:37:03 <@tablepc:matrix.org> I just ran and watched one for almost 2 minutes and it was fine.
2024-04-15 17:37:12 <@geraldosimiao:matrix.org> Wat did we at that time when copy paste get broke on kde vm? 
2024-04-15 17:37:26 <@adamwill:fedora.im> "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use" and all default applications must "withstand a basic functionality test"
2024-04-15 17:37:34 <@geraldosimiao:matrix.org> Wat we did at that time when copy paste get broke on kde vm? 
2024-04-15 17:37:56 <@adamwill:fedora.im> (you can trigger a recording from the panel or by launching it like an app from the overview, so i guess both are kinda applicable)
2024-04-15 17:37:57 <@nhanlon:beeper.com> possibly of note: I also get a crash on trying to record a screen area, whereas the 'full screen' option fails after 25s
2024-04-15 17:38:03 <@adamwill:fedora.im> geraldosimiao: didn't block. it's still broken.
2024-04-15 17:38:18 <@adamwill:fedora.im> Neil Hanlon: oh, interesting. i was always using full screen
2024-04-15 17:38:24 <@geraldosimiao:matrix.org> Ok, yeah 
2024-04-15 17:38:33 <@nielsenb:fedora.im> I was doing a selection
2024-04-15 17:38:35 <@geraldosimiao:matrix.org> So just FE 
2024-04-15 17:38:35 <@adamwill:fedora.im> so, i'm -1
2024-04-15 17:38:43 <@adamwill:fedora.im> counting nirik and brandon as -1 we're at -3
2024-04-15 17:38:45 <@nhanlon:beeper.com> that's even odder 😂
2024-04-15 17:38:45 <@adamwill:fedora.im> other votes?
2024-04-15 17:38:50 <@nielsenb:fedora.im> FinalBlocker -1
2024-04-15 17:38:51 <@nhanlon:beeper.com> -1
2024-04-15 17:39:05 <@salimma:fedora.im> FinalBlocker -1
2024-04-15 17:39:09 <@nhanlon:beeper.com> FB-1, to be clear
2024-04-15 17:39:10 <@geraldosimiao:matrix.org> FB -1
FE +1
2024-04-15 17:39:20 <@salimma:fedora.im> FinalFE +1
2024-04-15 17:39:26 <@nhanlon:beeper.com> FE+1
2024-04-15 17:39:28 <@adamwill:fedora.im> sure, FE +1
2024-04-15 17:40:27 <@nirik:matrix.scrye.com> FinalBlocker -1
2024-04-15 17:40:29 <@geraldosimiao:matrix.org> And, after all, is this gnome shell or pipewire mesa? 
2024-04-15 17:40:42 <@geraldosimiao:matrix.org> What do you think? 
2024-04-15 17:40:59 <@tablepc:matrix.org> I just tried a screencast on an area and it was all messed up for color
2024-04-15 17:41:31 <@adamwill:fedora.im> proposed !agreed 2275099 - RejectedBlocker (Final) - AcceptedFreezeException (Final) - our testing during the meeting suggests this is almost 100% reproducible on libvirt/qemu VMs (especially without 3D passthrough), but not reproducible at all on bare metal. That makes this a conditional violation of the "basic functionality" criterion for default apps and the default panel functionality criterion, but we judge that it's not severe enough to constitute a blocker, but it is bad enough to grant an FE.
2024-04-15 17:41:39 <@adamwill:fedora.im> geraldosimiao: dunno, we can figure that out outside the meeting I guess
2024-04-15 17:41:49 <@nielsenb:fedora.im> ack
2024-04-15 17:41:51 <@nhanlon:beeper.com> ack
2024-04-15 17:42:06 <@adamwill:fedora.im> tablepc: are you testing in a VM or on metal? sorry, i'm losing track :D
2024-04-15 17:42:09 <@geraldosimiao:matrix.org> Ack 
2024-04-15 17:42:22 <@tablepc:matrix.org> metal
2024-04-15 17:43:28 <@tablepc:matrix.org> Just gor wide white and blue strips
2024-04-15 17:43:30 <@adamwill:fedora.im> hum, what system?
2024-04-15 17:43:40 <@adamwill:fedora.im> !agreed 2275099 - RejectedBlocker (Final) - AcceptedFreezeException (Final) - our testing during the meeting suggests this is almost 100% reproducible on libvirt/qemu VMs (especially without 3D passthrough), but not reproducible at all on bare metal. That makes this a conditional violation of the "basic functionality" criterion for default apps and the default panel functionality criterion, but we judge that it's not severe enough to constitute a blocker, but it is bad enough to grant an FE.
2024-04-15 17:43:47 <@adamwill:fedora.im> kinda sounds like you're hitting something different
2024-04-15 17:44:08 <@tablepc:matrix.org> Lenovo intel
2024-04-15 17:44:36 <@adamwill:fedora.im> hmm
2024-04-15 17:44:47 <@adamwill:fedora.im> just tried here on my bare metal test box and colors in an area recording seem fine
2024-04-15 17:44:56 <@adamwill:fedora.im> !topic Accepted blocker review
2024-04-15 17:45:04 <@adamwill:fedora.im> !topic (2242759) dnf system-upgrade fails on some RPi4 due to system boot date that pre-dates gpg key
2024-04-15 17:45:06 <@adamwill:fedora.im> !link https://bugzilla.redhat.com/show_bug.cgi?id=2242759
2024-04-15 17:45:09 <@adamwill:fedora.im> !link https://pagure.io/fedora-qa/blocker-review/issue/1435
2024-04-15 17:45:12 <@adamwill:fedora.im> !info Accepted Previous Release Blocker, distribution, NEW
2024-04-15 17:45:19 <@adamwill:fedora.im> we still seem to be stuck on this one :/ no great ideas, anyone?
2024-04-15 17:46:06 <@nielsenb:fedora.im> So, the small service to set a clock based on file age is pretty much how I would solve it. But I don't see how you make that actually happen _before_ the update.
2024-04-15 17:46:25 <@nielsenb:fedora.im> At least automagically
2024-04-15 17:46:59 <@tablepc:matrix.org> Window worked
2024-04-15 17:47:11 <@decathorpe:fedora.im> isn't that what Before / After settings in unit files are for?
2024-04-15 17:47:40 <@nielsenb:fedora.im> Right, but how do you get that service installed and running on a system before you do the update without some kind of additional user interaction?
2024-04-15 17:47:54 <@adamwill:fedora.im> ah, it looks like wireplumber update fixes the screencast thing
2024-04-15 17:47:58 <@nielsenb:fedora.im> And running in the update environment
2024-04-15 17:48:51 <@nirik:matrix.scrye.com> I think the update env is just a target... just needs to add that service Before it...
2024-04-15 17:49:20 <@nielsenb:fedora.im> Basically, any "fix" is just as bad of a story for the user as the currently documented fix.
2024-04-15 17:49:30 <@nielsenb:fedora.im> At least as I see it.
2024-04-15 17:49:52 <@nielsenb:fedora.im> Can skip the script and just enable timesyncd or whatever the systemd thing is.
2024-04-15 17:50:52 <@decathorpe:fedora.im> just run it unconditionally? having the clock set to some date way in the past is *always* bad on devices like the RPi :)
2024-04-15 17:50:56 <@nielsenb:fedora.im> I guess by fix I  mean workaround in commonbugs.
2024-04-15 17:51:13 <@nirik:matrix.scrye.com> I guess it would be nice to have the dnf maintainers weigh in on what they would accept?
2024-04-15 17:51:17 <@adamwill:fedora.im> !info we still don't have a great idea for a fix for this, we'll have to discuss further at go/no-go
2024-04-15 17:51:26 <@nirik:matrix.scrye.com> because it could just do this as part of the normal system-upgrade
2024-04-15 17:53:05 <@nielsenb:fedora.im> https://discussion.fedoraproject.org/t/f38-to-f39-40-dnf-system-upgrade-can-fail-on-raspberry-pi/92403
2024-04-15 17:53:21 <@nielsenb:fedora.im> Basically, touching a file is just as easy of a thing to tell a user to do, as install a package
2024-04-15 17:54:12 <@nielsenb:fedora.im> Side note, I feel like common issues on Discourse aren't as favored by Google as what we did before :-/
2024-04-15 17:56:11 <@nielsenb:fedora.im> Could make a one-shot service somehow required on update, so it would get pulled in during the "upgrade before updating releases" step maybe. But as I discovered, using gnome-software to do a regular update also hits this bug, so again, requires manual user CLI intervention
2024-04-15 17:56:17 <@adamwill:fedora.im> okay, let's move to open floor, as we only have five minutes left...
2024-04-15 17:56:24 <@adamwill:fedora.im> !topic Open floor
2024-04-15 17:56:28 <@adamwill:fedora.im> any other business, folks?
2024-04-15 17:57:20 <@tablepc:matrix.org> Looking forward to F40 Workstation
2024-04-15 17:58:42 <@tablepc:matrix.org> Oh QUick question  is there a place to set the font size in the F40 top bar
2024-04-15 17:59:33 <@adamwill:fedora.im> no idea
2024-04-15 17:59:55 <@tablepc:matrix.org> I ask on Ask
2024-04-15 18:00:22 <@adamwill:fedora.im> alrighty folks, that's time
2024-04-15 18:00:28 <@adamwill:fedora.im> thanks for coming, everyone!
2024-04-15 18:00:35 <@tablepc:matrix.org> Have a Great Afternoon!
2024-04-15 18:00:35 <@adamwill:fedora.im> keep testing RC 1.14 :)
2024-04-15 18:00:39 <@adamwill:fedora.im> !endmeeting