14:00:34 #startmeeting Prioritized_bugs_and_issues 14:00:34 Meeting started Wed May 24 14:00:34 2017 UTC. The chair is jkurik. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:34 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:00:34 The meeting name has been set to 'prioritized_bugs_and_issues' 14:00:36 #meetingname Fedora Prioritized bugs and issues 14:00:36 The meeting name has been set to 'fedora_prioritized_bugs_and_issues' 14:00:45 #topic Purpose of this meeting 14:00:47 #info The purpose of this process is to help with processing backlog of bugs and 14:00:48 #info issues found during the development, verification and use of Fedora distribution. 14:00:50 #info The main goal is to raise visibility of bugs and issues to help 14:00:57 #info contributors focus on the most important issues. 14:00:58 #link https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues_-_the_process 14:01:00 #info Currently we have 2 proposed bugs for evaluation and 8 bugs already approved for review. 14:01:08 #topic Roll Call 14:01:10 #chair jkurik mattdm mcatanzaro dustymabe sgallagh roshi 14:01:10 Current chairs: dustymabe jkurik mattdm mcatanzaro roshi sgallagh 14:01:11 do we have someone around today ? 14:01:16 I'm here 14:01:28 .hello sgallagh 14:01:29 sgallagh: sgallagh 'Stephen Gallagher' 14:01:41 Hi sgallagh and mattdm 14:01:54 #topic Evaluation of bug #1306992: PackageKit accumulate over 18GBytes of RPM packages in /var/cache/PackageKit/metadata and fill my root filesystem with unused RPM files 14:01:56 #link https://bugzilla.redhat.com/show_bug.cgi?id=1306992 14:02:16 I talked to hughsie about this briefly 14:02:45 filed upstream issue 14:02:47 #link https://github.com/hughsie/PackageKit/issues/194 14:03:02 .hello roshi 14:03:03 roshi: roshi 'Mike Ruckman' 14:03:17 morning folks :) 14:03:22 some of this is "needs coordination with dnf" 14:03:30 good afternoon roshi 14:03:31 which aiui is ironically waiting on DNF to move to libdnf 14:03:40 not a typo :) 14:04:33 do you know whether we have a ticket describing what needs to be moved to libdnf ? 14:04:36 Anyway I'm +1 to making this a prioritized bug. It's clearly problematic 14:05:04 jkurik: that I don't know. Possibly worth a meeting with the DNF team 14:05:31 the "needs coordination with" part is not really a blocker for this particular issue, but with that they could share cache 14:06:11 mattdm: thanks for getting the status 14:06:25 jkurik: np! 14:06:51 ok, so finaly I am +1 to make it as a prioritized bug 14:07:03 $ sudo du -sh /var/cache/PackageKit 14:07:04 sgallagh, roshi: what is your POV ? 14:07:04 [sudo] password for mattdm: 14:07:06 9.5G /var/cache/PackageKit 14:07:08 :-( 14:07:16 Sorry, got distracted. 14:07:18 * sgallagh reads 14:07:23 that's so sad it deserves a sad face with an old-school nose 14:07:59 IMO packagekit shouldn't download anything in advance 14:08:28 ignatenkobrain: DIfferent problem, take it elsewhere please. 14:08:32 ignatenkobrain: I think that's a different issue. 14:08:44 The problem is more that the cache isn't cleaned effectively later. 14:08:46 I'm +1 here 14:09:45 looks like we have lost roshi 14:10:08 so there are +3 and no -1 14:10:41 #agreed The bug #1306992 has been accepted on the list of prioritized bugs 14:10:55 #topic Evaluation of bug #1434619: systemd-vconsole-setup.service fails to start on F26 Alpha base cloud image 14:10:56 #link https://bugzilla.redhat.com/show_bug.cgi?id=1434619 14:12:01 sorry 14:12:13 in house thing needed taken care of right away 14:12:19 jkurik: isn't this a final blocker already? 14:12:31 This is an accepted blocker. No need to put it on this list. 14:12:49 correct 14:12:49 although I think dusty's frustration is that no one has looked at it 14:13:00 sgallagh: can you talk to the systemd folks? 14:13:11 * roshi is retroactively +1 :) 14:13:14 and here now 14:13:39 mattdm: I'm not sure what I can do past pinging them and saying "hey, this is a blocker... any input"? 14:13:41 But sure 14:13:46 dusty put it on the list to see if we could get a fix in before beta, iirc 14:13:49 sgallagh: it's a good start :) 14:14:12 if that doesn't get any response, we can escalate 14:14:14 roshi: That would necessitate a Freeze Exception as well 14:14:42 #agreed The bug #1306992 has not been accepted on the Prioritized list as it is already on the list of Accepted Blockers 14:16:07 #topic Review of bug #893179: Automatic MacOSX grub entries are broken (and weird) 14:16:08 #link https://bugzilla.redhat.com/show_bug.cgi?id=893179 14:16:12 sure 14:17:30 I do not have any update on the bug #893179, so I will ask Alberto to provide some. 14:17:37 Remind me what we said our selection criteria was going to be, again? 14:17:45 thanks jkurik. looks like he's waiting on pjones 14:18:12 sgallagh: " 14:18:14 Issues eligible for this status would be those which do not necessarily fail a release criterion but which have critical impact on a Fedora Edition or on a council-approved Fedora Objective. Issues may also be nominated from the Common Bugs list when they are deemed by QA to have critical impact." 14:18:28 * pjones looks 14:18:42 yay pjones 14:19:01 Hi pjones, shall we ask you to look at the https://bugzilla.redhat.com/show_bug.cgi?id=893179 ? 14:19:05 mattdm: In our first meeting, we listed some criteria we agreed upon 14:19:14 jkurik: I literally just said I was looking, geez. 14:19:16 But that never made it to the "Evaluation" section of the page on this 14:19:38 pjones: sorry :) 14:20:53 I would think something like what christian kellner posted is the right thing. I *think* we're just creating whatever os-prober tells us to? 14:21:13 "The general criteria should be something like: "Failure to resolve this bug will result in unpleasantness for a subjectively large subset of users"" 14:21:18 That's what I was looking for 14:21:41 Which I guess did make it to that page. 14:21:46 I'm not sure this should be on the prioritized list. Especially since the proposed resolution seems to be "tell people to do the thing that they currently need to do" 14:21:47 I just thought I remembered it being less vague 14:21:56 hm. yeah, probably not even hard to fix. 14:22:04 although I'm glad for pjones to fix it :) 14:22:47 Correct me if I'm wrong, but this doesn't even hit a majority of Apple users, does it? 14:23:20 I would expect most of them hold down option or whatever to get the mac bootloader screen, which we do install an entry into, and thus no. 14:23:48 why you would want to add grub into the macos boot path is beyond me. 14:24:11 proposal: drop this from the list, document the thing pjones said, move on, and pjones to fix the grub thing to tie it off 14:24:49 Oh, I see - it's because we're becoming the default, I guess, and so you need to hit option in order to boot macos. 14:25:03 I am OK to remove this bug from the list 14:25:08 so the reason people are using grub is basically path of least resistance 14:25:09 mattdm: +1 14:25:44 +1 from me as well 14:26:04 * roshi isn't quite sure if he's a voting member of this group (does it have a name?) 14:26:05 #agreed Bug #893179 is removed from the list of prioritized bugs as it hits just minority of users 14:26:08 and then pjones to come up with whatever fix he thinks is best :) 14:26:44 roshi: it is the same as on blocker meeting - who appears have the permission to vote 14:26:49 roshi: Prioritized Bugs Evaluation Team. ANd you're on the list if you have a stake and show up :) 14:26:57 :D 14:27:15 #action pjones to come up with whatever fix he thinks is best for bug #893179 14:27:24 ok, moving on... 14:27:30 pjones: thanks 14:27:39 oh ugh. i have to run away for something. I'll follow up with the minutes here later. if you need me to track something down for any of the open bugs, give me a an action 14:27:48 #topic Review of bug #1366004: [abrt] setroubleshoot-server: service.py:647:_message_cb:SystemError: returned a result with an error set 14:27:50 #link https://bugzilla.redhat.com/show_bug.cgi?id=1366004 14:29:58 I do not see any progress, just more occurences appears 14:30:11 Yeah 14:30:28 looks like 14:31:25 #action jkurik to ping the assignee and ask for a status 14:31:45 #topic Review of bug #1340203: goa-daemon not stopped on logout, and gnome-keyring unusable on next log in 14:31:46 #link https://bugzilla.redhat.com/show_bug.cgi?id=1340203 14:32:26 This one's been marked a Final Blocker. 14:32:36 I'm not sure why it's on our list at that point 14:32:40 We should probably drop it 14:33:28 it was on the Prioritized list first and then it was accepted as the blocker 14:34:02 proposal: Drop it from our list since it's now a blocker 14:34:23 ack 14:34:29 ack 14:34:31 #agreed Drop it from our list since it's now a blocker 14:34:46 #topic Review of bug #1146232: no VM networking; 'default' network in the VM conflicts with 'default' network on the host 14:34:47 #link https://bugzilla.redhat.com/show_bug.cgi?id=1146232 14:36:34 No progress on this 14:37:58 I will ping the assignee 14:38:10 #action jkurik to ping the assignee 14:38:25 #topic Review of bug #1375468: [abrt] nautilus: nautilus_window_slot_get_allow_stop(): nautilus killed by SIGSEGV 14:38:27 #link https://bugzilla.redhat.com/show_bug.cgi?id=1375468 14:39:25 No progress and the assignee has already been asked to provide a status 14:39:32 just to track back, was there somebody here who can actually test #893179? 14:39:40 * pjones has needinfo'd it 14:40:23 sgtm 14:40:35 * roshi has not been tracking any of these bugs, aside from the blockers 14:41:04 pjones: I am aware of the reporter only 14:42:35 #action jkurik to ask Matthias about status 14:42:48 #topic Review of bug #1405539: changing the default keyboard layout changes also disk decryption in plymouth, but only after kernel update, long after 14:42:49 #link https://bugzilla.redhat.com/show_bug.cgi?id=1405539 14:43:29 * roshi remembers this one 14:44:33 * sgallagh hates this one 14:44:44 me too 14:45:08 so, I dunno 14:45:24 Honestly, I'm not sure this is an actual solvable problem :-( 14:45:28 we could bikeshed on the wording forever, basically 14:46:44 there's no good solution from what I can tell 14:47:28 have a link to some mega document that explains luks and keyboard layouts? 14:47:36 makes sense to put this on common bugs list and close it ? 14:47:46 I guess? 14:47:54 I'm not convinced this is a bug 14:49:12 sgallagh: what is your POV ? 14:52:05 I'd just drop this from our list 14:52:36 But I'm unsure. 14:52:43 I mean, when this happens, it's *bad* 14:52:59 But at the same time, a lot of people smarter about this than I am haven't found a solution. 14:53:08 but the issue at hand is changing the wording 14:53:11 isn't it? 14:53:22 I mean, the best we could come up with was have a warning 14:53:33 I don't think that's a real solution 14:55:17 I might support the idea of dropping it from the list as it does not impact large set of users and it does not have a good solution, so having it on the list does not help to solve the issue 14:55:37 jkurik: +1 14:56:48 roshi: are you fine to drop it ? 14:56:53 yeah, I guess 14:57:02 #agreed Drop bug #1405539 from the list as it does not impact large set of users and it does not have a good solution, so having it on the list does not help to solve the issue 14:57:17 #topic Review of bug #1385432: Dracut exhibits numerous AVC denied errors during cleanup, takes long time to power off 14:57:19 #link https://bugzilla.redhat.com/show_bug.cgi?id=1385432 14:59:18 I might ask assignee to provide some status as it seems stalled 14:59:47 that works 14:59:52 #action jkurik to ping assigne to provide a status update 15:00:05 last one.... 15:00:09 #topic Review of bug #1413306: Pointer speed on some Dell laptops (XPS 13, Precision 5510...) too slow with recent libinput (inc. 1.6) 15:00:10 #link https://bugzilla.redhat.com/show_bug.cgi?id=1413306 15:00:46 fix has been pushed, so lets wait for the verification ... 15:01:19 sgtm 15:01:42 #info The bug is already in ON_QA, we will review it once more once it is verified. 15:01:54 sgallagh, roshi, mattdm: Thanks 15:02:02 #endmeeting