f45-blocker-review
LOGS
<@adamwill:fedora.im>
16:00:33
!startmeeting F45-blocker-review
<@meetbot:fedora.im>
16:00:34
Meeting started at 2026-09-28 16:00:33 UTC
<@meetbot:fedora.im>
16:00:34
The Meeting name is 'F45-blocker-review'
<@adamwill:fedora.im>
16:00:38
!topic Roll Call
<@adamwill:fedora.im>
16:00:44
who's around for blocker review fun?
<@adamwill:fedora.im>
16:00:45
!hi
<@zodbot:fedora.im>
16:00:46
adamw: Adam Williamson (adamwill) - he / him / his
<@nielsenb:fedora.im>
16:00:56
!hi
<@zodbot:fedora.im>
16:00:57
Brandon Nielsen: Brandon Nielsen (nielsenb)
<@decathorpe:fedora.im>
16:01:02
!hi
<@zodbot:fedora.im>
16:01:03
Fabio Valentini 🌈: Fabio Valentini (decathorpe) - he / him / his
<@derekenz:fedora.im>
16:01:34
!hi
<@zodbot:fedora.im>
16:01:35
Derek Enz: Derek Enz (derekenz)
<@lruzicka:fedora.im>
16:03:36
!hi
<@zodbot:fedora.im>
16:03:38
Lukáš Růžička: Lukáš Růžička (lruzicka) - he / him / his
<@goroboro:matrix.org>
16:03:41
!hi
<@supakeen:fedora.im>
16:03:42
!hi
<@zodbot:fedora.im>
16:03:43
Simon de Vlieger: Simon de Vlieger (supakeen) - he / him / his
<@zodbot:fedora.im>
16:03:44
Ro: Rowan Puttergill (goroboro) - he / him / his
<@adamwill:fedora.im>
16:04:23
hi everyone! thanks for joining
<@adamwill:fedora.im>
16:04:31
time for everyone's favourite plate...boilerplate
<@adamwill:fedora.im>
16:04:37
!topic Introduction
<@adamwill:fedora.im>
16:04:37
Why are we here?
<@adamwill:fedora.im>
16:04:37
!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>
16:04:37
!info We'll be following the process outlined at:
<@adamwill:fedora.im>
16:04:37
<@adamwill:fedora.im>
16:04:37
!info The bugs up for review today are available at:
<@adamwill:fedora.im>
16:04:37
<@adamwill:fedora.im>
16:04:37
!info The criteria for release blocking bugs can be found at:
<@adamwill:fedora.im>
16:04:37
<@adamwill:fedora.im>
16:04:37
<@adamwill:fedora.im>
16:04:37
<@adamwill:fedora.im>
16:04:54
!info for Final, we have:
<@adamwill:fedora.im>
16:04:55
!info 5 Proposed Blockers
<@adamwill:fedora.im>
16:04:55
!info 2 Accepted Blockers
<@adamwill:fedora.im>
16:04:59
!info 6 Accepted Freeze Exceptions
<@adamwill:fedora.im>
16:05:18
!info since lukas is off today, I will secretarialize
<@lruzicka:fedora.im>
16:05:55
I am here for the meeting but then will go off, thanks for the job, Adam.
<@adamwill:fedora.im>
16:06:35
you shouldn't be here! leave! :D
<@adamwill:fedora.im>
16:07:08
let's get started with:
<@adamwill:fedora.im>
16:07:11
!topic Proposed Final blockers
<@adamwill:fedora.im>
16:07:20
!topic (2538553) Czech keyboard layouts are a weird pain: what should we do
<@adamwill:fedora.im>
16:07:20
<@adamwill:fedora.im>
16:07:20
<@adamwill:fedora.im>
16:07:20
!info Proposed Blocker, anaconda, NEW
<@adamwill:fedora.im>
16:07:20
!info Ticket vote: FinalBlocker (+5,0,-1) (+lruzicka, +geraldosimiao, +augenauf, +kparal, +derekenz, -adamwill)
<@adamwill:fedora.im>
16:07:30
so this got a lot of votes quickly, but then we looked into it and the picture is more complicated than we thought
<@adamwill:fedora.im>
16:07:34
hence the bug name change
<@adamwill:fedora.im>
16:08:46
thanks to kparal for extensive research on this. the executive summary is: what we're hitting here is specific to czech, there's a few factors involved but the main issue is, there are various czech keyboard configurations and it seems none of the console ones *exactly* match the xkb ones so mapping between them is very difficult
<@adamwill:fedora.im>
16:09:27
we don't *think* anything has changed here since f44 and previous fedoras. anaconda delegates xkb<->kbd conversion to localed and its logic and data haven't changed
<@nielsenb:fedora.im>
16:10:09
I feel like even if we voted it as a blocker, it's likely to get waived as "too hard to fix" / "rabbit hole too deep"
<@goroboro:matrix.org>
16:10:28
if it isn't a regression... then I don't think it is blocking... but I am also not a czech keyboard user... so I don't know how terrible this is
<@adamwill:fedora.im>
16:10:51
i mean it's not technically difficult to change the behavior, but it's definitely a rabbit hole, because you're trying to guess/infer what a few million czech people expect their keyboard to behave like and map that to the imperfect choices available
<@supakeen:fedora.im>
16:10:54
the czechs are all on holiday today too!
<@lruzicka:fedora.im>
16:11:09
I am a Czech keyboard user and I think that Kamil has made the issue overly complex.
<@derekenz:fedora.im>
16:11:56
Lets hear it Lukas
<@nielsenb:fedora.im>
16:11:56
Right, I feel like anything we would do would be less of a fix, and more of change for preference reasons
<@lruzicka:fedora.im>
16:13:46
There are a couple of historical layouts both in the Linux and WIndows world, but the default Czech keyboard is qwertz. To be sincere, I have never ever experienced any problems with Czech keyboard when I picked it during the installation. The QWERTZ keyboard enables to type all Czech letter, also all US programmatical symbols like []#$%, etc, also several special symbols like €←↓→øþ$'
<@lruzicka:fedora.im>
16:14:27
So if you are a Czech qwertz user, you do not need a dual Czech, English layout for mostly nothing.
<@lruzicka:fedora.im>
16:14:38
I keep the dual layout for Kamil to switch to when he shows me something on CLI.
<@adamwill:fedora.im>
16:14:51
i believe you only encounter the problems here if you use the keyboard config options (either in the installer, on KDE, or in GNOME Control Center, on Workstation) to pick a cz,us or us,cz configuration
<@adamwill:fedora.im>
16:15:10
if you just go with the installer default, or change from cz(qwertz) to cz(qwerty) alone, I don't believe you will see any issues
<@lruzicka:fedora.im>
16:15:42
Therefore I tend to believe that most Czech users will not hit this issue, at least not hit it hard.
<@supakeen:fedora.im>
16:16:16
we can deny this for 45 (on the basis that 'it was already like this', i guess) and then ask as many czechs as we can how they feel about keyboard layouts?
<@lruzicka:fedora.im>
16:16:19
As the situation stands now, I would be -1 FB plus explanation in CommonBugs.
<@supakeen:fedora.im>
16:16:41
we can deny this for 45 (on the basis that 'it was already like this', i guess) and then ask as many czechs as we can how they feel about keyboard layouts (for potentially the next release)?
<@lruzicka:fedora.im>
16:16:43
We can make a survey, sure.
<@adamwill:fedora.im>
16:17:03
i'm -1 also
<@nielsenb:fedora.im>
16:17:19
FinalBlocker -1
<@derekenz:fedora.im>
16:17:33
Sound ok to me FB -1
<@sgallagh:fedora.im>
16:17:36
I'm with Lukas here: FB -1
<@goroboro:matrix.org>
16:17:41
-1
<@derekenz:fedora.im>
16:18:08
Sounds ok to me FB -1
<@adamwill:fedora.im>
16:19:48
let me count votes, just a sec
<@adamwill:fedora.im>
16:20:27
if we assume kparal flipped to -1, that's only geraldo and augenauf left as +2, and we have...at least 6 -1, so we're at -4
<@adamwill:fedora.im>
16:21:52
proposed !agreed 2538553 - RejectedBlocker (Final) - this is rejected as it's very specific to Czech, requires the user to set a custom config rather than just using the default, the behavior has not changed in 45 (except for consoles now using xkb config due to kmscon, but this should be an improvement), and it not being clear what the "correct" thing to do in this case is anyway and there's a high risk trying to fix it makes something worse / somebody unhappy
<@derekenz:fedora.im>
16:22:15
ack
<@lruzicka:fedora.im>
16:22:24
ack, you formulated it very correctly
<@nielsenb:fedora.im>
16:22:28
ack
<@adamwill:fedora.im>
16:22:38
!agreed 2538553 - RejectedBlocker (Final) - this is rejected as it's very specific to Czech, requires the user to set a custom config rather than just using the default, the behavior has not changed in 45 (except for consoles now using xkb config due to kmscon, but this should be an improvement), and it not being clear what the "correct" thing to do in this case is anyway and there's a high risk trying to fix it makes something worse / somebody unhappy
<@adamwill:fedora.im>
16:22:53
!topic (2542374) Anaconda WebUI does not react to keyboard changes when GNOME Settings focus returns on a screen other than Localization
<@adamwill:fedora.im>
16:22:53
<@adamwill:fedora.im>
16:22:53
<@adamwill:fedora.im>
16:22:53
!info Proposed Blocker, anaconda-webui, POST
<@adamwill:fedora.im>
16:22:53
!info Ticket vote: FinalBlocker (+1,0,-1) (+augenauf, -nielsenb)
<@adamwill:fedora.im>
16:22:53
!info Ticket vote: FinalFreezeException (+1,0,-0) (+augenauf)
<@nielsenb:fedora.im>
16:23:30
I actually changed my vote on this one
<@adamwill:fedora.im>
16:23:58
this feels a bit borderline to me...
<@goroboro:matrix.org>
16:24:52
I haven't looked at the webUI too closely so don't feel in much of a position to comment on this
<@lruzicka:fedora.im>
16:25:25
So, basically we have a same bug as the Czech one, now with the german keyboard.
<@geraldosimiao:matrix.org>
16:25:32
!hi
<@zodbot:fedora.im>
16:25:34
geraldosimiao: Geraldo S. Simião Kutz (geraldosimiao) - he / him / his
<@lruzicka:fedora.im>
16:26:06
The problem seems to be that Anaconda shows the selected keyboard layout, which sometimes (although correct) has a misleading name.
<@adamwill:fedora.im>
16:26:19
that's not how I read it
<@nielsenb:fedora.im>
16:26:27
I feel like we've decided a couple of things weren't blockers because we figured the user would do the right thing because UI showed the right thing, but now we have the UI showing the wrong thing
<@lruzicka:fedora.im>
16:26:41
how do you read it, adamw ?
<@nielsenb:fedora.im>
16:26:58
Though maybe that was with KDE
<@adamwill:fedora.im>
16:27:00
well, hmm. it's actually not clear
<@adamwill:fedora.im>
16:27:34
katerina is assuming that what happened is the reporter changed the layout in GNOME Control Center *after proceeding past the welcome screen*
<@adamwill:fedora.im>
16:27:35
but the reporter didn't exactly *say* that
<@adamwill:fedora.im>
16:27:49
let me test this quick, i should be able to
<@adamwill:fedora.im>
16:30:47
hmm. it's a bit weird that the installer UI is shown in german but the reporter says they had to manually select de layout...
<@adamwill:fedora.im>
16:32:19
oh, no, that's normal in german
<@adamwill:fedora.im>
16:32:25
oh, no, that's normal in workstaiton
<@lruzicka:fedora.im>
16:32:26
I tested it:
<@lruzicka:fedora.im>
16:32:26
When I selected "Deutsch (Deutschland)" the UI changed the language immediately, but keyboard layout stayed at "us"! I had to add the German layout if I wanted it and it brought us-acentos
<@adamwill:fedora.im>
16:32:42
yes that's normal in workstation (you have to change it yourself). i forgot
<@adamwill:fedora.im>
16:32:51
it's the lognstanding issue that gnome doesn't let anaconda control the layouts
<@goroboro:matrix.org>
16:33:36
so non-regression? just ugly...
<@lruzicka:fedora.im>
16:33:44
Indeed? I am not sure about Czech. Let me test it, too
<@adamwill:fedora.im>
16:33:54
but if I do the layout change on the Welcome page then proceed to the passphrase page, it's correct
<@adamwill:fedora.im>
16:34:05
no, that's not the thing the bug is about.
<@goroboro:matrix.org>
16:34:17
ah
<@adamwill:fedora.im>
16:34:18
but well yes, also, that part isn't a regression.
<@lruzicka:fedora.im>
16:34:19
Yes, confirmed.
<@adamwill:fedora.im>
16:34:28
let's see if i can also reproduce the bug by changing later
<@lruzicka:fedora.im>
16:34:43
I had to manually deselect US and select CZ instead. I think this could be done with German keyboard.
<@lruzicka:fedora.im>
16:35:55
If I do it and remove US layout, I get DE on encryption page.
<@adamwill:fedora.im>
16:36:01
yes, as I said, that's known and not a regression. it's why webui shows the link to the Control Center on this page in the first place, it only does that on Workstation
<@adamwill:fedora.im>
16:36:08
on KDE it shows a keyboard configuration widget, because it can do that
<@lruzicka:fedora.im>
16:36:30
However, Anaconda changes language and Gnome DOES NOT.
<@lruzicka:fedora.im>
16:36:49
That looks a bit stupid.
<@lruzicka:fedora.im>
16:37:15
But not blocking material, I believe
<@adamwill:fedora.im>
16:37:19
i dunno if anaconda even tries to change the desktop *language* to what you pick
<@adamwill:fedora.im>
16:37:33
but if it did, it probably would have the same issue in gnome, it's probably not allowed
<@adamwill:fedora.im>
16:38:16
darn, i changed too late that time, i think...
<@adamwill:fedora.im>
16:43:21
hmm. i can't get us-acentos to appear anyhow. but...it works ok if you change on the welcome page where the link is, if you change on the next page, anaconda shows 'us' (for me)
<@adamwill:fedora.im>
16:44:51
so, on the whole...guess i'm -1 on this, it's not ideal but the most standard path works, for me
<@adamwill:fedora.im>
16:45:05
probably will ask the reporter for more info on *exactly* what they did, though
<@nielsenb:fedora.im>
16:45:41
Do we want a FE for the "pick up change in settings" fix?
<@adamwill:fedora.im>
16:46:27
yeah, i think FE for picking up changes on other pages is fine
<@adamwill:fedora.im>
16:46:36
ahhh, if you configure *both* keyboards, i see
<@adamwill:fedora.im>
16:47:22
hmmmm
<@adamwill:fedora.im>
16:47:26
i might be punt on this, actually
<@lruzicka:fedora.im>
16:47:41
so am I, +1 punt
<@derekenz:fedora.im>
16:47:47
Punt
<@adamwill:fedora.im>
16:47:53
need to figure exactly what the reporter did, and what happened
<@goroboro:matrix.org>
16:47:55
I will go with that :) +1
<@nielsenb:fedora.im>
16:48:03
Quick, everyone, to the punt boats!
<@goroboro:matrix.org>
16:48:03
that was +1 punt
<@nielsenb:fedora.im>
16:48:27
Punt +1
<@adamwill:fedora.im>
16:48:33
proposed !agreed 2542374 - punt (delay decision) - we're not sure exactly what the reporter did here, and exactly what happened. we're punting to ask for more information and also to test some paths ourselves
<@derekenz:fedora.im>
16:48:56
ack
<@nielsenb:fedora.im>
16:49:06
ack
<@lruzicka:fedora.im>
16:49:34
ack
<@goroboro:matrix.org>
16:49:38
ack
<@adamwill:fedora.im>
16:50:52
!agreed 2542374 - punt (delay decision) - we're not sure exactly what the reporter did here, and exactly what happened. we're punting to ask for more information and also to test some paths ourselves
<@adamwill:fedora.im>
16:53:11
!topic (2536815) dnf command not available in kickstart, f45 netboot installer
<@adamwill:fedora.im>
16:53:11
<@adamwill:fedora.im>
16:53:11
<@adamwill:fedora.im>
16:53:11
!info Proposed Blocker, lorax, POST
<@adamwill:fedora.im>
16:53:11
!info Ticket vote: BetaBlocker (+0,0,-1) (-boniboyblue)
<@adamwill:fedora.im>
16:53:11
!info Ticket vote: FinalBlocker (+0,0,-3) (-boniboyblue, -nielsenb, -adamwill)
<@adamwill:fedora.im>
16:53:11
!info Ticket vote: FinalFreezeException (+1,0,-0) (+adamwill)
<@adamwill:fedora.im>
16:53:31
we have -3 / +1 for this in ticket so I figured let's bring it up here so we can vote on both
<@adamwill:fedora.im>
16:53:42
anyone want to argue for +1 blocker? I'm still -1 blocker, +1 FE
<@supakeen:fedora.im>
16:53:59
Not really no.
<@adamwill:fedora.im>
16:54:17
anyone want to vote for FE? :D
<@derekenz:fedora.im>
16:54:25
FE +1
<@nielsenb:fedora.im>
16:54:33
FinalFE +1
<@supakeen:fedora.im>
16:54:42
Sorry, FE +1
<@goroboro:matrix.org>
16:54:52
FE +1
<@lruzicka:fedora.im>
16:55:45
+1
<@adamwill:fedora.im>
16:56:04
proposed !agreed 2536815 - RejectedBlocker (Final) AcceptedFreezeException (Final) - we agreed *this specific bug* does not violate any release criteria, so it's rejected as a blocker. But it is convenient to have a package manager available in the environment and that can't be fixed post-release, so it's accepted as an FE. The "reinstall with encrypted /home" scenario should be treated separately and proposed as a blocker in itself if it's problematic
<@nielsenb:fedora.im>
16:56:19
ack
<@derekenz:fedora.im>
16:56:25
ack
<@goroboro:matrix.org>
16:58:36
mmm it is such a weird use-case :D I wonder about just using rpm in this case... I don't know if dnf even makes sense here
<@goroboro:matrix.org>
16:58:53
ack
<@lruzicka:fedora.im>
16:59:01
ack
<@adamwill:fedora.im>
17:00:47
!agreed 2536815 - RejectedBlocker (Final) AcceptedFreezeException (Final) - we agreed this specific bug does not violate any release criteria, so it's rejected as a blocker. But it is convenient to have a package manager available in the environment and that can't be fixed post-release, so it's accepted as an FE. The "reinstall with encrypted /home" scenario should be treated separately and proposed as a blocker in itself if it's problematic
<@adamwill:fedora.im>
17:00:55
!topic (2540692) Cannot authenticate to secure wifi during gnome-initial-setup
<@adamwill:fedora.im>
17:00:55
<@adamwill:fedora.im>
17:00:55
<@adamwill:fedora.im>
17:00:55
!info Proposed Blocker, oo7, NEW
<@adamwill:fedora.im>
17:01:02
this one I think we should probably punt and have more folks test
<@goroboro:matrix.org>
17:02:08
+1 punt
<@decathorpe:fedora.im>
17:02:29
from oo7 package maintainer perspective, I'm not *entirely* sure how it could be to blame here, unless "cannot save wifi password to keyring" prevents it from *connecting* entirely
<@adamwill:fedora.im>
17:02:45
yeah, i don't know if oo7 is the issue at all. it needs more testing
<@nielsenb:fedora.im>
17:02:49
It never even prompts
<@adamwill:fedora.im>
17:03:00
i guess brandon just figured oo7 is the obvious New Thing in this area?
<@nielsenb:fedora.im>
17:03:06
So there's nothing for oo7 to save, even if a keyring is available
<@nielsenb:fedora.im>
17:03:18
The log shows no secrets provider, oo7 is the new secrets provider, no?
<@decathorpe:fedora.im>
17:03:24
possibly. though there's also been the 0.7.0.beta update in the meantime I think, so it might have changed too.
<@decathorpe:fedora.im>
17:03:43
not sure if oo7-daemon needs to run (or does run?) in the initial-setup session
<@nielsenb:fedora.im>
17:04:09
I just tested with the 20260927.n.0 compose, still see it, if the update was included there
<@adamwill:fedora.im>
17:05:26
anyhoo, we can debug outside the meeting :D
<@adamwill:fedora.im>
17:05:53
proposed !agreed 2540692 - punt (delay decision) - this is certainly potentially a blocker if confirmed, but we want to have more folks test and confirm the problem and get more details
<@derekenz:fedora.im>
17:06:04
ack
<@goroboro:matrix.org>
17:06:16
ack
<@nielsenb:fedora.im>
17:06:21
ack
<@decathorpe:fedora.im>
17:06:33
ack
<@adamwill:fedora.im>
17:07:16
!agreed 2540692 - punt (delay decision) - this is certainly potentially a blocker if confirmed, but we want to have more folks test and confirm the problem and get more details
<@adamwill:fedora.im>
17:08:52
!topic (2541402) systemd-imds-early-network.service fails at boot with AVC denials
<@adamwill:fedora.im>
17:08:52
<@adamwill:fedora.im>
17:08:52
<@adamwill:fedora.im>
17:08:52
!info Proposed Blocker, selinux-policy, ASSIGNED
<@adamwill:fedora.im>
17:08:52
!info Ticket vote: FinalBlocker (+0,0,-1) (-nielsenb)
<@adamwill:fedora.im>
17:08:52
!info Ticket vote: FinalFreezeException (+1,0,-0) (+nielsenb)
<@adamwill:fedora.im>
17:09:17
i'd say that by policy this is a blocker, and we should just disable the service if it can't be made to work properly
<@adamwill:fedora.im>
17:09:19
+1 blocker
<@lruzicka:fedora.im>
17:10:02
+1 FB
<@derekenz:fedora.im>
17:10:08
+1 FB
<@goroboro:matrix.org>
17:10:15
+1 FB
<@nielsenb:fedora.im>
17:10:21
I guess
<@nielsenb:fedora.im>
17:10:26
FinalBlocker +1
<@supakeen:fedora.im>
17:10:38
+1 FB but is the solution going to be policy adjustment or disablement?
<@supakeen:fedora.im>
17:10:46
Like, have we tried to make it work properly? :)
<@adamwill:fedora.im>
17:11:14
we don't make that decision
<@supakeen:fedora.im>
17:11:19
Ok.
<@adamwill:fedora.im>
17:11:45
it sounds like zdenek thinks it's too late to write an selinux policy for a new service, so we will likely have to disable it
<@adamwill:fedora.im>
17:12:36
proposed !agreed 2541402 - AcceptedBlocker (Final) - this is accepted as a violation of final criterion "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present". We note that disabling the service by default would be an acceptable resolution
<@supakeen:fedora.im>
17:12:38
That's fine I don't think anyone has plans yet to use systemd's new IMDS anyhow, I was just wondering if I should spend some time on it :)
<@supakeen:fedora.im>
17:12:39
ack
<@goroboro:matrix.org>
17:12:44
ack
<@adamwill:fedora.im>
17:12:55
i mean, if you have time to write a policy for it and get zdenek to accept it, that'd be great
<@lruzicka:fedora.im>
17:12:58
ack
<@adamwill:fedora.im>
17:13:07
we can always disable it for now and if a policy appears in time, re-enable it
<@adamwill:fedora.im>
17:13:26
!agreed 2541402 - AcceptedBlocker (Final) - this is accepted as a violation of final criterion "All system services present after installation with one of the release-blocking package sets must start properly, unless they require hardware which is not present". We note that disabling the service by default would be an acceptable resolution
<@adamwill:fedora.im>
17:14:21
that's all the proposed blockers, let's go on to:
<@adamwill:fedora.im>
17:14:37
ah, and there are no proposed FEs, so we'll go straight to:
<@adamwill:fedora.im>
17:14:41
!info there are no proposed FEs
<@adamwill:fedora.im>
17:14:50
!topic Accepted Final blocker review
<@supakeen:fedora.im>
17:14:51
Oh I thought there would be one.
<@adamwill:fedora.im>
17:15:14
the ones that were there this morning had sufficient votes to be resolved before meeting, except for one we voted on earlier in the meeting
<@adamwill:fedora.im>
17:15:18
which one were you interested in?
<@supakeen:fedora.im>
17:15:26
Let's continue I can bring it up at the very end.
<@goroboro:matrix.org>
17:15:30
mmm... on FE... https://forge.fedoraproject.org/server/tickets/issues/216
<@supakeen:fedora.im>
17:15:48
Yea, the one Ro just mentioned was being talked about and I thought it might've been proposed.
<@goroboro:matrix.org>
17:15:50
we kind of have a solution... maybe :)
<@adamwill:fedora.im>
17:16:06
nope. i'm the only person who's filed a bug report on it and i didn't propose it as anything because i still can't reproduce
<@adamwill:fedora.im>
17:16:18
i don't like the idea of changing the systemd service in Server only. for a start, that is hard to do.
<@goroboro:matrix.org>
17:16:39
well really its about stopping the spew of console messages
<@goroboro:matrix.org>
17:17:05
my new proposal is to keep the lines from the f44 that handle this...
<@supakeen:fedora.im>
17:17:09
Regardless we need an actual proposed FB/FE so we can vote on it and more people can try to reproduce.
<@adamwill:fedora.im>
17:17:12
if that's really the issue...maybe we just put those lines back in universally?
<@goroboro:matrix.org>
17:17:17
it is two lines in the service
<@adamwill:fedora.im>
17:17:22
but anyway, this needs to be properly proposed as a blocker or FE to be discussed here
<@goroboro:matrix.org>
17:17:36
okay... will chat outside of this meeting
<@adamwill:fedora.im>
17:19:55
ok, moving on with the scheduled agenda :D
<@adamwill:fedora.im>
17:20:02
!topic (2535534) Multiple things don't work from GNOME quick settings menu
<@adamwill:fedora.im>
17:20:02
<@adamwill:fedora.im>
17:20:02
<@adamwill:fedora.im>
17:20:02
!info Accepted Blocker, gnome-shell, VERIFIED
<@adamwill:fedora.im>
17:20:10
!info the fix for this is verified, we just need to karma the update and get it stable
<@adamwill:fedora.im>
17:21:13
!topic (2537341) oo7-portal not installed by default after upgrading to f45
<@adamwill:fedora.im>
17:21:13
<@adamwill:fedora.im>
17:21:13
<@adamwill:fedora.im>
17:21:13
!info Accepted Blocker, oo7, ON_QA
<@adamwill:fedora.im>
17:21:26
this needs testing/confirmation. I can at least update Silverblue shortly and see if it's appeared in that now
<@nielsenb:fedora.im>
17:21:37
Appeared in my workstation update today
<@adamwill:fedora.im>
17:21:40
!info we need to test and confirm that the fix for this worked
<@adamwill:fedora.im>
17:22:56
!topic Open floor
<@adamwill:fedora.im>
17:23:01
that's about all I had, anything else, folks?
<@decathorpe:fedora.im>
17:24:15
↑ this should be fixed
<@lruzicka:fedora.im>
17:25:23
nothing on my heart
<@goroboro:matrix.org>
17:25:25
thanks @adamw and everyone else.
<@adamwill:fedora.im>
17:25:27
sure, that's why it's on ON_QA, but the process is that we then *verify* the fix :D
<@derekenz:fedora.im>
17:25:33
Good for now Adam
<@adamwill:fedora.im>
17:28:24
ok, thanks for coming everyone!
<@adamwill:fedora.im>
17:28:31
!endmeeting