15:00:08 <bcotton> #startmeeting Prioritized bugs and issues
15:00:08 <zodbot> Meeting started Wed Aug 11 15:00:08 2021 UTC.
15:00:08 <zodbot> This meeting is logged and archived in a public location.
15:00:08 <zodbot> The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:08 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
15:00:08 <zodbot> The meeting name has been set to 'prioritized_bugs_and_issues'
15:00:13 <bcotton> #meetingname Fedora Prioritized bugs and issues
15:00:13 <zodbot> The meeting name has been set to 'fedora_prioritized_bugs_and_issues'
15:00:18 <bcotton> #topic Purpose of this meeting
15:00:24 <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:29 <bcotton> #info The main goal is to raise visibility of bugs and issues to help  contributors focus on the most important issues.
15:00:33 <bcotton> #link https://docs.fedoraproject.org/en-US/program_management/prioritized_bugs/#_process_description
15:00:42 <bcotton> #topic Roll Call
15:00:52 <bcotton> i know bittin  is here. who else? :-)
15:00:57 * bittin is here, but watching the Samsung event at the same time
15:01:37 <decathorpe> .hello2
15:01:38 <zodbot> decathorpe: decathorpe 'Fabio Valentini' <decathorpe@gmail.com>
15:01:59 <bcotton> welcome, Fabio Valentini (decathorpe)
15:02:22 <decathorpe> guess I should participate since I nominated a bug :)
15:02:42 <bcotton> i mean, if you're into that sort of thing :-)
15:02:49 * bcotton looks around for mattdm
15:03:18 <mattdm> i am here
15:03:28 <mattdm> i was here a minute ago i just got distracted by twitter :)
15:03:42 <bcotton> that never happens to me
15:03:51 <bcotton> 0:-)
15:04:30 <bcotton> alright, shall we?
15:04:38 <bcotton> #topic Nominated bugs
15:04:42 <bcotton> #info 1 nominated bugs
15:04:47 <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:55 <bcotton> #topic SELinux is preventing gnome-session-c from 'write' accesses on the sock_file dbus-7hye6voX3Y.
15:05:00 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1949712
15:05:36 <bittin> is a bit distracted by the Samsung event stream but it ends in 2 minutes
15:05:39 <decathorpe> Should I provide some information here?
15:06:09 <bcotton> please do
15:07:22 <decathorpe> So, it looks like this is a widespread SELinux issue on Fedora 34. According to the bug report, users of Workstation and Cinnamon Spin are affected, and if affected, it happens at every boot/login.
15:08:03 <decathorpe> I am affected too, and I have added this specific AVC to the list of ignored ones in setroubleshoot just so I don't get the notification every time I boot my machine.
15:08:19 <bcotton> does this imply that it's not universal?
15:08:36 * bittin is here for real now
15:09:13 <decathorpe> I'm not sure. But there's a steady stream of users reporting in on the BZ with "me too"
15:09:41 <decathorpe> bit it seems to affect both clean installs and f33->f34 upgrades.
15:10:35 <mattdm> I haven't seen it, so it's not universal.
15:10:44 <mattdm> But there do seem to be a lot of reports.
15:10:50 <bittin> same have not seen it
15:10:53 <bcotton> does it actually impact functionality, or is it just annoying?
15:11:54 <decathorpe> AFAICT it's just annoying / concerning
15:12:20 <decathorpe> But isn't there a release acceptance criterion for "No SELinux messages on clean install" or something like that?
15:12:26 <bcotton> there is
15:12:43 <decathorpe> well, this issue has been present since before F34 Beta so clearly nobody cared :)
15:13:02 <bcotton> well if it's not universal, it could just be that none of the test cases triggered it
15:13:10 <mattdm> if it does violate that criteria, maybe kick this back to regular blocker for f35?
15:14:30 <bcotton> it's a little early in the process for that, imo. i mean we could but ideally we should fix it on 34 long before then
15:15:25 <bcotton> so i'm +1 prioritized bug, with the understanding that if we can replicate it on 35 as we start testing those composes, we label it a blocker
15:17:19 <bcotton> any other thoughts?
15:17:29 <mattdm> ok wfm
15:17:35 <mattdm> +1
15:17:43 <bittin> +1
15:18:56 <bcotton> proposed #agreed 1949712 - Accepted - If we see this on F35 composes as we start testing those, it will be proposed as an F35 blocker
15:19:39 <decathorpe> thanks!
15:19:42 <bcotton> #agreed 1949712 - Accepted - If we see this on F35 composes as we start testing those, it will be proposed as an F35 blocker
15:20:19 <bcotton> #action bcotton to follow up with QA team  to see if we can identify cases where this bug is triggered so that we can make sure we're testing for it
15:20:24 <bcotton> anything else on this bug?
15:21:39 <bcotton> ok!
15:21:42 <bcotton> #topic Accepted bugs
15:21:51 <bcotton> #info 2 accepted bugs
15:21:59 <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:07 <bcotton> #topic Akonadi does not start due to DB failure
15:22:13 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1953675
15:22:20 <bcotton> #info Raised with KDE SIG
15:22:26 <bcotton> #link https://pagure.io/fedora-kde/SIG/issue/89
15:22:36 <bcotton> so this one has been looked at and passed around a bit
15:24:14 <bcotton> the current assignee had some vague suggestions: https://bugzilla.redhat.com/show_bug.cgi?id=1953675#c11
15:24:27 <bcotton> i can follow up with the KDE SIG for their input on this, i suppose
15:24:37 <bittin> sounds good
15:24:41 <mattdm> Is this a ... commonly used application?
15:24:56 <bittin> its the database used for a lot of KDE applications
15:25:19 <bcotton> define "used"
15:25:37 <bcotton> ii'm not sure i've ever directly interacted with it outside this bug, but it's part of the default Plasma install
15:25:47 <bittin> https://community.kde.org/KDE_PIM/Akonadi guessing Kmail, Kontakt etc reads from it
15:26:36 <mattdm> Am I to understand that a normal KDE desktop requires running a mysql/mariadb server?
15:27:27 <mattdm> (i am super-skeptical of their faq entry about sqlite not being good enough at concurrency. how many thousands of users does a single desktop environment have at once?)
15:27:39 <mattdm> (but that's kind of irrelevant to the considerations at hand)
15:28:11 <bcotton> yeah, that's a question for another day
15:28:31 <bcotton> so anyway, i'll
15:28:44 <bcotton> #action bcotton to follow up with KDE SIG about comment 11 on this bug
15:28:55 <mattdm> yeah I think that's best.
15:29:09 <bcotton> anything else to add on this bug? I feel like it might be reaching the "we tried, but we give up" threshold
15:29:26 <mattdm> I'm not sure that the proposed approach in the ticket is good -- it seems to be proposing _user level_ cleanup in _system level_ package scripts
15:30:14 <mattdm> apparently there's also this: https://www.reddit.com/r/kde/comments/a4t98v/bringing_kmail_and_postgresql_together_vinzv/ebk21zl/ :)
15:30:57 <bcotton> yeah, i'm not sure it's entirely feasible without iterating over every user...and hope /home isn't autofs with root squash or something like that
15:31:00 <bcotton> but anyway, not our problem for now :-)
15:31:39 <bcotton> #topic A glibc test hangs upon pthread cancellation when glibc is compiled with annobin turned on
15:31:48 <bcotton> #link https://bugzilla.redhat.com/show_bug.cgi?id=1951492
15:32:09 <bcotton> so this one was called a "mass rebuild blocker", but the mass rebuild seems to have completed just fine
15:32:30 <bcotton> so i'm not sure if it got quietly fixed or wasn't actually a problem or the problem hasn't surfaced
15:32:41 <bcotton> but my inclination is to say it's no longer a prioritized bug
15:33:01 <mattdm> yes.
15:34:16 <bcotton> proposed #agreed 1951492 is no longer a prioritized bug as the mass rebuild seems to have completed successfully without it
15:34:22 <mattdm> +1
15:34:29 <bcotton> s/it/a fix/
15:35:29 <bcotton> #agreed 1951492 is no longer a prioritized bug as the mass rebuild seems to have completed successfully without a fix
15:35:37 <bcotton> #topic Next meeting
15:35:43 <bcotton> #info We will meet again on 25 August at 1500 UTC in #fedora-meeting-1
15:35:50 <bcotton> anything else before we adjourn?
15:36:12 <bittin> won't show up then as i will be helping out with Debian Conference stuff at Debconf Online 2021
15:37:14 <mattdm> I got nothin'. Thanks bcotton!
15:37:23 <bcotton> enjoy it, bittin!
15:37:26 <bcotton> okay, thanks everyone!
15:37:28 <bcotton> #endmeeting