15:00:55 #startmeeting Prioritized bugs and issues 15:00:55 Meeting started Wed Sep 12 15:00:55 2018 UTC. 15:00:55 This meeting is logged and archived in a public location. 15:00:55 The chair is bcotton. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:55 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:00:55 The meeting name has been set to 'prioritized_bugs_and_issues' 15:00:57 #meetingname Fedora Prioritized bugs and issues 15:00:57 The meeting name has been set to 'fedora_prioritized_bugs_and_issues' 15:01:05 #topic Purpose of this meeting 15:01:06 #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:13 #info The main goal is to raise visibility of bugs and issues to help contributors focus on the most important issues. 15:01:15 #link https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process 15:01:19 #topic Roll Call 15:01:37 hello! 15:02:28 hi, mattdm, so good to talk to you again :-) 15:04:12 yes. :) 15:04:15 just us here? 15:04:39 looks like it 15:04:51 i guess we'll get started and see what happens 15:04:56 #topic Nominated bugs 15:05:01 only one today! 15:05:14 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Fedora&keywords=Triaged&keywords_type=nowords&list_id=9195844&product=Fedora&query_format=advanced&status_whiteboard=PrioritizedBug&status_whiteboard_type=allwords 15:05:20 #link https://bugzilla.redhat.com/show_bug.cgi?id=1578494 15:05:22 #info 8 other open bugs with the same summary 15:05:27 so this is the one we got via email the other day 15:06:44 mmmm. the trace is probably helpful for debugging, but... 15:06:59 it would be helpful for *me* to understand exactly what situations this happpens in 15:07:02 which the bug does not say 15:07:23 yeah, and looking at the other bugs, i don't see much narrative info 15:07:44 as i read it, if you update using dnf, it kills packagekitd 15:08:08 possibly? 15:08:17 one bug says 15:08:19 Attepting to install Wireshark using gnome-software. 15:08:21 The installation progress bar went up to 100%, but it just stayed there and never disappeared. 15:09:39 and if packagekitd crashes, shouldn't systemd restart it anyway? 15:10:01 probably? maybe it's crashing all the time and most people aren't noticing? 15:10:04 it's not really clear what the impact is beyond "the daemon crashed". which isn't a great thing to happen, but what's the actual impact 15:10:11 or maybe it's rare. i certainly haven't noticed 15:11:26 proposed #agreed BXZ 1578484 is deferred to the next meeting. bcotton will NEEDINFO the bug to get a better understanding of what the user impact is 15:11:37 +1 that sounds reasonable 15:11:49 #agreed BZ 1578484 is deferred to the next meeting. bcotton will NEEDINFO the bug to get a better understanding of what the user impact is 15:12:16 #topic Accepted bugs 15:12:18 #link https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&classification=Fedora&keywords=Triaged&keywords_type=allwords&list_id=9195442&product=Fedora&query_format=advanced&status_whiteboard=PrioritizedBug&status_whiteboard_type=allwords 15:12:29 just a quick review of what we still have open 15:12:38 #link https://bugzilla.redhat.com/show_bug.cgi?id=1336435 15:12:40 #info BZ 13364535 was accepted on 2017-08-02 15:12:41 #info assignee has made no comments since needinfo flag was set on 2017-09-27 15:12:43 #info Upstream bug has had no activity in the last year 15:12:44 #link https://gitlab.gnome.org/GNOME/gnome-software/issues/116 15:12:49 wait one more note on the previous 15:12:57 except don't bother to undo all of that :0 15:13:02 https://retrace.fedoraproject.org/faf/problems/?component_names=PackageKit&associate=__None&type=core&daterange=2018-09-01%3A2018-09-30&bug_filter=None&function_names=&binary_names=&source_file_names=&since_version=&since_release=&to_version=&to_release= 15:13:12 shows quite a few different crashes with repo_internalize_trigger 15:13:25 that is all :) 15:13:27 okay moving on 15:13:38 cool, i'll #link that for the next meeting 15:14:10 I've had some correspondence with Richard about this ... he said he'd update the bug. 15:14:14 I'll ping him about it again 15:14:27 BZ 1336435? 15:15:55 i was going to suggest we remove it from the list. it doesn't seem to be a priority upstream, and idk how many prioritized bugs we can throw at richard :-) 15:16:24 Yeah, but it was a priority for QA 15:16:36 I'd like to at least have the public discussion between dev and qa 15:16:49 okay, works for me 15:16:52 he had some points which he *said* he'd put in the bug but hasn't 15:17:12 #action mattdm to follow up with Richard Huges to update BZ 1336435 15:17:51 #undo 15:17:51 Removing item from minutes: ACTION by bcotton at 15:17:12 : mattdm to follow up with Richard Huges to update BZ 1336435 15:18:04 #action mattdm to follow up with Richard Hughes to update BZ 1336435 15:18:21 are we all good on this one? 15:18:27 yep! thanks. 15:18:43 #link https://bugzilla.redhat.com/show_bug.cgi?id=1385432 15:18:44 #info BZ 1385432 was accepted on 2017-05-25 15:18:46 #info assignee has made no comments since needinfo flag was set on 2018-08-02 15:19:22 ermagerd. 15:19:29 looks like we need deep expertise on this one. 15:19:38 "I would ask people familiar with shutdown process in initramfs (systemd/dracut nowadays?) and kernel/lsm if the -EPERM on semctl is really unexpected in this case. But again, for device-mapper the -EPERM on semctl is not a blocker for device deactivation." 15:19:56 I'm gonna escalate this internally 15:20:16 mattdm++ 15:20:17 bcotton: Karma for mattdm changed to 9 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:20:36 #action mattdm to escalate BZ 1385432 internally 15:21:02 moving on to happier news... 15:21:06 #link https://bugzilla.redhat.com/show_bug.cgi?id=1563674 15:21:07 #info CLOSED->CURRENTRELEASE on 2018-09-11 15:21:34 apparently this one got fixed a little while ago and my pestering got the developer to update the BZ :-) 15:21:43 \o/ 15:21:53 one for the fixed list, finally :) 15:22:08 proof that the process works sometimes 15:22:13 okay, now back to the sadness 15:22:17 #link https://bugzilla.redhat.com/show_bug.cgi?id=1306992 15:22:18 aw 15:22:19 #info BZ 1306992 was accepted on 2018-08-29 15:22:45 at least it's not old sadness :) 15:22:52 yeah, it's relatively fresh 15:23:19 there's a (private) email thread with richard and some of the other people in the ticket with the tmpfiles suggestion 15:23:30 so I think progress is happening 15:23:32 still needinfo for richard. might be worth bringing this one up too 15:23:34 hooray 15:23:45 yeah this is actually more optimistic than the last one 15:24:41 okay. i'll let you work your magic on this and if there are no updates at the next meeting, i'll pull out the annoying stick 15:25:06 yep, sounds good :) 15:25:31 #link https://bugzilla.redhat.com/show_bug.cgi?id=1548586 15:25:32 #info BZ 1548586 was accepted on 2018-06-11 15:25:34 #info fixed version in dnf 3.0 COPR, but not available in Fedora yet 15:27:06 so it sounds like this is going to be in F29? but i didn't see a change proposal for it (unless i missed it) 15:27:10 i know that there's (separate bug) effort in getting the rawhide version of dnf to f29 15:27:23 dnf 3, you mean? 15:27:28 yes 15:27:44 yeah, they didn't file a change proposal, just noted that they were doing it 15:27:56 well no badge for them, then 15:28:01 right? 15:28:12 so i think this merits calling the bug fixed for the purposes of this meeting 15:28:32 though i'm open to leaving it on the list until it actually lands 15:28:44 let's leave it open until adamw is happy :) 15:28:55 if adamw ain't happy, no one is happy 15:29:16 heh 15:29:18 okay, last one 15:29:20 #link https://bugzilla.redhat.com/show_bug.cgi?id=1558485 15:29:22 #info BZ 1558485 was accepted on 2018-08-02 15:29:23 #info no activity on the bug since 2018-08-10 15:31:39 so, I think from https://bugzilla.redhat.com/show_bug.cgi?id=1558485#c6 15:31:43 that this is really a documentation issue 15:31:53 halfline: you around? can you confirm? 15:32:20 "halfine" is Ray Strode and he knows everything there is to know about GDM :) 15:33:16 guess not, at least not immediately. 15:33:22 bcotton can you follow up with ray? 15:33:37 and maybe if it *is* a docs problem, we can find someone from docs team to write it up for quickdocs 15:33:59 can do. i'll also look and see if upstream has an issue for it 15:34:09 thanks 15:34:19 #action bcotton to follow up with halfline on BZ 1558485 15:34:38 hey i'm here 15:34:39 anything else on the existing bugs? 15:34:44 oh cool 15:34:48 oh hi, halfline, just in time :-) 15:34:54 * halfline clicks 15:35:20 My understanding is that this is partially irrelvant because we're not suspending by default anymore 15:35:29 that should be true from the login screen too, right? 15:35:59 and second, this can be configured but it's just not well documented. 15:36:36 hmm 15:37:38 yea not sure. 15:38:00 i mean you could argue the user settings should be transfered to the login screen automatically on single user systems 15:38:21 but things are working "as designed" at the moment 15:38:38 as i understand it 15:39:00 The justification for having it as a prioritized bug is basically... 15:39:21 We don't want to upset and surprise users who have turned off suspend in their user accounts, but then it still happens globally 15:39:44 it seems to me that since we're not suspending by default that isn't really a practical problem right now 15:40:04 but if we just turned it off for users but not gdm then we do have that problem 15:40:05 also we stop the login screen when you're logged in now 15:40:44 i don't actually know if we turned it off or not, will have to investigate 15:40:56 halfline: thanks. appreciate it! 15:41:23 halfline: so we can come back to you in two weeks? 15:41:32 sure 15:41:38 or update bug before that, of course :) 15:42:19 #undo 15:42:19 Removing item from minutes: ACTION by bcotton at 15:34:19 : bcotton to follow up with halfline on BZ 1558485 15:42:33 #action halfline to follow up on the bug and provide an update 15:42:37 #undo 15:42:37 Removing item from minutes: ACTION by bcotton at 15:42:33 : halfline to follow up on the bug and provide an update 15:42:49 #action halfline to follow up on BZ 1558485 and provide an update 15:43:05 okay. anything else on prioritized bugs? 15:43:15 I'm good. Thanks Ben! 15:43:45 mattdm: re 1548586, bcl and i would like it to be fixed in f28 15:43:56 (and f27, if it affects that) 15:44:03 i think it probably is fixed in f29 15:44:23 one thing it causes is, you can't generate an updated installer image on f28. because it tries to pull in conflicting package from the main repo and the updates repo. 15:44:38 ahhh. yeah that's bad. 15:45:15 adamw: do you know if the fix can be backported to dnf 2? 15:45:43 bcotton: I don't know that, no. 15:45:43 asking more for curiousity than for an impact on whether or not we should prioritize the bug 15:46:11 ok 15:46:24 it would probably be good to ask pbrobinson etc. if it is affecting composes of IoT and atomic for f28 15:46:30 as per https://bugzilla.redhat.com/show_bug.cgi?id=1548586#c12 15:47:21 #action bcotton to check with pbrobinson on the impact BZ 1548586 is having on IoT and Atomic F28 composes 15:48:08 #action bcotton to update BZ 1548586 to indicate we'd like it fixed for F27 and F28 as well 15:48:57 last call 15:50:12 #topic Next meeting 15:50:14 #info The next meeting is 26 September at 1500 UTC in #fedora-meeting 15:50:24 cool. see you then! 15:50:25 okay, thanks everyone! 15:50:32 well, also, before. but on this topic, then 15:50:33 thanks guys, sorry for the late chip-in 15:50:36 thanks bcotton 15:50:46 thanks to adamw and halfline for appearing when summoned :) 15:50:48 halfline++ 15:50:51 adamw++ 15:50:51 mattdm: Karma for adamwill changed to 4 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:50:56 adamw++ 15:50:56 bcotton: Karma for adamwill changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:50:59 halfline++ 15:50:59 bcotton: Karma for rstrode changed to 5 (for the current release cycle): https://badges.fedoraproject.org/tags/cookie/any 15:51:03 karma for everyone! 15:51:07 #endmeeting