15:05:08 <bcotton> #startmeeting Prioritized bugs and issues
15:05:08 <zodbot> Meeting started Wed Nov 16 15:05:08 2022 UTC.
15:05:08 <zodbot> This meeting is logged and archived in a public location.
15:05:08 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:05:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:05:08 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues'
15:05:08 <bcotton> #meetingname Fedora Prioritized bugs and issues
15:05:08 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues'
15:05:27 <mattdm> They complained about that on the Linux Unplugged podcast.
15:05:36 <mattdm> Possibly should be prioritized bug :)
15:05:38 <bcotton> #topic Purpose of this meeting
15:05:39 <bcotton> #info The purpose of this process is to help with processing backlog of bugs and issues found during the development, verification and use of Fedora distribution.
15:05:39 <bcotton> #info The main goal is to raise visibility of bugs and issues to help  contributors focus on the most important issues.
15:05:44 <bcotton> oh good. not just me then :-)
15:05:49 <bcotton> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description
15:05:57 <bcotton> #topic Roll Call
15:06:24 <bcotton> for sure, i'll see if i can find one for the next time
15:06:41 <bittin_> Prio bugs meeting? (sorry for being late)
15:07:15 <bcotton> #topic Common Bugs review
15:07:20 <bcotton> #info Let's start with a check of the Common Bugs pages for supported releases and see if any should be nominated as Prioritized Bugs
15:07:20 <bcotton> #link https://ask.fedoraproject.org/c/common-issues/141/none/l/latest?order=votes
15:09:17 <bcotton> the only one that stands out to me is https://bugzilla.redhat.com/show_bug.cgi?id=2015490 but that seems like kind of a big fix
15:09:30 * mattdm is going to add a banner topic to ask noting the auth problems
15:10:54 <mattdm> I think that one might be worth poking at .
15:11:14 <mattdm> It's kind of a corner case, and part of the answer is "well, don't do that".
15:11:31 <mattdm> But it's clearly not a good experience, and we considered it for a blocker...
15:12:27 <bcotton> does this mean you'd like to nominate it? :-)
15:13:06 <mattdm> Yeah, let's do it
15:13:09 <mattdm> I am nominating that one
15:13:09 <bcotton> ok!
15:13:16 <bcotton> #topic Nominated bugs
15:13:24 <bcotton> #info 2 nominated bugs
15:13:35 <bcotton> #topic It is possible to go through the initial setup without creating a root and without adding a user to the wheel group
15:13:42 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2015490
15:13:59 <bcotton> #info This was an in-meeting nomination as part of the Common Issues review
15:14:45 <bcotton> I agree that this definitely is a foot gun for users that accidentally put themselves in that corner
15:15:33 <bcotton> I just worry we'll end up having to remove the prioritized designation because it's too hard to fix reasonably
15:15:34 <mattdm> I guess I +1 my own nomination :)
15:16:17 <bcotton> oh, also, do we know that this is still an issue on F37 media?
15:16:32 <mattdm> I think it should be possible to improve the logic in the initial setup app
15:16:35 <bcotton> because this can't be fixed for current releases, only future
15:17:01 <mattdm> I have not looked at that in over ten years, but I don't think it should be that hard
15:17:41 <mattdm> I'm not sure why it's parsing the kickstart instead of ... checking of there is a root password
15:18:43 <mattdm> like, just remove that check?
15:19:10 <mattdm> I might be missing something. :)
15:20:02 <mattdm> s/of/if/
15:20:39 <bcotton> i was going to stall while i verified that it's still a problem in f37, but i apparently need to install the virt stack first
15:20:52 <bcotton> so I'm okay with just accepting it and we can close it if it magically got fixed
15:21:39 <bcotton> proposed #agreed 2015490 - Accepted - This is a corner case, but it can lead to a very bad experience for users who encounter it.
15:21:46 <mattdm> As described I do not see how it could magically fix itself.
15:22:31 <bcotton> more like someone fixed it and forgot to update the BZ. but i agree it seems unlikely
15:24:12 <bcotton> seeing no objections...
15:24:12 <bcotton> #agreed 2015490 - Accepted - This is a corner case, but it can lead to a very bad experience for users who encounter it.
15:24:27 <bcotton> #topic ABRT on KDE can't store any passwords: Secret Service is not available
15:24:27 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2141237
15:25:46 <bcotton> so this looks like it may be fixed already
15:25:52 <mattdm> yay to fixed bugs
15:25:59 <bittin_> nice
15:26:55 <bcotton> ah, it's fixed in copr
15:26:56 <bcotton> so i say we accept it and nudge the maintainers to update the official repos
15:27:14 <bittin_> bcotton: +1 agrees
15:27:35 <mattdm> +1
15:29:23 <bcotton> #agreed 2141237 - Accepted - This presents a major roadblock to bug reporting on KDE Plasma based variants
15:29:40 <bcotton> #topic Accepted bugs
15:29:40 <bcotton> #info 0 accepted bugs
15:29:40 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871665&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%2B
15:30:27 <bcotton> #topic Bugs fixed since last meeting
15:30:27 <bcotton> #info This is to remind ourselves that the process works
15:30:28 <bcotton> #info Systemd causes PC Speaker to emit a loud beep during reboot/poweroff, after suspend&resume
15:30:28 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2129387
15:30:49 <bcotton> #topic Next meeting
15:30:49 <bcotton> #info We will meet again on 30 November at 1500 UTC in #fedora-meeting-1
15:30:55 <bcotton> #topic Open floor
15:31:00 <bcotton> Anything else before we close?
15:31:53 <mattdm> That's all I have. Thanks Ben!
15:32:41 <bcotton> alrighty! have fun, everyone
15:32:43 <bcotton> #endmeeting