<@adamwill:fedora.im>
17:00:32
!startmeeting F44-blocker-review
<@meetbot:fedora.im>
17:00:32
Meeting started at 2026-02-23 17:00:32 UTC
<@meetbot:fedora.im>
17:00:33
The Meeting name is 'F44-blocker-review'
<@adamwill:fedora.im>
17:00:36
!topic Roll Call
<@adamwill:fedora.im>
17:00:47
hi hi everyone, it's your favourite time of the week again
<@conan_kudo:matrix.org>
17:01:18
!hi
<@zodbot:fedora.im>
17:01:22
Neal Gompa (ngompa) - he / him / his
<@kparal:matrix.org>
17:01:40
!hi
<@zodbot:fedora.im>
17:01:41
Kamil Páral (kparal) - he / him / his
<@conan_kudo:matrix.org>
17:01:46
tool time?
<@jgroman:fedora.im>
17:01:58
!hi
<@zodbot:fedora.im>
17:01:59
Jaroslav Groman (jgroman)
<@conan_kudo:matrix.org>
17:01:59
is tim the tool man taylor here too?
<@psklenar:fedora.im>
17:02:03
!hi
<@zodbot:fedora.im>
17:02:04
Petr Sklenar (psklenar)
<@korora:fedora.im>
17:02:40
!hi
<@zodbot:fedora.im>
17:02:41
Jocelyn Gould (korora) - she / her / hers
<@adamwill:fedora.im>
17:03:25
hi hi
<@boniboyblue:fedora.im>
17:03:32
!hi
<@zodbot:fedora.im>
17:03:33
Christopher Boni (boniboyblue)
<@adamwill:fedora.im>
17:03:37
alrighty, let's get rolling with some wonderful boilerplate
<@adamwill:fedora.im>
17:03:44
!link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
<@adamwill:fedora.im>
17:03:44
!link https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria
<@adamwill:fedora.im>
17:03:44
!link https://fedoraproject.org/wiki/Fedora_44_Beta_Release_Criteria
<@adamwill:fedora.im>
17:03:44
!link https://fedoraproject.org/wiki/Basic_Release_Criteria
<@adamwill:fedora.im>
17:03:44
!info The criteria for release blocking bugs can be found at:
<@adamwill:fedora.im>
17:03:44
!link http://qa.fedoraproject.org/blockerbugs/current
<@adamwill:fedora.im>
17:03:44
!topic Introduction
<@adamwill:fedora.im>
17:03:44
Why are we here?
<@adamwill:fedora.im>
17:03:44
!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.
<@adamwill:fedora.im>
17:03:44
!info We'll be following the process outlined at:
<@adamwill:fedora.im>
17:03:44
!info The bugs up for review today are available at:
<@adamwill:fedora.im>
17:04:03
(man i still owe infinity beers to whoever fixed matrix so I don't have to paste that one line at a time any more)
<@adamwill:fedora.im>
17:04:19
!info for Beta, we have:
<@adamwill:fedora.im>
17:04:29
!info 4 Proposed Freeze Exceptions
<@adamwill:fedora.im>
17:04:29
!info 2 Proposed Blockers
<@adamwill:fedora.im>
17:04:29
!info 8 Accepted Freeze Exceptions
<@adamwill:fedora.im>
17:04:29
!info 2 Accepted Blockers
<@adamwill:fedora.im>
17:05:09
!info nothing to review for Final ATM
<@adamwill:fedora.im>
17:05:19
who wants to secretarialize?
<@adamwill:fedora.im>
17:06:41
welp, if nobody does, guess I will
<@adamwill:fedora.im>
17:06:49
!info adamw will secretarialize
<@adamwill:fedora.im>
17:07:13
!topic Proposed Beta blockers
<@adamwill:fedora.im>
17:07:22
!link https://bugzilla.redhat.com/show_bug.cgi?id=2439813
<@adamwill:fedora.im>
17:07:22
!topic (2439813) KDE network installs hang during scriptlets (%triggerin on ibus)
<@adamwill:fedora.im>
17:07:22
!info Proposed Blocker, anaconda, NEW
<@adamwill:fedora.im>
17:07:22
!link https://pagure.io/fedora-qa/blocker-review/issue/2048
<@adamwill:fedora.im>
17:08:01
so...i'm not sure there's a criterion that covers this. we require package set selection to work in anaconda, but we specifically say in that criterion it doesn't mean the selected package set must actually work. and afaik the 'officially supported' way to deploy KDE is the live image
<@adamwill:fedora.im>
17:08:15
still, it's a pretty bad bug (and it's a problem for openQA cos it means we can't re-generate the KDE base disk image)
<@conan_kudo:matrix.org>
17:08:45
wait what?
<@m4rtink:fedora.im>
17:09:12
maybe it expects some DBus service that is not running to be there ?
<@adamwill:fedora.im>
17:09:35
i'm about to re-test this and see if kparal's dconf theory is right
<@kparal:matrix.org>
17:09:39
I'll try to do some of that on the fly
<@m4rtink:fedora.im>
17:09:43
sounds like some input method related thing & that is often run via DBus
<@kparal:matrix.org>
17:10:32
I filed this bug because two people already complained about it on quality channel
<@kparal:matrix.org>
17:10:39
so it's pretty much confirmed, I think
<@kparal:matrix.org>
17:10:58
in the end I waited 45 minutes I think and then killed it
<@adamwill:fedora.im>
17:11:34
oh, yes, it's definitely consistent, i already reported it (this is my original report, i closed yours as a dupe) and openQA disk image generation has been stuck on it for weeks
<@adamwill:fedora.im>
17:13:29
per the criteria i guess this is a bit fuzzy. the way it works is we have the "Initialization requirements" section that says "All release-blocking images must boot in their supported configurations", and then at various points we refer back to that, including in the installer requirements where we say "each of these requirements applies to all supported configurations described above", and then in the installed system requirements where we say "each of these requirements applies to all supported configurations described above"
<@kparal:matrix.org>
17:13:30
hmm, so are you saying we only block on dedicated install images now, and no longer on netinst?
<@kparal:matrix.org>
17:13:43
that's different from what I think I remember from the past
<@conan_kudo:matrix.org>
17:13:47
we still block on netinst
<@conan_kudo:matrix.org>
17:13:50
that's why this is a problem
<@adamwill:fedora.im>
17:13:58
in the installer requirements we say "When installing with the generic network install image, interactively selecting a package set other than the default must work", but a footnote says ""Work" means that the mechanism for selecting different package sets must work: the packages in the set chosen must actually be correctly selected for installation. This particular criterion does not cover any errors in the available package sets, though other criteria may"
<@adamwill:fedora.im>
17:14:03
I would say it's ambiguous
<@adamwill:fedora.im>
17:14:10
netinst is a blocking image
<@adamwill:fedora.im>
17:14:25
but i'd say we only *clearly* block on a default package install from netinst
<@conan_kudo:matrix.org>
17:14:27
that... seems like a strange carveout
<@kparal:matrix.org>
17:14:38
if we block on netinst but don't block on any package set that can be selected, then we effectively... don't block on it?
<@adamwill:fedora.im>
17:14:41
(and default install of workstation live, kde live, etc etc - default install of all the blocking images)
<@m4rtink:fedora.im>
17:14:47
BTW, I would expect this to also fail for dir installation if it really needs some service or DBus interface to be available to install a package
<@adamwill:fedora.im>
17:15:02
but on the other hand, how do we limit it if we block on other installs from netinst?
<@adamwill:fedora.im>
17:15:06
you can install more or less *anything* from netinst
<@conan_kudo:matrix.org>
17:15:07
yeah, I don't think that's a reasonable carve-out
<@kparal:matrix.org>
17:15:08
hmm
<@adamwill:fedora.im>
17:15:17
clearly, we need to cover this better, anyway
<@conan_kudo:matrix.org>
17:15:30
we can condition on mapping to release-blocking environments
<@adamwill:fedora.im>
17:15:35
in the wording, to express whatever it is we want to mean
<@kparal:matrix.org>
17:15:39
I assumed we block on release-blocking package sets
<@conan_kudo:matrix.org>
17:15:42
e.g. Workstation, KDE, Server, Custom
<@adamwill:fedora.im>
17:15:50
i think desktop team does not want to 'support' workstation install from netinst, though
<@conan_kudo:matrix.org>
17:15:50
yes, exactly
<@adamwill:fedora.im>
17:15:56
pretty sure they've said that in the past
<@conan_kudo:matrix.org>
17:15:57
e.g. Workstation, KDE, Server, Custom/Minimal
<@conan_kudo:matrix.org>
17:16:50
afaik all release blocking deliverables are mapped to environment groups, so I don't see why they _wouldn't_ be considered blocking
<@adamwill:fedora.im>
17:16:58
btw, i have an install in the stuck state now, and `ps aux | grep dconf` doesn't show a running dconf update process...there's a dconf-service , but i think that's part of the installer env
<@adamwill:fedora.im>
17:18:24
aha, we're stuck in `/usr/bin/ibus write-cache --system` it looks like
<@kparal:matrix.org>
17:18:31
we have this explicit criterion: https://fedoraproject.org/wiki/Fedora_44_Final_Release_Criteria#Minimal_install
<@kparal:matrix.org>
17:18:38
based on that, I think Adam is currently right
<@m4rtink:fedora.im>
17:20:02
at least I don't see anything ibus related being purged in https://github.com/weldr/lorax/blob/master/share/templates.d/99-generic/runtime-cleanup.tmpl :)
<@m4rtink:fedora.im>
17:20:36
also no dconf stuff
<@adamwill:fedora.im>
17:20:47
added https://bugzilla.redhat.com/show_bug.cgi?id=2439813#c3
<@adamwill:fedora.im>
17:21:36
proposal: we punt on this and discuss on list / discourse
<@adamwill:fedora.im>
17:21:42
i think it's too fuzzy to decide in a meeting
<@conan_kudo:matrix.org>
17:22:22
+1
<@kparal:matrix.org>
17:22:34
ok
<@adamwill:fedora.im>
17:26:01
proposed !agreed 2439813 - punt (delay decision) - there's substantial sentiment that this ought to be blocking, but the current criteria don't clearly allow for that. whether the criteria should be adjusted to make this a blocker is a somewhat complex question we don't want to try and resolve live during a meeting, so we'll punt this to allow for more calm consideration of that
<@kparal:matrix.org>
17:26:25
ack
<@lruzicka:fedora.im>
17:26:28
ack
<@adamwill:fedora.im>
17:28:17
any more acks?
<@conan_kudo:matrix.org>
17:28:31
ack
<@korora:fedora.im>
17:28:54
ack
<@adamwill:fedora.im>
17:30:45
!agreed 2439813 - punt (delay decision) - there's substantial sentiment that this ought to be blocking, but the current criteria don't clearly allow for that. whether the criteria should be adjusted to make this a blocker is a somewhat complex question we don't want to try and resolve live during a meeting, so we'll punt this to allow for more calm consideration of that
<@adamwill:fedora.im>
17:31:00
!info Ticket vote: BetaBlocker (+2,0,-0) (+nielsenb, +psklenar)
<@adamwill:fedora.im>
17:31:00
!info Proposed Blocker, kernel, NEW
<@adamwill:fedora.im>
17:31:00
!link https://pagure.io/fedora-qa/blocker-review/issue/2047
<@adamwill:fedora.im>
17:31:00
!link https://bugzilla.redhat.com/show_bug.cgi?id=2441941
<@adamwill:fedora.im>
17:31:00
!topic (2441941) Graphics break when trying to type LUKS password
<@adamwill:fedora.im>
17:31:14
i don't think we should block on this if it's only known to affect a single system so far
<@adamwill:fedora.im>
17:31:30
that
<@adamwill:fedora.im>
17:31:39
that's much too high a bar to try and maintain
<@adamwill:fedora.im>
17:32:12
2438442 seems different as we have reports across multiple systems
<@adamwill:fedora.im>
17:32:49
well, hmm, i thought it had, but...looking closer...seems not so clear, maybe we shouldn't have waved that one through
<@psklenar:fedora.im>
17:33:15
both BZ#2441941 and BZ#2438442 identify a regression occurring between kernel versions 6.18 and 6.19. Debugging is currently difficult - Fedora QA does not have this specific hardware.
<@kparal:matrix.org>
17:33:52
I'd give this a week, and ask testers in test@ and in Discussion to post feedback, if they find an affected system
<@adamwill:fedora.im>
17:34:28
yeah, i think we should do a call for testing mentioning both bugs and asking folks to specify whether `i915.enable_psr=0` helps if they do have issues
<@adamwill:fedora.im>
17:34:52
that should clarify things a bit. and of course if someone can bisect it...
<@kparal:matrix.org>
17:34:59
we should also specify that they should test without any other monitor attached
<@adamwill:fedora.im>
17:35:03
(or at least just test past koji builds and get us the last good and first bad)
<@psklenar:fedora.im>
17:35:15
there is currently kernel test week, I added a note about that https://fedoraproject.org/wiki/Test_Day:2026-02-22_Kernel_6.19_Test_Week#known_bugs
<@kparal:matrix.org>
17:37:01
thanks. I fixed the formatting
<@adamwill:fedora.im>
17:39:20
proposed !agreed 2441941 - punt (delay decision) - so far this is only reported to affect one system. On a closer inspection, the similar-but-not-identical 2438442 which we previously accepted as a blocker has also only been reported to affect one model, so far. Blocking on bugs that affect only one laptop model is a bit of a high bar especially for Beta. we plan to issue a call for testing asking folks with Intel laptops to see if they hit either bug and then re-evaluate both bugs based on the responses
<@conan_kudo:matrix.org>
17:39:50
+1
<@korora:fedora.im>
17:40:07
+1
<@kparal:matrix.org>
17:40:25
ack
<@psklenar:fedora.im>
17:40:35
+1
<@psklenar:fedora.im>
17:41:12
do anyone know who is kernel qa to ask them for a help? maybe they have more hw ..
<@conan_kudo:matrix.org>
17:41:38
do we _have_ kernel qa?
<@conan_kudo:matrix.org>
17:41:47
as in specific people who do that
<@psklenar:fedora.im>
17:41:48
no idea :)
<@kparal:matrix.org>
17:41:54
fedora kernel team has only one person, which is justin forbes, afaik
<@conan_kudo:matrix.org>
17:42:29
yes
<@conan_kudo:matrix.org>
17:42:37
there are no other fedora kernel people currently
<@conan_kudo:matrix.org>
17:42:43
well, not officially anyway
<@adamwill:fedora.im>
17:43:06
i mean, rh probably has more folks we could ask, i have no idea who to poke after the last umpteen reorgs. i can see if brendan knows, or just pick some random list to mail
<@adamwill:fedora.im>
17:46:03
!agreed 2441941 - punt (delay decision) - so far this is only reported to affect one system. On a closer inspection, the similar-but-not-identical 2438442 which we previously accepted as a blocker has also only been reported to affect one model, so far. Blocking on bugs that affect only one laptop model is a bit of a high bar especially for Beta. we plan to issue a call for testing asking folks with Intel laptops to see if they hit either bug and then re-evaluate both bugs based on the responses
<@kashyapc:fedora.im>
17:47:00
Would a RISC-V SIG kernel person (Jason Montleon) count? :D
<@kashyapc:fedora.im>
17:47:56
Yeah, as Adam said, we can check w/ the Red Hat kernel team.
<@conan_kudo:matrix.org>
17:47:57
I'm not sure, actually
<@kparal:matrix.org>
17:48:07
we take anyone who's willing the invest the time and has enough skills 😉
<@conan_kudo:matrix.org>
17:48:18
not sure, but maybe :)
<@psklenar:fedora.im>
17:48:29
I will write to one of the mailing list what I have just found
<@kashyapc:fedora.im>
17:50:04
Petr Sklenar: For graphics stuff, Adam Jackson comes to mind. He's a long-time "Linux Graphics Person"
<@kparal:matrix.org>
17:51:08
adamw: time for FEs?
<@adamwill:fedora.im>
17:51:44
yes, sorry
<@adamwill:fedora.im>
17:51:45
multitasking
<@adamwill:fedora.im>
17:52:16
kashyapc we don't really need developers at this point, we need testers. once we have more information about what systems are affected and ideally what kernel build introduced the problem(s), we know how to contact developers.
<@adamwill:fedora.im>
17:52:41
!topic Proposed Beta Freeze Exceptions
<@adamwill:fedora.im>
17:52:52
!link https://bugzilla.redhat.com/show_bug.cgi?id=2434041
<@adamwill:fedora.im>
17:52:52
!link https://pagure.io/fedora-qa/blocker-review/issue/2044
<@adamwill:fedora.im>
17:52:52
!info Proposed Freeze Exceptions, fish, ON_QA
<@adamwill:fedora.im>
17:52:52
!topic (2434041) fish: FTBFS in Fedora rawhide/f44
<@adamwill:fedora.im>
17:52:52
!info Ticket vote: BetaFreezeException (+0,0,-1) (-nielsenb)
<@adamwill:fedora.im>
17:53:11
we usually grant FEs for simple FTI, but not FTBFS alone...
<@adamwill:fedora.im>
17:53:19
Conan Kudo is this FTI or just FTBFS?
<@conan_kudo:matrix.org>
17:56:22
it's just an FTBFS
<@adamwill:fedora.im>
17:56:35
i'm -1, in that case. no need for an FE.
<@conan_kudo:matrix.org>
17:56:39
I don't think it's an FTI atm
<@kparal:matrix.org>
17:57:08
-1
<@kparal:matrix.org>
17:59:24
for newcomers: FTBFS = fails to build from source, FTI = fails to install
<@psklenar:fedora.im>
17:59:35
-1
<@kparal:matrix.org>
17:59:50
this can be installed (the previous version), just a new version can't be currently built
<@kparal:matrix.org>
18:00:46
the devs can fix this after Beta is released and freeze is liften (until then it can be in updates-testing only)
<@conan_kudo:matrix.org>
18:01:15
yeah that's fine for this one
<@adamwill:fedora.im>
18:02:15
proposed !agreed 2434041 - RejectedFreezeException (Beta) - this is rejected on the basis that the package is still installable, and there's no real benefit from a freeze exception solely to fix the package build unless it's necessary to make the package installable or fix a significant bug
<@conan_kudo:matrix.org>
18:02:32
+1
<@kparal:matrix.org>
18:02:37
ack
<@conan_kudo:matrix.org>
18:02:45
ack
<@adamwill:fedora.im>
18:04:10
!agreed 2434041 - RejectedFreezeException (Beta) - this is rejected on the basis that the package is still installable, and there's no real benefit from a freeze exception solely to fix the package build unless it's necessary to make the package installable or fix a significant bug
<@kparal:matrix.org>
18:04:11
any more acks?
<@kparal:matrix.org>
18:04:15
we usually need 3
<@adamwill:fedora.im>
18:04:19
!info Ticket vote: BetaFreezeException (+1,0,-0) (+nielsenb)
<@adamwill:fedora.im>
18:04:19
!info Proposed Freeze Exceptions, gtk4, ON_QA
<@adamwill:fedora.im>
18:04:19
!link https://pagure.io/fedora-qa/blocker-review/issue/2041
<@adamwill:fedora.im>
18:04:19
!link https://bugzilla.redhat.com/show_bug.cgi?id=2440500
<@adamwill:fedora.im>
18:04:19
!topic (2440500) SVG texture heights are incorrect
<@adamwill:fedora.im>
18:04:37
yeah, but i don't wanna keep everyone sitting around for ever
<@adamwill:fedora.im>
18:04:59
the votes are more important than the acks
<@adamwill:fedora.im>
18:05:13
this one makes the tour you see on first boot after install look weird, so it's pretty visible
<@adamwill:fedora.im>
18:05:27
and it may well affect other things i didn't find yet, and it's a *very* obvious cause and fix
<@adamwill:fedora.im>
18:05:49
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/9476/diffs
<@conan_kudo:matrix.org>
18:06:07
yeah, also threw a +1 BetaFE in the ticket after looking it over
<@conan_kudo:matrix.org>
18:06:24
the fix is a one-liner too :)
<@adamwill:fedora.im>
18:06:46
ok, if i'm +1, that's +3
<@adamwill:fedora.im>
18:06:50
any other votes?
<@lruzicka:fedora.im>
18:07:29
+1
<@kparal:matrix.org>
18:07:34
+1
<@korora:fedora.im>
18:07:38
+1
<@adamwill:fedora.im>
18:10:00
proposed !agreed 2440500 - AcceptedFreezeException (Beta) - this is accepted as it's a very obvious fix that addresses at least one highly visible bug (the GNOME Tour window being oversized) and there may well be other cases we didn't spot yet that are worse (for a tall-but-narrow image we could wind up cutting off a lot of it)
<@kparal:matrix.org>
18:10:57
ack
<@conan_kudo:matrix.org>
18:11:57
ack
<@adamwill:fedora.im>
18:13:04
any nacks/patches?
<@adamwill:fedora.im>
18:14:27
!agreed 2440500 - AcceptedFreezeException (Beta) - this is accepted as it's a very obvious fix that addresses at least one highly visible bug (the GNOME Tour window being oversized) and there may well be other cases we didn't spot yet that are worse (for a tall-but-narrow image we could wind up cutting off a lot of it)
<@adamwill:fedora.im>
18:14:34
!info Ticket vote: BetaFreezeException (+0,0,-1) (-nielsenb)
<@adamwill:fedora.im>
18:14:34
!link https://pagure.io/fedora-qa/blocker-review/issue/2045
<@adamwill:fedora.im>
18:14:34
!info Proposed Freeze Exceptions, krita, ON_QA
<@adamwill:fedora.im>
18:14:34
!link https://bugzilla.redhat.com/show_bug.cgi?id=2441074
<@adamwill:fedora.im>
18:14:34
!topic (2441074) Update krita to 6.0.0 beta2
<@kparal:matrix.org>
18:16:02
+1 FE for the design suite
<@kparal:matrix.org>
18:16:19
without it, I would be -1, because updates-testing is enabled by default
<@adamwill:fedora.im>
18:16:37
what is the impact of "mlt was updated shortly before Beta freeze with a change that dropped Qt5 support. As the only remaining Qt5 consumer of mlt, krita 5 is particularly impacted, and provides an additional impetus to migrate early"?
<@adamwill:fedora.im>
18:16:46
what does mlt do? what can't krita do without it?
<@kparal:matrix.org>
18:18:15
shotcut uses mlt to orchestrate the video transcode process. I have no idea what krita uses it for.
<@conan_kudo:matrix.org>
18:18:30
same thing
<@conan_kudo:matrix.org>
18:18:38
it uses it for transforms, effects, animations, etc.
<@conan_kudo:matrix.org>
18:19:16
and it can process and let you edit video frames
<@adamwill:fedora.im>
18:19:55
ok, i guess if it's in design suite, fine. and if it's not in KDE by default, if the update happens to eat babies it can't be a release blocker...
<@adamwill:fedora.im>
18:20:05
+1
<@adamwill:fedora.im>
18:20:33
that's +4 / -1, any other votes?
<@adamwill:fedora.im>
18:20:48
(the -1 was before 'it's default in design suite' was known, for the record)
<@adamwill:fedora.im>
18:23:05
proposed !agreed 2441074 - AcceptedFreezeException (Beta) - this is accepted as it's a significant functionality problem in a default app on a non-blocking spin (Design Suite)
<@kparal:matrix.org>
18:23:23
ack
<@conan_kudo:matrix.org>
18:25:02
ack
<@kparal:matrix.org>
18:26:13
it we've lost everyone else
<@kparal:matrix.org>
18:26:22
give it your ack, Adam, and we can move on
<@adamwill:fedora.im>
18:26:44
ok
<@adamwill:fedora.im>
18:26:50
!agreed 2441074 - AcceptedFreezeException (Beta) - this is accepted as it's a significant functionality problem in a default app on a non-blocking spin (Design Suite)
<@lruzicka:fedora.im>
18:26:56
ack
<@adamwill:fedora.im>
18:27:00
!topic (2435519) OCR functionality in Spectacle does not work unless tesseract-devel is installed (due to bad library discovery code in Spectacle)
<@adamwill:fedora.im>
18:27:00
!link https://bugzilla.redhat.com/show_bug.cgi?id=2435519
<@adamwill:fedora.im>
18:27:00
!link https://pagure.io/fedora-qa/blocker-review/issue/2043
<@adamwill:fedora.im>
18:27:00
!info Proposed Freeze Exceptions, spectacle, ON_QA
<@adamwill:fedora.im>
18:27:00
!info Ticket vote: BetaFreezeException (+1,0,-0) (+nielsenb)
<@kparal:matrix.org>
18:27:05
it seems we've lost everyone else
<@adamwill:fedora.im>
18:27:27
minor penalty, ruzicka, two minutes for late ack'ing
<@ngompa:fedora.im>
18:27:46
there's a sync issue with matrix.org
<@adamwill:fedora.im>
18:27:55
oh, well. this is the last issue anyway...
<@adamwill:fedora.im>
18:28:46
eh, I think describing OCR as 'core functionality' of a screenshot tool is pushing it a bit
<@kparal:matrix.org>
18:29:01
I see that my comments are sometimes lagging
<@ngompa:fedora.im>
18:29:05
it's more that it's literally a flagship feature on the Plasma 6.6 release page
<@kparal:matrix.org>
18:29:41
I'm +1 FE, it fixes a bug, and it's not a release-blocking app
<@kparal:matrix.org>
18:29:49
so any regressions shouldn't be a problem
<@ngompa:fedora.im>
18:31:15
spectacle is releaseblocking for KDE
<@adamwill:fedora.im>
18:31:16
well, that's not the guidelines we usually go by? on that basis we should give an FE to any update that we think is not 'release-blocking', pretty much...
<@ngompa:fedora.im>
18:31:18
it's a core function
<@adamwill:fedora.im>
18:31:38
well, it can't work both ways...
<@ngompa:fedora.im>
18:32:38
it's a core app
<@ngompa:fedora.im>
18:33:28
I filed it as an FE because we don't have OCR criterion
<@kparal:matrix.org>
18:33:34
Neal Gompa (Fedora): we have this https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Default_application_functionality
<@kparal:matrix.org>
18:33:40
and this: https://fedoraproject.org/wiki/Fedora_43_Final_Release_Criteria#Default_panel_functionality
<@lruzicka:fedora.im>
18:34:40
I have been fighting with power outages all day long, plus in the meantime with no power, I rewired internet and now, when power is back on, I am fighting internet outages :D
<@lruzicka:fedora.im>
18:35:15
Oh my, I wish I paid more attention when doing networking at university.
<@kparal:matrix.org>
18:35:27
IIUI that spectacle is a screenshot tool, it probably doesn't fit, unless it's available from the system panel
<@ngompa:fedora.im>
18:35:42
it's triggered from the system function print screen?
<@ngompa:fedora.im>
18:35:48
it's triggered from the button print screen?
<@ngompa:fedora.im>
18:35:59
and its default behavior is a shell overlay
<@ngompa:fedora.im>
18:36:04
but yeah, I dunno
<@ngompa:fedora.im>
18:36:31
I didn't see an obvious criterion, so I went with an FE, especially since this function was highlighted in the release announcement for Plasma 6.6
<@kparal:matrix.org>
18:36:56
I'm still +1 FE
<@kparal:matrix.org>
18:37:10
adamw: your vote?
<@adamwill:fedora.im>
18:37:51
ehh, fine, i guess +1
<@adamwill:fedora.im>
18:40:57
it's more or less up to you what you want to cover in the list
<@adamwill:fedora.im>
18:41:32
proposed !agreed 2435519 - AcceptedFreezeException (Beta) - this is accepted as the fix for a major new feature of a default KDE application
<@kparal:matrix.org>
18:41:56
ack
<@kparal:matrix.org>
18:43:01
come up, folks, please vote
<@kparal:matrix.org>
18:43:06
come on, folks, please vote
<@ngompa:fedora.im>
18:43:25
ack
<@jgroman:fedora.im>
18:43:32
ack
<@psklenar:fedora.im>
18:43:44
ack
<@adamwill:fedora.im>
18:43:54
!agreed 2435519 - AcceptedFreezeException (Beta) - this is accepted as the fix for a major new feature of a default KDE application
<@adamwill:fedora.im>
18:43:58
okay! i guess that's it
<@adamwill:fedora.im>
18:44:10
well, we can do a quick spin through:
<@adamwill:fedora.im>
18:44:17
!topic Accepted Beta Blockers
<@adamwill:fedora.im>
18:44:25
!info as a reminder, we're checking status, not re-voting
<@adamwill:fedora.im>
18:44:31
!link https://pagure.io/fedora-qa/blocker-review/issue/2028
<@adamwill:fedora.im>
18:44:31
!info Accepted Blocker, kernel, NEW
<@adamwill:fedora.im>
18:44:31
!link https://bugzilla.redhat.com/show_bug.cgi?id=2438442
<@adamwill:fedora.im>
18:44:31
!topic (2438442) Graphics broken unless Panel Self Refresh is disabled (with i915.enable_psr=0)
<@adamwill:fedora.im>
18:44:43
!info we decided earlier in the meeting to do a call for testing on this one along with the new one
<@kparal:matrix.org>
18:44:47
adamw: I've done the secretary stuff
<@adamwill:fedora.im>
18:44:50
thanks
<@adamwill:fedora.im>
18:45:30
!info jforbes says a bisect would be very valuable if anyone with an affected system can do it (even just identifying the last good / first broken kernel builds in koji would help)
<@adamwill:fedora.im>
18:45:35
!link https://pagure.io/fedora-qa/blocker-review/issue/2036
<@adamwill:fedora.im>
18:45:35
!link https://bugzilla.redhat.com/show_bug.cgi?id=2438907
<@adamwill:fedora.im>
18:45:35
!topic (2438907) [abrt] gnome-shell: meta_wayland_popup_grab_finish(): gnome-shell killed by SIGSEGV
<@adamwill:fedora.im>
18:45:35
!info Accepted Blocker, mutter, ON_QA
<@adamwill:fedora.im>
18:45:47
fix for this is in testing, please test and karma it so we can push it stable
<@adamwill:fedora.im>
18:45:53
!info fix for this is in testing, please test and karma it so we can push it stable
<@jforbes:fedora.im>
18:46:14
I can see if one of these laptops I have is meteor lake.
<@jforbes:fedora.im>
18:47:17
Pretty sure I don't have any meteor lake though, only lunar lake
<@ngompa:fedora.im>
18:48:25
alas I don't have anything that new Intel-wise
<@adamwill:fedora.im>
18:50:05
me either
<@adamwill:fedora.im>
18:50:11
!topic Open floor
<@adamwill:fedora.im>
18:50:18
alrighty, that's everything, I think - did I miss anything?
<@ngompa:fedora.im>
18:51:06
nope
<@ngompa:fedora.im>
18:51:19
this will be the first cycle with forgejo for freeze pushes though
<@adamwill:fedora.im>
18:55:12
shouldn't make any difference, really. i might need to update an SOP somewhere though...
<@adamwill:fedora.im>
18:56:01
cya
<@adamwill:fedora.im>
18:56:06
thanks for coming, everyone
<@adamwill:fedora.im>
18:56:07
!endmeeting