15:01:07 <bcotton> #startmeeting Prioritized bugs and issues
15:01:07 <zodbot> Meeting started Wed Nov 30 15:01:07 2022 UTC.
15:01:07 <zodbot> This meeting is logged and archived in a public location.
15:01:07 <zodbot> The chair is bcotton. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
15:01:07 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:01:07 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues'
15:01:08 <bcotton> #meetingname Fedora Prioritized bugs and issues
15:01:08 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues'
15:01:15 <bcotton> #topic Purpose of this meeting
15:01:16 <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:01:16 <bcotton> #info The main goal is to raise visibility of bugs and issues to help  contributors focus on the most important issues.
15:01:25 <bcotton> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description
15:01:38 <bcotton> #topic Roll Call
15:01:50 <mhroncok> .hello churchyard
15:01:51 <zodbot> mhroncok: Something blew up, please try again
15:01:54 <zodbot> mhroncok: An error has occurred and has been logged. Please contact this bot's administrator for more information.
15:02:58 <bcotton> oh noes :-(
15:04:38 <mhroncok> .hello churchyard
15:04:39 <zodbot> mhroncok: Something blew up, please try again
15:04:42 <zodbot> mhroncok: An error has occurred and has been logged. Please contact this bot's administrator for more information.
15:05:53 <mhroncok> meh
15:06:15 * bcotton wonders if mattdm is around
15:06:30 * bcotton also wonders why element didn't update my display name
15:08:22 <bcotton> okay, well i'm on the phone, but let's get started
15:08:22 <bcotton> #topic Common Bugs review
15:08:23 <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:08:23 <bcotton> #link https://ask.fedoraproject.org/c/common-issues/141/none/l/latest?order=votes
15:09:02 <bcotton> i don't see anything recently updated that stands out
15:09:56 <bcotton> #topic Nominated bugs
15:09:57 <bcotton> #info 3 nominated bugs
15:10:05 <bcotton> #link https://bugzilla.redhat.com/buglist.cgi?bug_status=__open__&f1=flagtypes.name&f2=OP&list_id=10871664&o1=substring&query_format=advanced&v1=fedora_prioritized_bug%3F
15:10:06 <bcotton> #topic Recent kernels cause problem with microphone LED on Thinkpad X1 Carbon gen. 9
15:10:06 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2134824
15:10:56 <bcotton> so justin made it pretty clear he doesn't want to prioritize it, which i understand
15:10:56 <mhroncok> I see that Mark responded
15:11:06 <markpearson> hi!
15:11:18 <markpearson> I've been working on that one
15:11:21 <bcotton> but yeah, markpearson is on the case, so i think it makes sense to let it work from his end
15:11:30 <markpearson> happy to take it
15:11:36 <bcotton> to be honest, i didn't even know that was a thing on my laptop until I saw the BZ :-)
15:12:01 <markpearson> The funny thing is it's been broken on AMD laptops forever - finally got that working and now it breaks ont he X1 Carbon....sigh
15:12:08 <mhroncok> the reason I thinkt his should be prioritized is that this is quite common laptop model, especially in RH
15:12:36 <mhroncok> but getting somebody who knows what to do actually look at it is success
15:12:46 <markpearson> It does look like a kernel problem - broken sometime between 5.18.19 and 5.19.1
15:12:52 <bcotton> yes, but is the impact quite common? like what percentage of users are 1. using this feature and 2. notice that the light isn't on
15:13:19 <markpearson> What does making it a priority cause to happen?
15:14:30 <mhroncok> I honestly assumed that everybody uses this feature
15:14:48 <bcotton> markpearson: marking it as a prioritized bug basically means matthew or I become really annoying until it's fixed ;-)
15:15:03 <mattdm> hi I'm around now
15:15:26 <markpearson> Hah - usually it's my role to be annoying :)
15:16:16 <bcotton> I guess from a process perspective, it doesn't particularly matter if prioritizing it means that we pester justin or pester mark
15:16:34 <mattdm> +1 mark prioritized, note that we're pestering mark on this one :)
15:16:45 <markpearson> Yeah - leave Justin in peace
15:17:18 <mattdm> We want the Carbon to feel like a top-notch, polished experience and should avoid these kinds of regressions as much as possible
15:17:26 <markpearson> but I'm OK to be on a hotseat for this one - I'd want it fixed myself. I know it annoyed the heck out of AMD platform users when it was broken there
15:17:35 <bcotton> works for me
15:19:00 <bcotton> proposed #agreed 2134824 - Accepted - This impacts an important laptop model for our community.
15:19:02 <mhroncok> ack
15:19:44 <bcotton> and i'll re-assign the bug to mark, at least until we need justin to do a kernel build (assuming it doesn't get caught up in a regular update)
15:19:45 <mhroncok> let's assign the bugzilla to Mark so Justin knows we are not trying to exploit him?
15:19:46 <mhroncok> :)
15:20:06 <bcotton> #agreed great minds think alike :-)
15:20:23 <bcotton> #agreed 2134824 - Accepted - This impacts an important laptop model for our community.
15:20:24 <bcotton> #topic Do Not Disturb enabled when screens are not mirrored
15:20:24 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2143358
15:20:49 <bcotton> so i nominated this one. it caused me to almost miss the last prioritized bug meeting, which feels like it should be an auto-accept
15:21:25 <bcotton> i don't see anything in the upstream tracker (which means I should probably file it myself), but i have seen some social media, etc commentary about it
15:22:22 <mhroncok> it would certainly help to see that this is reproducible by others
15:24:25 <bcotton> i'm okay with holding off on this for two weeks to see if it's a Me Problem™
15:24:57 <bcotton> 5
15:24:59 <bcotton> whoops :-)
15:26:16 <bcotton> any strong opinions either way?
15:26:24 <mhroncok> not really
15:26:42 <mhroncok> waiting seems resonable
15:26:53 <mhroncok> assuming somebody actually triages KDE SIG bugzillas
15:27:45 <bcotton> if they don't do it on their own, I know where to find them :-)
15:27:47 <bcotton> #action bcotton to find or file an upstream bug for RHBZ 2143358
15:28:08 <bcotton> #agreed 2143358 - we'll wait until the next meeting to gather more information
15:28:09 <bcotton> #topic gtk3-3.24.35 broke double click to maximize in many apps (regression from gtk3-3.24.34)
15:28:09 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2149632
15:28:49 <bcotton> this one got nominated after the agenda email went out, but given the impact, I felt it was worth including in today's meeting
15:29:35 <mhroncok> +1 prioritized
15:30:11 <mhroncok> Given Kamil is QA I assume he double checked this is reproducible
15:30:11 <bcotton> yeah, this one feels pretty straightforward. the only wrinkle is that the upstream maintainer is traveling most of this week and next, so it's not clear how much attention it will get
15:30:30 <mhroncok> gtk3 update with +2 karma limit scares me
15:30:42 <bcotton> yeah, that seems suboptimal
15:32:03 <bcotton> hm. well...worksforme
15:32:05 <mattdm> I still miss "double click to roll up window, amiga workbench style" from gtk2
15:32:56 <bcotton> OH! it does not work for me, it's just limited to a set of applications that does not include Terminal
15:33:41 <mattdm> I think "drag to top" is the preferred way to maximize windows in GNOME. And anecdotally when I was using Windows (not on my comptuer) the other day, that's how my daughter told me to maximize a window there.
15:34:00 <bcotton> i already have 3.24.35 so i can't quickly test that it worked with .34, but i'll trust kamil
15:34:00 <mhroncok> terminal might be gtk4... ?
15:34:33 <bcotton> that does work, but this doesn't feel like a "well stop doing it wrong, then" scenario
15:34:34 <bcotton> this is a pretty ingrained behavior for a lot of users
15:35:05 <mattdm> I may not be the right person to opine here though, because I don't understand what kind of monitors people have that they want windows maximized :)
15:35:44 <mattdm> But I'll support it as prioritized as a pretty serious behavior-change regression in a minor update.
15:36:12 <mattdm> And maybe, um, ask them for a higher karma/vote threshold before pushing those except in the event of a severe security bug?
15:36:40 <bcotton> proposed #agreed 2149632 - Accepted - This is a serious behavior change regression in a minor update
15:38:03 <mattdm> +1
15:38:29 <mhroncok> +1
15:38:34 <bcotton> #agreed 2149632 - Accepted - This is a serious behavior change regression in a minor update
15:39:03 <bcotton> #topic Accepted bugs
15:39:04 <bcotton> #info 1 accepted bugs
15:39:04 <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:39:04 <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:39:04 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2015490
15:39:34 <bcotton> there hasn't been any BZ activity, although this seems like it would be a non-trivial fix
15:39:36 <bcotton> is anyone aware of behind-the-scenes action here?
15:40:32 <mattdm> I am not.
15:40:46 <mattdm> Hmm. I wonder if there is a way to ask policykit if an admin user exists.
15:43:02 <bcotton> okay, i'll nudge the assignee and see what they say
15:43:03 <bcotton> #topic Bugs fixed since last meeting
15:43:04 <bcotton> #info This is to remind ourselves that the process works
15:43:21 <bcotton> #topic ABRT on KDE can't store any passwords: Secret Service is not available
15:43:21 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=2141237
15:43:30 <bcotton> #topic Next meeting
15:43:30 <bcotton> #info We will meet again on 14 December at 1500 UTC in #fedora-meeting-1
15:43:31 <bcotton> anything else before we close?
15:44:15 <mattdm> nope. sorry for being half-present. thanks everyone!
15:44:16 <mhroncok> nope
15:44:26 <bcotton> okay, thanks everyone!
15:44:27 <bcotton> #endmeeting