15:00:34 <bcotton_> #startmeeting Prioritized bugs and issues
15:00:34 <zodbot> Meeting started Wed May  5 15:00:34 2021 UTC.
15:00:34 <zodbot> This meeting is logged and archived in a public location.
15:00:34 <zodbot> The chair is bcotton_. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:34 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues'
15:00:35 <bcotton_> #meetingname Fedora Prioritized bugs and issues
15:00:35 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues'
15:00:42 <bcotton_> #topic Purpose of this meeting
15:00:43 <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:00:45 <bcotton_> #info The main goal is to raise visibility of bugs and issues to help  contributors focus on the most important issues.
15:00:46 <bcotton_> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description
15:00:48 <bcotton_> #topic Roll Call
15:01:00 <tablepc> .hello 2
15:01:02 <zodbot> tablepc: Sorry, but you don't exist
15:01:06 <dtometzki> .hi
15:01:07 <zodbot> dtometzki: dtometzki 'Damian Tometzki' <linux@tometzki.de>
15:01:31 <tablepc> I'm pretty sure I do exist
15:01:53 <bcotton_> tablepc: i think you had a space between hello and 2 so it looked for an account named '2'
15:01:59 <dtometzki> tablepc, perhaps without the 2
15:02:10 <tablepc> .hello2
15:02:13 <zodbot> tablepc: tablepc 'Pat Kelly' <pmkellly@frontier.com>
15:02:19 <mattdm> i am here!
15:02:39 <bcotton_> hooray!
15:03:09 <mhroncok> hi
15:03:49 <bcotton_> well i think that's all of the usual crew, let's start
15:03:57 <bcotton_> #topic Nominated bugs
15:03:59 <bcotton_> #info 1 nominated bugs
15:04:00 <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:04:03 <bcotton_> #topic Firewalld Panel Applet not working
15:04:05 <bcotton_> #link https://bugzilla.redhat.com/show_bug.cgi?id=1791860
15:04:14 <bcotton_> tablepc slipped this one under the door right before we started :-)
15:04:39 <tablepc> I was just wondering if an old bug on something bood qualifies.
15:04:39 <bcotton_> looks like this has been broken since ~F31?
15:05:35 <tablepc> Yes even before F31 but different bug numners
15:07:18 <mhroncok> https://bugzilla.redhat.com/show_bug.cgi?id=1812510#c3 the maintainer acknowledged the bug a year ago
15:08:04 <mattdm> Hmmmm. So... in the default GNOME config, these kind of icons aren't shown at all, right?
15:08:15 <mhroncok> probably a good idea to nudge them a bit, nit sure if the applet is a priority :/
15:08:57 <mattdm> I'm honestly not sure what the GNOME concept for UI access for these kind of things is *supposed* to be.
15:10:30 <mattdm> I have a whole pile of disappointments re firewalld that this comes in, like, fifteenth on the list
15:12:28 <bcotton_> tablepc: where does this fall on the "blocks work" to "mildly annoying" scale for you?
15:13:40 <tablepc> About in the middle I'd say. I have this installed in my users machines so they can shut off quick if something happens
15:14:23 <tablepc> The just haven't been able to use it for a while now
15:15:43 <tablepc> They also like the notifications when the net comes up or shuts down
15:15:43 <bcotton_> i don't have a strong opinion (or even a weak one) about whether or not to accept this. anyone care to make arguments either direction?
15:16:37 <mattdm> I have a vague but somewhat cynical interest in improving the state of the firewall tool entirely. It might be worth talking to the firewalld current maintainers about their plans.
15:17:18 <jforbes> .hello2
15:17:19 <zodbot> jforbes: jforbes 'Justin M. Forbes' <jforbes@redhat.com>
15:18:08 <mattdm> hi justin!
15:18:19 <bcotton_> mattdm: is that a +1 or a -1? :-)
15:18:20 <dtometzki> hi
15:18:33 <bcotton_> or is it a "let's come back to it next time?"
15:19:11 <mattdm> Let's make it #action mattdm speak to firewalld maintainers about their plans, revisit this next time in light of that
15:19:19 <mhroncok> mattdm: ack
15:19:26 <tablepc> ack
15:19:40 <Pawel[m]> is there any alternative available for this applet, some other applet or simple front-end as a workaround that can be put somewhere in documentation?
15:20:12 <tablepc> I've looked, but with no success
15:20:13 <bcotton_> #action mattdm speak to firewalld maintainers about their plans, revisit this next time in light of that
15:21:41 <Pawel[m]> ok, let's wait then
15:21:58 <mattdm> I'll send mail as soon as we're done there and report back to y'all next time :)
15:22:14 <bcotton_> #topic Accepted bugs
15:22:15 <bcotton_> #info 1 accepted bugs
15:22:17 <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:22:21 <bcotton_> #topic Cpu usage very high until touchpad is touched
15:22:23 <bcotton_> #link https://bugzilla.redhat.com/show_bug.cgi?id=1847627
15:22:32 <jforbes> I have thoughts :)
15:22:34 <bcotton_> so we were a little uncertain about this one when we accepted it
15:22:42 <bcotton_> i put out a call for testing and we got updates
15:22:48 <bcotton_> which leads me to jforbes's thoughts...
15:22:53 <bcotton_> go ahead, justin
15:23:17 <jforbes> It turns out, I have this exact laptop, but never saw it because it isn't the default configuration.  The testers that confirmed the bug had to be told how to change their config to reproduce
15:24:00 <jforbes> It certainly is a bug, and I will work on a fix when I can get to it, but rather than priority bug, I would consider it low priority bug.  It is common hardware, but not the default or standard config
15:24:01 <mattdm> # action send more laptops to jforbes
15:24:17 <mattdm> +1 sounds reasonable
15:24:18 <jforbes> That works too.
15:24:50 <tablepc> My laptop used didn't see this
15:25:01 <bcotton_> so based on what we know now, i'm inclined to agree with jforbes and un-prioritized bugs this
15:25:10 <mhroncok> +1
15:25:47 <jforbes> The issue is with a specific touchpad.  A change went in a couple of years ago to not re intialize the module on resume, this fixed many touchpads, broke a few as well.  I need to write a quirk for it to bring it back.
15:26:15 <mattdm> # action ban all touchpads
15:26:59 <jforbes> I could be in favor of that as well, just because I hate to use them
15:27:17 <tablepc> Touchpads are a pain
15:27:43 <bcotton_> proposed #agreed BZ 1847627 is removed as a Prioritized Bug as the behavior is limited to a specific touchpad model used in non-default configuration
15:28:06 <jforbes> I would like to see this bug removed from priority though, and future consideration weigh the bug more on how many users are likely encountering it in the wild.
15:28:42 <bcotton_> jforbes: that's part of the consideration, but at the time it wasn't clear to use that it was a non-default configuration
15:28:49 <bcotton_> s/use/us/
15:29:24 <mattdm> +1 to proposed, and to what bcotton_ just said
15:29:56 <mhroncok> +1
15:30:02 <Pawel[m]> +1
15:30:03 <jforbes> Given the amount of hardware that we enable, something is always broken.  I would love to see it all fixed, but I don't exactly have an army here. Users working with upstream get a fix faster, but I would like to focus more on bugs which impact the most users, or are really critical (data corruption/security/loss of use)
15:30:10 <jforbes> +1
15:30:30 <mattdm> absolutely. We want the priorities to actually be useful rather than sending you on random chases
15:30:58 <jforbes> This one was a bit easier since it turns out I have the exact model :)
15:31:41 <jforbes> Though with merge window and test week, I still won't have the cycles until late next week
15:31:45 <mattdm> which is really kind of related because "that's a pretty popular Linux laptop" is definitely something that caught our eye in discussing this in the first place
15:31:51 <bcotton_> #agreed BZ 1847627 is removed as a Prioritized Bug as the behavior is limited to a specific touchpad model used in non-default configuration
15:32:00 <bcotton_> this goes back to the "send justin more laptops" point
15:32:32 <bcotton_> mattdm can use his Distinguished Engineer money to send a box truck full of laptops to jforbes's house
15:32:37 <jforbes> Yes, it is definitely a popular laptop.  Though if it were a default config issue, we would have had a lot more people piling on the bug before we specifically asked for testers
15:32:50 <mattdm> yeah
15:33:12 <mattdm> Honestly right now is a _great_ time to make HW requests at RH for things like this
15:33:22 <mattdm> because of budget $reasons
15:33:41 <mattdm> so in seriousness if there is more hardware that would be helpful, let's get it to you
15:33:45 <jforbes> I would really like to figure out how to get an M1 to make work as a build server :)
15:34:27 <mattdm> Eighth_Doctor keeps sending me optimistic links about getting that running as an actual productive laptop too :)
15:34:38 <jforbes> Though it will be a long time (if ever) before it becomes a viable fedora general purpose system due to graphics support
15:34:40 <Eighth_Doctor> 👋
15:34:55 <Eighth_Doctor> graphics support is likely to be available by December
15:35:07 <bcotton_> but december of what year? that's the question
15:35:11 <Eighth_Doctor> this year
15:35:13 <mattdm> heh.
15:35:20 <mattdm> anywayyyyyyy....
15:35:22 <jforbes> Yeah, I have been following, still not convinced. I mean not accelerated graphics
15:35:23 <mhroncok> bcotton_: the year when pandemic ends :D
15:36:05 <bcotton_> hahaha
15:36:14 <bcotton_> #topic Next meeting
15:36:15 <bcotton_> #info We will meet again on 19 May at 1500 UTC in #fedora-meeting-1
15:36:22 <bcotton_> okay, i think that's all we have for today
15:36:33 <bcotton_> thanks everyone for your participation
15:36:35 <Eighth_Doctor> .hello ngompa
15:36:36 <zodbot> Eighth_Doctor: ngompa 'Neal Gompa' <ngompa13@gmail.com>
15:36:37 <Eighth_Doctor> :)
15:36:39 <tablepc> Have a Great Day Everyone!
15:36:44 <jforbes> Side note, I may not always "join the meeting" but I am always in channel, feel free to ping me on any kernel issues
15:36:54 <bcotton_> jforbes: will do :-)
15:36:56 <bcotton_> #endmeeting