16:02:40 <adamw> #startmeeting F39-blocker-review
16:02:40 <zodbot> Meeting started Mon Sep 25 16:02:40 2023 UTC.
16:02:40 <zodbot> This meeting is logged and archived in a public location.
16:02:40 <zodbot> The chair is adamw. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
16:02:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:02:40 <zodbot> The meeting name has been set to 'f39-blocker-review'
16:02:40 <adamw> #meetingname F39-blocker-review
16:02:40 <zodbot> The meeting name has been set to 'f39-blocker-review'
16:02:40 <adamw> #topic Roll Call
16:02:42 <aoife> Hi everyone!
16:04:01 <geraldosimiao> .hello geraldosimiao
16:04:03 <zodbot> geraldosimiao: geraldosimiao 'Geraldo S. Simião Kutz' <geraldo.simiao.kutz@gmail.com>
16:04:18 <adamw> hi geraldo
16:04:32 <Son_Goku> .hello ngompa
16:04:33 <geraldosimiao> hi adam :)
16:04:33 <zodbot> Son_Goku: ngompa 'Neal Gompa' <ngompa13@gmail.com>
16:04:38 <Son_Goku> Yo.
16:04:42 <lruzicka> .hello lruzicka
16:04:43 <zodbot> lruzicka: lruzicka 'Lukáš Růžička' <lruzicka@redhat.com>
16:04:47 <adamw> hi hi hi
16:04:50 <thebeanogamer> .hello thebeanogamer
16:04:51 <zodbot> thebeanogamer: thebeanogamer 'Daniel Milnes' <daniel@daniel-milnes.uk>
16:04:55 <geraldosimiao> oh hello neal, the guy from the 2h interview
16:05:02 <davdunc> .hello davdunc
16:05:04 <zodbot> davdunc: davdunc 'David Duncan' <davdunc@amazon.com>
16:05:04 <geraldosimiao> ;)
16:05:21 <aleasto> .hello2
16:05:22 <zodbot> aleasto: aleasto 'Alessandro Astone' <ales.astone@gmail.com>
16:05:26 <coremodule> .hello2
16:05:27 <zodbot> coremodule: coremodule 'Geoffrey Marr' <gmarr@redhat.com>
16:07:53 <adamw> welcome welcome
16:07:56 <adamw> let's get started!
16:08:10 <aoife> .hello aoife
16:08:13 <zodbot> aoife: Sorry, but user 'aoife' does not exist
16:08:33 <aoife> of course I dont
16:08:41 <davdunc> if you believe hard enough . . .
16:09:14 <lruzicka> aoife, try with your FAS :D
16:09:17 <adamw> #chair davdunc coremodule
16:09:17 <zodbot> Current chairs: adamw coremodule davdunc
16:09:28 <adamw> impending boilerplate alert!
16:09:31 <adamw> #topic Introduction
16:09:31 <adamw> Why are we here?
16:09:31 <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:09:31 <adamw> #info We'll be following the process outlined at:
16:09:31 <adamw> #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
16:09:32 <adamw> #info The bugs up for review today are available at:
16:09:34 <adamw> #link http://qa.fedoraproject.org/blockerbugs/current
16:09:36 <adamw> #info The criteria for release blocking bugs can be found at:
16:09:38 <adamw> #link https://fedoraproject.org/wiki/Basic_Release_Criteria
16:09:42 <adamw> #link https://fedoraproject.org/wiki/Fedora_39_Beta_Release_Criteria
16:09:44 <adamw> #link https://fedoraproject.org/wiki/Fedora_39_Final_Release_Criteria
16:09:50 <adamw> #for F39 Final, we have:
16:09:51 <adamw> #info 5 Proposed Blockers
16:09:52 <adamw> #info 1 Accepted Blockers
16:09:56 <adamw> #info 6 Proposed Freeze Exceptions
16:10:08 <adamw> who wants to secretarialize?
16:10:27 * coremodule will do it.
16:11:18 <adamw> roger roger
16:11:24 <adamw> #info coremodule will secretarialize
16:11:29 <adamw> so without further ado, let's get started with:
16:11:35 <adamw> #topic Proposed Final blockers
16:11:46 <adamw> #topic (2239213) anaconda should use localed layout conversion when setting default console layout
16:11:46 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2239213
16:11:46 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1339
16:11:46 <adamw> #info Proposed Blocker, anaconda, POST
16:11:46 <adamw> #info Ticket vote: FinalBlocker (+2,0,-0) (+geraldosimiao, +bcotton)
16:12:04 <adamw> so welcome to the Adam's Getting Het Up About Keyboard Layouts Again show
16:12:14 <adamw> and also, apologies to all Bulgarian Fedora fans
16:13:03 <adamw> this has been around for a while without anybody getting too mad about it (at least in a language and/or forum that any of us have noticed!), but it does kinda quite clearly violate the criteria, at least for a few languages
16:14:45 <adamw> i guess it might *possibly* not pass the last blocker test if we found it the day before shipping, but eh. i do have the fixes ready to go
16:15:17 <lruzicka> it feels like an unhappy thing when it happens
16:15:21 <lruzicka> +1 fb
16:16:42 <coremodule> +1 FB here too
16:17:04 <adamw> ok, with the ticket votes that's enough...
16:17:44 <adamw> proposed #agreed 2239213 - AcceptedBlocker (Final) - this is accepted as a violation of "If a particular keyboard layout has been configured for the system, that keyboard layout must be used: ... When logging in at a console" in the case of Bulgarian and Kazakh layouts
16:17:55 <lruzicka> ack
16:18:00 <coremodule> ack
16:19:01 <geraldosimiao> ack
16:20:07 <adamw> #agreed 2239213 - AcceptedBlocker (Final) - this is accepted as a violation of "If a particular keyboard layout has been configured for the system, that keyboard layout must be used: ... When logging in at a console" in the case of Bulgarian and Kazakh layouts
16:20:15 <adamw> #topic (2239128) pop-up screen is stuck when try to  format a partition
16:20:15 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2239128
16:20:15 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1342
16:20:15 <adamw> #info Proposed Blocker, blivet-gui, NEW
16:20:15 <adamw> #info Ticket vote: FinalBlocker (+1,0,-0) (+imsedgar)
16:21:01 <adamw> hum
16:21:07 <adamw> seems a bit tricky, like there's timing involved
16:23:59 <lruzicka> According to the Bugzilla, it does not happen all the time and it can easily be workarounded with the Esc key and tried again. I think CommonBugs could be enough?
16:24:43 <geraldosimiao> looks like a commonbugs yeah
16:25:00 <adamw> figuring out that you can hit esc might be a bit tricky
16:25:14 <adamw> (for all the people who don't read commonbugs)
16:25:23 <adamw> we could say punt for more testing, but then we need people to test...:D
16:25:48 <lruzicka> I can test that tomorrow.
16:27:17 <adamw> so, let's give it a shot at least...
16:28:08 <adamw> proposed #agreed 2239128 - punt (delay decision) - per @kparal it seems this might be a timing issue and it would be good for other folks to test and see if they're affected and if so, how often (and maybe get some feedback from the devs). so let's punt this for a week at least
16:28:19 <geraldosimiao> ack
16:29:30 <coremodule> ack
16:31:06 <geraldosimiao_IR> oh man, IRC don't like me... :(
16:32:25 <adamw> any more acks?
16:33:20 <adamw> i guess two is fine!
16:33:23 <adamw> agreed 2239128 - punt (delay decision) - per @kparal it seems this might be a timing issue and it would be good for other folks to test and see if they're affected and if so, how often (and maybe get some feedback from the devs). so let's punt this for a week at least
16:33:25 <adamw> grr
16:33:27 <adamw> #agreed 2239128 - punt (delay decision) - per @kparal it seems this might be a timing issue and it would be good for other folks to test and see if they're affected and if so, how often (and maybe get some feedback from the devs). so let's punt this for a week at least
16:33:34 <adamw> #topic (2239426) Displayed keymap on the login screen is often wrong
16:33:34 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2239426
16:33:34 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1336
16:33:34 <adamw> #info Proposed Blocker, sddm, NEW
16:33:34 <adamw> #info Ticket vote: FinalBlocker (+1,0,-0) (+geraldosimiao)
16:34:08 * aleasto takes the floor
16:34:36 <aleasto> so the sddm keyboard switcher has been a noop since we shipepd f38
16:34:59 <geraldosimiao_IR> yeah
16:35:02 <aleasto> we've merged the change upstream to remove the button
16:35:25 <aleasto> it will correctly use the layout(s) set at setup through `locale1`
16:35:56 <aleasto> i have a MR open with the patch https://src.fedoraproject.org/rpms/sddm/pull-request/8
16:36:09 <aleasto> i'll bring it up in the KDE SIG meeting in 25 minutes
16:36:21 <lruzicka> this feels blockery for me
16:37:14 <adamw> yeah...technically the layout selected is used, but a big indicator saying it *isn't* used is sure confusing...
16:37:28 <aleasto> sure
16:37:39 <aleasto> also you can select another layout but nothing will change ^^
16:38:42 <lruzicka> that's even trickier :D
16:38:53 <adamw> yeah
16:39:16 <adamw> okay, i'll vote +1 i guess, based on a slightly creative reading of that criterion :D again this might not quite pass the last blocker test, but...never mind
16:39:27 <lruzicka> +1 fb, too
16:39:46 <Son_Goku> we're removing the stuff that makes it look confusing, which should resolve this for now, no?
16:41:58 <lruzicka> Son_Goku, which will fix the Final Blocker, sure. But it is still a blocker, aint it?
16:42:46 <adamw> Son_Goku: aiui, the removal is the intended fix for the bug.
16:42:57 <adamw> but it's only 'merged upstream', which is not downstream. yet.
16:43:01 <Son_Goku> okay, so we're on the same page then
16:43:28 <Son_Goku> I'll land the fix and ship an update today
16:46:01 <adamw> alright, we have +3
16:46:53 <adamw> proposed #agreed 2239426 - AcceptedBlocker (Final) - it's a slight stretch, but we view this as an effective violation of the keyboard layout criterion: the layout chosen during install *is* used, but a prominent indicator says it isn't, which is very confusing. also, attempting to switch using the indicator doesn't work
16:47:05 <geraldosimiao_IR> ack
16:47:14 <lruzicka> ack
16:47:22 <Son_Goku> ack
16:48:41 <adamw> #agreed 2239426 - AcceptedBlocker (Final) - it's a slight stretch, but we view this as an effective violation of the keyboard layout criterion: the layout chosen during install *is* used, but a prominent indicator says it isn't, which is very confusing. also, attempting to switch using the indicator doesn't work
16:48:52 <adamw> siiigh. do leading spaces work? i don't know. can I type? clearly not
16:48:54 <adamw> #agreed 2239426 - AcceptedBlocker (Final) - it's a slight stretch, but we view this as an effective violation of the keyboard layout criterion: the layout chosen during install *is* used, but a prominent indicator says it isn't, which is very confusing. also, attempting to switch using the indicator doesn't work
16:49:04 <adamw> #topic (2239121) the second part of btrfs volume is shown as not-mounted
16:49:04 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2239121
16:49:04 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1335
16:49:04 <adamw> #info Proposed Blocker, util-linux, NEW
16:49:04 <adamw> #info Ticket vote: FinalBlocker (+0,0,-1) (-kparal)
16:51:58 <adamw> debates! i love debates
16:52:07 <lruzicka> Hmm, I believe that this one is quite similar to what we just have had with the keyboard indicator.
16:52:19 <lruzicka> But the risk is more severe.
16:52:25 <lruzicka> +1 FB
16:52:29 <adamw> but the situation is less common, i guess...
16:52:48 <adamw> well, i don't really know, since telemetry is evil so we are doomed to never have any idea how anyone actually uses our stuff
16:53:09 <lruzicka> sure, I understand
16:53:36 <Son_Goku> 😦
16:54:13 * Son_Goku is confused why all these are coming up now
16:54:17 <adamw> i think the gnome-disks case is the most plausible for a blocker vote
16:54:27 <adamw> just lili doing her best kparal impression i think :)
16:54:46 <Son_Goku> is she a new QE/QA person?
16:54:53 <adamw> no, she's been around for years
16:55:17 <lruzicka> Son_Goku, no, but I guess her child is more independent now and she has time to test more.
16:55:23 <adamw> she was with us at flock, you probably met her...
16:55:55 <Son_Goku> ah
16:55:58 <lruzicka> Son_Goku, she does various testing stuff with a bunch of media, that we do not have in Brno
16:56:40 <lruzicka> Son_Goku, so that's probably why these things show up now
16:56:41 <adamw> i might want input from the gnome-disks devs about how practical it is to fix this, i guess it might be the case they just get the info from the kernel or util-linux or whatever...
16:57:14 <adamw> i kiinda lean -1 on this just because it's not new and hasn't caused major problems so far as we know, but it does seem close
16:57:38 <lruzicka> I am +1 punt and see what the devs think about it
16:57:55 <Son_Goku> +1 punt
16:59:00 <adamw> proposed #agreed 2239121 - punt (delay decision) - we would like to ask the GNOME Disks developers (and possibly util-linux too) for their opinion on this bug and how practical it is to try and address it
17:00:05 <lruzicka> ack
17:00:10 <coremodule> ack
17:01:38 <adamw> #agreed 2239121 - punt (delay decision) - we would like to ask the GNOME Disks developers (and possibly util-linux too) for their opinion on this bug and how practical it is to try and address it
17:01:54 <geraldosimiao_IR> ack
17:01:59 <adamw> #topic (2240211) Fonts, maximize buttons, cursor size settings not applied in "GTK" Flatpaks
17:01:59 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2240211
17:02:00 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1344
17:02:00 <adamw> #info Proposed Blocker, xdg-desktop-portal, NEW
17:02:00 <adamw> #info Ticket vote: FinalBlocker (+1,0,-0) (+geraldosimiao)
17:03:06 <Son_Goku> ugh
17:03:15 <Son_Goku> I think this is the result of xdp being upgraded to 1.18
17:03:17 <adamw> this does seem quite bad...not sure if it's quite a blocker, after all it could be fixed fine with an update...
17:04:48 <lruzicka> but it probably looks awful when you hit it and you'd need to live with that until the update fixes it :D
17:05:49 <adamw> " This is breaking basic display settings for GTK based Flatpaks in a KDE session." - that's...not a release criterion
17:06:07 <adamw> i think unless someone can come up with some good criteria judo i'm -1 on this one
17:06:56 <aleasto> maybe... `maximize buttons are missing` ?
17:07:01 <geraldosimiao_IR> but can we garantee a FE for it? in case the upgrade don't come before freeze?
17:07:36 <geraldosimiao_IR> I think only exit button are on
17:07:44 <geraldosimiao_IR> other ones are missing
17:08:23 <adamw> aleasto: this is also not a release criterion
17:08:28 <adamw> otherwise we would never release Workstation...:P
17:08:43 <geraldosimiao_IR> ;)
17:08:45 <aleasto> haha right
17:09:12 <adamw> the closest criterion is "For each release-blocking desktop, the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable), windows switching, using windows on virtual workspaces, and similar common operations as expected. Common application content such as regular application windows, video output, and games must be displayed
17:09:12 <adamw> correctly.", I guess
17:09:27 <adamw> you could *argue* this as a conditional violation of that, but i'd still be inclined to -1 personally. but everyone gets a vote!
17:09:36 <Son_Goku> I'm iffy, leaning +1
17:09:42 <adamw> FE status...the question is, what is the benefit of giving this an FE?
17:09:53 <Son_Goku> Kinoite images are stuck for life with this problem :/
17:09:59 <adamw> given that by the time you get any flatpaks installed you should be able to update the system...
17:10:04 <lruzicka> According to that criterion +1 FB
17:10:38 <adamw> how would kinoite be stuck for life? we ship updates don't we?
17:11:02 <aleasto> wait is the gtk portal only used by flatpaks?
17:11:41 <geraldosimiao_IR> I guess no
17:12:08 <aleasto> geraldosimiai_IR: do you know if this only affects flatpak or also system gtk apps?
17:12:08 <geraldosimiao_IR> because I faced this problem on other gtk apps, rpms ones
17:12:13 <aleasto> yea that's what i thought
17:12:29 <geraldosimiao_IR> even firefox is affected
17:12:50 <Son_Goku> it affects Firefox
17:12:54 <geraldosimiao_IR> yeah
17:13:15 <Son_Goku> adamw: hmm I guess, but not update images :(
17:13:19 <geraldosimiao_IR> and abrt, and all other gtk apps on plasma
17:14:13 <adamw> Son_Goku: well sure, but the kinoite installer isn't live? i guess you'd have the issue if you just installed straight from the installer then ran some flatpaks before updating the system, but that's just the same as with any other image, including the live...
17:14:25 <Son_Goku> hmm, I guess
17:14:29 <adamw> oh, if it affects preinstalled GTK apps i'm a lot more +1
17:14:34 <aleasto> yep
17:14:35 <adamw> i was assuming it was flatpak-only
17:14:39 <adamw> ok, then changing to +1\
17:14:41 <Son_Goku> nope, it affects everything because Wayland
17:15:57 <adamw> proposed #agreed 2240211 - AcceptedBlocker (Final) - this is accepted as a violation of "... the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable)..." in the case of OOTB-installed GTK applications, e.g. Firefox
17:16:06 <lruzicka> ack
17:16:12 <coremodule> ack
17:17:38 <Son_Goku> ack
17:17:44 <adamw> #agreed 2240211 - AcceptedBlocker (Final) - this is accepted as a violation of "... the desktop environment must perform regular operations like windows close/resize/maximize/minimize/fullscreen (when supported/applicable)..." in the case of OOTB-installed GTK applications, e.g. Firefox
17:17:57 <adamw> OK, that's all the proposed blockers, moving on to...
17:18:03 <adamw> #topic Proposed Final freeze exceptions
17:18:12 <adamw> #topic (2234638) Installation of the system fails when using `inst.sdboot` on anything but network install images
17:18:12 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2234638
17:18:12 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1337
17:18:12 <adamw> #info Proposed Freeze Exceptions, anaconda, ASSIGNED
17:18:43 <adamw> I believe this is proposed for the work planned to make the feature work on the Server DVD and hide it on lives...
17:19:00 <adamw> (I guess we might also want to hide it on ostree installer images, now I think about it?)
17:20:55 <Son_Goku> yeah
17:22:01 <adamw> specifically, i proposed it for FE so anaconda team have 'justification' to include the anaconda patch(es), since they only merge fe/blocker fixes after beta freeze.
17:22:58 <lruzicka> +1 fe
17:23:04 <Son_Goku> +1 FE
17:23:30 <geraldosimiao_IR> +1 fe
17:26:13 <adamw> proposed #agreed 2234638 - AcceptedFreezeException (Final) - this is accepted as it would be good to have this Change working in all environments where it can (netinsts and the Server DVD) and disabled in environments where it can't (lives, ostrees?)
17:26:28 <geraldosimiao_IR> ack
17:26:45 <lruzicka> ack
17:28:51 <Son_Goku> ack
17:29:08 <adamw> #agreed 2234638 - AcceptedFreezeException (Final) - this is accepted as it would be good to have this Change working in all environments where it can (netinsts and the Server DVD) and disabled in environments where it can't (lives, ostrees?)
17:29:16 <adamw> #topic (2237327) btrfs flags are missing when using  inst.sdboot option.
17:29:16 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2237327
17:29:16 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1347
17:29:16 <adamw> #info Proposed Freeze Exceptions, anaconda, POST
17:35:01 <adamw> did everybody fall asleep
17:35:09 <lruzicka> no, sorry
17:35:14 <lruzicka> fe +1
17:37:21 <coremodule> +1FE
17:37:29 <geraldosimiao_IR> +1 fe
17:38:33 <adamw> proposed #agreed 2237327 - AcceptedFreezeException (Final) - this is an issue in an F39 Change that cannot be fixed with a post-release update, and the fix is pretty isolated to the systemd-boot code in the installer so can't break anything else
17:40:26 <lruzicka> ack
17:41:51 <geraldosimiao_IR> ack
17:42:20 <Son_Goku> ack
17:42:41 <adamw> #agreed 2237327 - AcceptedFreezeException (Final) - this is an issue in an F39 Change that cannot be fixed with a post-release update, and the fix is pretty isolated to the systemd-boot code in the installer so can't break anything else
17:42:56 <adamw> #topic (2237396) Failed to create task for container: failed to create shim task: ttrpc: cannot marshal unknown type: *task.CreateTaskRequest: unknown
17:42:56 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2237396
17:42:56 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1345
17:42:56 <adamw> #info Proposed Freeze Exceptions, containerd, NEW
17:44:51 <adamw> oh, this is the 'docker doesn't work' bug, right?
17:45:00 <lruzicka> it looks like this
17:46:03 <lruzicka> +1 fe
17:46:07 <adamw> again, not sure what the justification for an FE specifically is
17:46:10 <adamw> why can it not be a 0-day
17:46:42 <lruzicka> it would look bad if someone does not update after installation
17:47:26 <adamw> well, so would *any* bug, we don't give them all FEs...
17:47:40 <adamw> podman doesn't use containerd, right?
17:48:07 <adamw> so, is containerd even on any frozen media?
17:49:35 <adamw> on the whole i'm -1 without clearer justification
17:50:51 <lruzicka> I am not sure, let's check
17:52:02 <Son_Goku> it shouldn't be on anything except CoreOS
17:52:09 <Son_Goku> since moby-engine depends on it
17:52:34 <adamw> oh, we ship moby on coreos?
17:52:44 <Son_Goku> yes
17:53:23 <lruzicka> it's not on Workstation, confirmed
17:55:02 <adamw> for coreos...well, i guess there's kinda a case to fix it, then, but otoh, coreos has its own release cadence and filters...have they even pulled this in, or did they catch the problem and pin it to an older version?
18:00:02 <adamw> i think i'm -1 at least until there's a clearer proposal
18:00:04 <adamw> other votes?
18:01:01 <geraldosimiao_IR> punt +1
18:01:52 <geraldosimiao_IR> because for now I'm FE +0
18:01:58 <Son_Goku> punt +1
18:02:02 <Son_Goku> though I lean FE +1
18:02:10 <lruzicka> punt is ok +1
18:02:14 <adamw> that sounds like it adds up to punt...
18:03:05 <adamw> proposed #agreed 2237396 - punt (delay decision) - we would like a clearer rationale for why it would be beneficial to grant an FE to this bug, given that containerd is not used by podman and probably isn't on any media aside from CoreOS. what does an FE achieve here that a 0-day update would not?
18:03:19 <lruzicka> ack
18:03:28 <Son_Goku> ack
18:04:49 <adamw> #agreed 2237396 - punt (delay decision) - we would like a clearer rationale for why it would be beneficial to grant an FE to this bug, given that containerd is not used by podman and probably isn't on any media aside from CoreOS. what does an FE achieve here that a 0-day update would not?
18:05:00 <geraldosimiao_IR> ack
18:05:01 <adamw> #topic (2238985) the system is almost unusable when low-disk-space pops up
18:05:01 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2238985
18:05:01 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1333
18:05:01 <adamw> #info Proposed Freeze Exceptions, gnome-settings-daemon, NEW
18:07:34 <lruzicka> To hit this, you'd have to be quite unlucky, this could be a part of 0-day updates ... or any updates.
18:07:49 <lruzicka> -1 FE
18:07:58 <adamw> i wonder if it's related to all the other btrfs space issues lili found...
18:08:15 <adamw> (i.e. it might kinda depend on the size of disk and stuff...)
18:08:52 <adamw> yeah, i agree that FE doesn't seem sensible, it's kinda natural that you wouldn't start running out of disk space till after you'd usually have updated the system...
18:12:01 <adamw> anyone else?
18:12:39 <geraldosimiao_IR> -1 FE
18:14:18 <adamw> proposed #agreed 2238985 - RejectedFreezeException (Final) - this is rejected for now as we don't see how an FE would benefit versus a 0-day update here; typically if you're running out of disk space it would be after using the system for a while, not immediately after install
18:15:06 <geraldosimiao_IR> ack
18:16:46 <lruzicka> ack
18:17:13 <adamw> #agreed 2238985 - RejectedFreezeException (Final) - this is rejected for now as we don't see how an FE would benefit versus a 0-day update here; typically if you're running out of disk space it would be after using the system for a while, not immediately after install
18:17:24 <adamw> #topic (2239111) low-disk-space warning message pops up pretty slow when the /home (btrfs volume ) is out of space
18:17:24 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2239111
18:17:24 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1334
18:17:24 <adamw> #info Proposed Freeze Exceptions, gnome-settings-daemon, NEW
18:17:58 <adamw> this sounds kinda...similar?
18:20:45 <geraldosimiao_IR> yeah
18:21:37 <lruzicka> yeah, and similarly I am -1 FE
18:22:07 <adamw> yeah, same again, -1 for now
18:22:23 <geraldosimiao_IR> -1 FE
18:23:28 <adamw> proposed #agreed 2239111 - RejectedFreezeException (Final) - similar to the previous bug, we don't see immediately that bugs in low free space notification are good FE candidates since they should be addressable with updates
18:23:33 <lruzicka> ack
18:27:16 <adamw> any more acks
18:28:54 <adamw> let's just go with it
18:28:57 <adamw> #agreed 2239111 - RejectedFreezeException (Final) - similar to the previous bug, we don't see immediately that bugs in low free space notification are good FE candidates since they should be addressable with updates
18:29:06 <adamw> #topic (2238905) F39 workstation's Displays Scale is 125% by default on 1920x1080 14" laptop display
18:29:06 <adamw> #link https://bugzilla.redhat.com/show_bug.cgi?id=2238905
18:29:06 <adamw> #link https://pagure.io/fedora-qa/blocker-review/issue/1331
18:29:06 <adamw> #info Proposed Freeze Exceptions, mutter, NEW
18:29:08 <adamw> okay, last one
18:29:47 <adamw> there's a bunch of concerns about the fractional scaling change now it's landed, this one as titled is about fractional scales being autodetected, which in practice means a lot more people will be using non-100% scaling...
18:30:25 <adamw> i feel like i can vote a kinda general +1 to "if we do decide to make conservative changes to the fractional scaling stuff, we should give that an FE in general"
18:30:40 <adamw> that is, changes to make it less 'aggressive' and more like the previous state
18:31:36 <lruzicka> sure, +1 fe
18:32:35 <adamw> anyone else still awake? :D
18:33:13 <lruzicka> seems like it's hard to get the quorum :D
18:33:38 <geraldosimiao_IR> I'm barelly awake here :|
18:33:53 <adamw> toss a coin and vote :D
18:33:54 <adamw> this is the last one
18:33:56 <lruzicka> geraldosimiao_IR, are you +1 or -1?
18:34:07 <geraldosimiao_IR> +1 FE
18:35:16 <adamw> yaay
18:35:18 <adamw> alright
18:36:10 <adamw> proposed #agreed 2238905 - AcceptedFreezeException (Final) - there are various considerations and discussions around the fractional scaling feature, we are generally willing to grant an FE to any change in a conservative direction here (e.g. in this case, not applying auto-detection to non-integer scaling levels)
18:36:17 <geraldosimiao_IR> ack
18:37:00 <lruzicka> ack
18:37:38 <adamw> #agreed 2238905 - AcceptedFreezeException (Final) - there are various considerations and discussions around the fractional scaling feature, we are generally willing to grant an FE to any change in a conservative direction here (e.g. in this case, not applying auto-detection to non-integer scaling levels)
18:37:43 <adamw> #topic Accepted blockers
18:37:55 <adamw> #info the only accepted blocker is the famous shim one, we are still tracking upstream progress there
18:37:57 <adamw> #topic Open floor
18:38:01 <adamw> any other business?
18:38:08 <lruzicka> I do not have anything. Must be going now. :D
18:38:28 <adamw> thanks for sticking around!
18:39:18 <lruzicka> no problem, take care and have a nice day
18:39:35 <adamw> alrighty, let's wrap it up then
18:39:37 <adamw> #endmeeting