16:00:20 <roshi> #startmeeting F23-blocker-review
16:00:20 <zodbot> Meeting started Mon Oct 26 16:00:20 2015 UTC.  The chair is roshi. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:00:20 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
16:00:20 <roshi> #meetingname F23-blocker-review
16:00:20 <zodbot> The meeting name has been set to 'f23-blocker-review'
16:00:20 <roshi> #topic Roll Call
16:00:27 <adamw> ahoy
16:00:34 <roshi> ahoy
16:00:37 <jkurik> .hello jkurik
16:00:37 <zodbot> jkurik: jkurik 'Jan Kurik' <jkurik@redhat.com>
16:00:43 * kparal is here
16:00:47 * nirik is lurking around
16:00:51 * satellit listening
16:01:25 <kalev> ahoy
16:01:42 <roshi> #chair adamw jkurik kalev kparal nirik satellit tflink danofsatx
16:01:42 <zodbot> Current chairs: adamw danofsatx jkurik kalev kparal nirik roshi satellit tflink
16:01:58 <roshi> #topic Introduction
16:01:58 <roshi> Why are we here?
16:01:58 <roshi> #info Our purpose in this meeting is to review proposed blocker and nice-to-have bugs and decide whether to accept them, and to monitor the progress of fixing existing accepted blocker and nice-to-have bugs.
16:02:02 <roshi> #info We'll be following the process outlined at:
16:02:05 <roshi> #link https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting
16:02:06 * pschindl is here
16:02:07 <roshi> #info The bugs up for review today are available at:
16:02:10 <roshi> #link http://qa.fedoraproject.org/blockerbugs/current
16:02:12 <roshi> #info The criteria for release blocking bugs can be found at:
16:02:15 <roshi> #link https://fedoraproject.org/wiki/Fedora_23_Alpha_Release_Criteria
16:02:18 <roshi> #link https://fedoraproject.org/wiki/Fedora_23_Beta_Release_Criteria
16:02:21 <roshi> #link https://fedoraproject.org/wiki/Fedora_23_Final_Release_Criteria
16:03:04 * danofsatx is present, building VMs on RC3
16:03:29 <roshi> sweet sweet
16:03:39 <roshi> we've got 3 proposed
16:03:50 <roshi> first up
16:03:51 <roshi> #topic (1266756) [abrt] kf5-kwallet: qt_message_fatal(): kwalletd5 killed by SIGABRT
16:03:55 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1266756
16:03:57 <roshi> #info Proposed Blocker, kf5-kwallet, POST
16:05:09 <adamw> so this seems to happen on every 32-bit install, and presumably breaks kwallet (since it's looking for the file in the wrong place) - it's fairly bad. I'm +1 blocker
16:05:50 <brunowolff> +1 blocker
16:05:55 <kalev> I can see two +1's in the ticket too
16:05:58 <nirik> ok, +1 blocker...
16:06:05 <roshi> +1
16:06:08 <kalev> +1
16:06:12 <danofsatx> +1
16:06:30 <satellit> +1
16:06:42 <kparal> +1
16:06:43 <pschindl> +1
16:06:49 * satellit saw this in dnf system upgrade of i386 kde also
16:07:07 <roshi> proposed #agreed - 1266756 - AcceptedBlocker Final - This bug is a clear violation of the following criterion: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."
16:07:32 <kalev> ack
16:07:33 <pschindl> ack
16:07:39 <brunowolff> ack
16:07:42 <roshi> #agreed - 1266756 - AcceptedBlocker Final - This bug is a clear violation of the following criterion: "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop."
16:07:44 <satellit> ack
16:07:55 <danofsatx> late ack
16:07:57 <roshi> #topic (1271230) libssh agent support fails on big endian architectures
16:08:00 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1271230
16:08:03 <roshi> #info Proposed Blocker, libssh, ON_QA
16:08:05 * danofsatx is lagging bigtime because he can't see the screen
16:08:25 <brunowolff> Are any blocking arches big endian?
16:08:36 <danofsatx> aren't some ARMs big endian?
16:08:49 <kparal> this seems to be only request for a FE
16:09:06 <kparal> ah, good question
16:09:11 <nirik> yeah, +1FE (per the secondary arch clause)
16:09:15 <brunowolff> The request asks for both at once.
16:09:34 <kparal> +1 FE, -1 blocker unless it affects one of our primary arches
16:09:43 <adamw> i think the blocker request was probably accidental
16:09:45 <brunowolff> +1 FE
16:09:49 <adamw> but since it's there -1 / +1
16:09:53 <danofsatx> +1 FE
16:09:56 <jkurik> +1 FE, -1 blocker
16:09:59 <roshi> yeah -1/+1
16:10:01 <kalev> +1 FE, -1 blocker
16:10:03 <pschindl> +1 FE
16:10:30 <adamw> though, i sure hope taking it as an FE doesn't somehow break on little-endian...
16:10:41 * garretraziel joins in so quietly that nobody notices he is late
16:10:52 <kalev> yes, there's always the question of that
16:10:59 <nirik> yeah. ;(
16:11:36 <brunowolff> Well they better test it on little endian before trying to push through the build.
16:11:44 <roshi> proposed #agreed - 1271230 - RejectedBlocker AcceptedFreezeException Final - This bug doesn't qualify for blocker status, but we'd cosider pulling in a tested fix despite freeze.
16:11:53 <nirik> well, they is us too. it's in updates-testing. Please test. ;)
16:12:25 <kparal> roshi: "consider"
16:12:36 <kparal> ack
16:12:40 <jkurik> ack
16:12:42 <kalev> ack
16:12:43 <roshi> ah, right :)
16:13:00 <roshi> patched #agreed - 1271230 - RejectedBlocker AcceptedFreezeException Final - This bug doesn't qualify for blocker status, but we'd consider pulling in a tested fix despite freeze.
16:13:03 <danofsatx> ack
16:13:10 <roshi> #agreed - 1271230 - RejectedBlocker AcceptedFreezeException Final - This bug doesn't qualify for blocker status, but we'd consider pulling in a tested fix despite freeze.
16:13:27 <roshi> any volunteers to secretarialize?
16:13:40 <roshi> (or I can do it after the meeting)
16:13:57 <pschindl> roshi: I'll do it
16:14:06 <roshi> thanks pschindl :)
16:14:18 <roshi> #topic (1274904) [abrt] plasma-workspace: KCrash::defaultCrashHandler(): plasmashell killed by SIGSEGV
16:14:21 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1274904
16:14:24 <roshi> #info Proposed Blocker, plasma-workspace, NEW
16:15:07 <kalev> so many 32 bit blockers
16:15:25 <adamw> we kinda ran into them both at the same time
16:15:27 <kparal> adamw: what is 'kicker'?
16:15:34 <adamw> the 'start' meny
16:15:35 <adamw> menu*
16:15:39 <kparal> ok
16:15:49 <adamw> so you open it, start typing whatever you want to search for ('terminal' or whatever), it crashes.
16:15:56 <adamw> well, the whole plasma shell crashes.
16:16:04 <adamw> sometimes it respawns itself successfully, sometimes you wind up at a black screen.
16:16:08 <kparal> +1
16:16:09 <kalev> that sounds pretty bad
16:16:13 <danofsatx> confirmed. +1 blocker
16:16:17 <brunowolff> +1 blocker
16:16:20 <adamw> yeah, was planning to look into this one today.
16:16:22 <adamw> i'm +1.
16:16:22 <garretraziel> +1
16:16:23 <roshi> +1
16:16:24 * nirik can't wait for not blocking on 32bit intel. ;)
16:16:32 <kalev> +1
16:16:33 <adamw> yeah, that'd be nice :/
16:16:34 <nirik> +1 for now tho
16:16:46 <kalev> we don't have a fix for this one, right?
16:16:48 <danofsatx> does not appear in x86
16:16:56 <danofsatx> erm, x86_64
16:17:04 <roshi> proposed #agreed - 1274904 - AcceptedBlocker Final - This bug is a clear violation of the following criterion: "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use."
16:17:13 <danofsatx> ack
16:17:14 <kalev> ack
16:17:17 <jkurik> ack
16:17:19 <garretraziel> ack
16:17:28 <garretraziel> when I was testing it, whole Live KDE on pure-32bit CPU gave me an awful experience, I blame the computer though
16:17:28 <roshi> #agreed - 1274904 - AcceptedBlocker Final - This bug is a clear violation of the following criterion: "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use."
16:17:41 <roshi> that's all the proposed blockers
16:17:56 <roshi> moving on to FE's since there's still a good chance for them to get in the next compose
16:18:13 <roshi> #topic Proposed Freeze Exceptions
16:18:14 <roshi> #topic (1275163) Removed apps reappear as installed a few seconds after removal
16:18:17 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1275163
16:18:20 <roshi> #info Proposed Freeze Exceptions, gnome-software, MODIFIED
16:18:26 <danofsatx> +1, sounds reasonable
16:19:00 <kparal> +1
16:19:00 <nirik> +1FE
16:19:21 <roshi> sure +1
16:19:26 <jkurik> +1 as FE
16:19:30 <garretraziel> +1 FE
16:19:32 <adamw> how safe is the fix?
16:19:45 <adamw> do you have the patch link handy, kalev?
16:19:51 <kalev> very safe, it basically brings it back to the same code as in 3.16
16:20:19 <kalev> https://git.gnome.org/browse/gnome-software/commit/?h=gnome-3-18&id=8bdfdb2c8378780c0fd9b7a33f4a4df73179a496
16:20:42 <adamw> OK, yeah, doesn't look too scary.
16:20:43 <adamw> +1
16:20:50 <pschindl> +1
16:21:34 <roshi> proposed #agreed - 1275163 - AcceptedFreezeException Final - The fix for this looks safe enough and it'd be good to get this pulled into the next compose.
16:21:42 <kalev> ack
16:21:49 <danofsatx> ack
16:21:57 <kparal> ack
16:21:59 <garretraziel> ack
16:22:01 <adamw> ack
16:22:05 <roshi> #agreed - 1275163 - AcceptedFreezeException Final - The fix for this looks safe enough and it'd be good to get this pulled into the next compose.
16:22:13 <roshi> #topic (1274869) Two volume icons on KDE's panel after upgrade (F22->F23)
16:22:16 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1274869
16:22:18 <roshi> #info Proposed Freeze Exceptions, kmix, MODIFIED
16:22:44 <danofsatx> -4
16:22:50 <danofsatx> erm, -1 even
16:23:34 <kalev> rdieter was -1 in the ticket and he understands the issue the best
16:23:44 <kalev> -1 from me as well then :)
16:23:55 * adamw reads
16:24:02 <adamw> danofsatx: i'm pretty sure you don't have that many votes ;)
16:24:03 <nirik> -1 here too... and looks like we will have a 0 day kmix update that fixes it.
16:24:13 <kparal> this can be fixed in 0-day updates and we don't gain anything be pushing this to the main repo I think
16:24:18 <kparal> *by
16:24:28 <roshi> -1
16:24:29 <jkurik> -1
16:24:30 <adamw> yeah, doesn't sound like it
16:24:31 <adamw> -1
16:24:43 <garretraziel> -1
16:25:13 <danofsatx> adamw: I can't type today. or, I can't proofread what I type that well...
16:25:29 <roshi> proposed #agreed - 1274869 - RejectedFreezeException Final - This bug can be fixed via updates and is not severe enough to break freeze for it.
16:25:43 <jkurik> ack
16:25:47 <danofsatx> ack
16:25:57 <danofsatx> I wouldn't even call it a bug.
16:26:11 <rdieter> danofsatx: having both is pretty bad though
16:26:17 <rdieter> well, bad'ish
16:26:22 <garretraziel> ack
16:26:22 <roshi> me either - but it is in the *bug* *tracker*
16:26:34 <danofsatx> it's annoying, but it's not a bug. An issue, maybe, but it doesn't break anything.
16:26:47 <rdieter> danofsatx: actually it does break media keys
16:26:47 * roshi imagines tiny gps devices strapped to the heads of bugs
16:26:52 <rdieter> (when both are running)
16:26:59 <roshi> #agreed - 1274869 - RejectedFreezeException Final - This bug can be fixed via updates and is not severe enough to break freeze for it.
16:27:05 <danofsatx> hmm...I didn' catch that
16:27:12 <roshi> #topic (1275273) include muon in kickoff favorites (instead of apper)
16:27:15 <kalev> rdieter: it doesn't affect the live images though, right? just upgrades from F22?
16:27:16 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1275273
16:27:18 <roshi> #info Proposed Freeze Exceptions, plasma-desktop, MODIFIED
16:27:34 <rdieter> kalev: correct
16:27:57 <danofsatx> +1 for muon-discover
16:28:39 <kalev> +1, makes sense to ship a working thing instead of a broken one :)
16:28:55 <nirik> sure, +1FE
16:28:58 * jkurik has no idea what this bug is about :(
16:29:03 <adamw> do we know muon-discover actually *works* now?
16:29:07 <satellit> +1 (have not tested it though)
16:29:11 <adamw> last time this came up a few weeks ago, i thought it was brokenb
16:29:12 * roshi is in the same boat as jkurik
16:29:22 <danofsatx> hmmm....
16:29:22 <kalev> KDE has two package managers, Apper and Muon and the former is horribly broken. they want to switch to the latter now.
16:29:23 * danofsatx checks
16:29:48 * roshi will defer to actual kde users
16:30:03 <danofsatx> wtf? I can't find it on this system...
16:30:43 * satellit fallback is to use terminal with dnf...
16:30:46 <rdieter> adamw: yes, it works
16:30:56 <danofsatx> yep, it's working now
16:30:59 <rdieter> I sorted it out with appstream maintainer
16:31:16 <danofsatx> it's in the RC3 image, and works fine
16:31:35 <rdieter> works since https://bodhi.fedoraproject.org/updates/FEDORA-2015-77b834245b
16:31:38 <adamw> alright, i guess, fine
16:31:39 <roshi> looks like we're generally in favor then
16:31:44 * danofsatx would check the 32 bit version, but the shell keeps crashing
16:31:46 <jkurik> satellit: yes, that is what I do all the time
16:31:53 <adamw> it would be appreciated if we could come up with some kind of coherent story about KDE package management for f24 though :P
16:31:58 <adamw> +1
16:32:31 <roshi> proposed #agreed - 1275273 - AcceptedFreezeException Final - It would be good to get a tested fix for this into the next compose.
16:32:47 <kalev> ack
16:32:50 <danofsatx> ack
16:32:51 <nirik> ack
16:32:57 <satellit> ack
16:33:17 <roshi> #agreed - 1275273 - AcceptedFreezeException Final - It would be good to get a tested fix for this into the next compose.
16:33:27 <roshi> #topic (1271993) CVE-2015-0856 sddm: Access to the KDE crash handler [fedora-all]
16:33:30 <roshi> #link https://bugzilla.redhat.com/show_bug.cgi?id=1271993
16:33:32 <roshi> #info Proposed Freeze Exceptions, sddm, ON_QA
16:34:43 <kparal> might be even a blocker, since it's CVE, I believe
16:34:55 <roshi> what's the actual bug though?
16:35:00 <danofsatx> is it so hard to actually include a summary of the CVE in the BZ?
16:35:04 <roshi> the CVE just says "reserved"
16:35:10 * danofsatx hates having to click *again* to figure out WTF the problem is
16:35:18 <adamw> well while we're chaning every other goddamn thing in KDE...
16:35:40 <nirik> https://github.com/sddm/sddm/commit/4cfed6b0a625593fb43876f04badc4dd99799d86
16:35:42 <nirik> has more info
16:35:45 <jkurik> +1 to FE as we will have an update in F22 and we do not want to have regressions
16:36:02 <adamw> so, fine, i guess. +1
16:36:06 <nirik> +1 FE as this sddm will be on the media...
16:36:06 <kalev> +1
16:36:15 <roshi> ah, there it is
16:36:24 <roshi> +1
16:36:32 <danofsatx> +1
16:36:36 <garretraziel> +1
16:37:22 <roshi> proposed #agreed - 1271993 - AcceptedFreezeException Final - It would be good to ensure our spins don't have any known, active CVEs in them. Accepted as a Freeze Exception.
16:37:39 <jkurik> ack
16:37:46 <danofsatx> ack
16:37:49 <garretraziel> ack
16:37:55 <roshi> #agreed - 1271993 - AcceptedFreezeException Final - It would be good to ensure our spins don't have any known, active CVEs in them. Accepted as a Freeze Exception.
16:38:01 <roshi> that's it for the FEs
16:38:26 <kalev> I'd like to follow up to one of the FE's that were pulled in to RC3
16:38:30 <roshi> go through the accepted blockers, or back to testing?
16:38:38 <roshi> go for it kalev
16:38:43 <roshi> you have chair
16:38:49 <kalev> https://bugzilla.redhat.com/show_bug.cgi?id=1274319 was one of the FE's I asked for, the yumdb fix
16:39:10 <adamw> yes
16:39:23 <kalev> the way I was hoping to have gnome-software look was:
16:39:26 <kalev> https://kalev.fedorapeople.org/gnome-software-yumdb2.png
16:39:34 <kalev> but where we really ended up was:
16:39:36 <kalev> https://kalev.fedorapeople.org/gnome-software-yumdb3.png
16:39:56 <kparal> #topic https://bugzilla.redhat.com/show_bug.cgi?id=1274319
16:40:19 <adamw> iirc we get that for packages pulled in from bleed
16:40:27 <adamw> is shotwell part of the 3.18.1 mega-update?
16:40:38 <adamw> hmm, no.
16:40:43 <kalev> no
16:40:46 <adamw> then, i dunno. must be something to do with the compose process.
16:40:59 <kalev> the issue is that releng doesn't use repos defined in kickstart for the compose
16:41:08 <kalev> but they override it on the koji command line and koji autogenerates repo names
16:41:21 <kalev> "fedora" gets renamed to koji-override-0
16:41:27 <kalev> and bleed gets renamed to koji-override-1
16:41:33 <nirik> this seems pretty cosmetic. ;)
16:41:39 <kalev> yup :)
16:41:48 <danofsatx> purely, imho
16:42:00 <kalev> just wanted to ask for guidance, is it something you guys would want to have fixed?
16:42:09 <nirik> might be nice to fix in f24, but I don't know that we want to monkey with koji right now
16:42:21 <kalev> we could possible do a sed run on the yumdb to fix up koji-override-0 -> fedora
16:42:41 <kparal> I wouldn't do this at this point
16:42:43 <kalev> (the yumdb is just a bunch of plaintext files)
16:42:48 <kalev> okay, fair enough, I'll let it be then
16:42:50 <adamw> the only person i can remember who ever even noticed it before was kk
16:42:59 <adamw> i wouldn't want to start futzing around at this point, no
16:43:00 <danofsatx> is that screenshot from a live or installed system?
16:43:05 <kalev> installed system
16:43:13 <adamw> if you want to deal with it, deal with it, but for f24 i think
16:43:16 <kalev> I'll work with releng to fix this properly for F24
16:43:23 <jkurik> if it does not make any other issue, this does not seem to be severe enough to play with it now
16:43:24 <roshi> sgtm
16:43:31 <bradfirj> Question, does that reset to the correct Fedora label once you do a dnf update for the first time on your new system?
16:43:38 <kalev> no
16:44:01 <roshi> but it would when that package gets an update, right?
16:44:01 <kalev> it stays like this for any packages that were part of the live media
16:44:03 <nirik> I have had people ask in #fedora about this...
16:44:04 <kalev> yes
16:44:20 <roshi> it's fine for now - can fix for F24
16:44:26 <kalev> ok
16:44:37 <kalev> I'll come up with a proper fix for F24 that doesn't require seding yumdb :)
16:44:43 <roshi> though, I'd rather see "koji-override-0" -> Fedora Live Image or something
16:44:55 <roshi> saying where it *actually* came from
16:45:04 <roshi> since it wasn't Fedora proper
16:45:13 <roshi> awesome, thanks kalev
16:45:27 <kalev> ok, nothing else from me, thanks guys
16:46:16 <roshi> accepted blockers now, or get back to testing?
16:46:52 * adamw checks if there's anything worth saying about accepted blockers
16:47:08 <adamw> nothing really interesting
16:47:13 <adamw> if folks could karma the anaconda update it'd be good
16:47:15 <roshi> that was kinda my thought
16:47:21 <roshi> #topic Open Floor
16:47:31 <roshi> anyone have anything else?
16:48:00 * kparal adds karma
16:49:04 <adamw> i'll test the potential fix for the KDE blocker now and then file an RC4 request if it works
16:49:12 * jkurik has nothing to discuss now
16:50:53 <danofsatx> Do we have "usual" contributors that do the Arabic and Asian language test cases?
16:51:43 <adamw> i usually do those./
16:51:59 <adamw> i did asian for TC11 or something back there,
16:52:13 <adamw> the buttons are the same in the installer whatever the text on them says. :P
16:52:40 <danofsatx> I'm teaching a Linux class this afternoon that uses  Fedora as the example system. This class has quite a few Saudi Arabian students, and I think at least one from Viet Nam. I can have them run through the tests
16:53:39 <roshi> that'd be great
16:53:43 * roshi sets the fuse...
16:54:57 <kalev> hughsie pointed out that we can do a hack to map koji-override-0 to fedora in gnome-software too and do a post-GA update with the hack
16:55:48 <kalev> or maybe even the PackageKit backend so that KDE benefits
16:55:51 <kalev> too
16:56:06 <nirik> that won't help dnf/yum directly tho. but sure.
16:56:22 * kalev nods.
16:57:19 <roshi> thanks for coming folks!
16:57:27 <roshi> 3...
16:57:32 <jkurik> thanks for chairing roshi
16:58:12 <roshi> np :)
16:58:14 <roshi> 2...
16:58:27 <roshi> being a meeting jockey is just one of the services I provide :p
16:59:04 <roshi> 1...
16:59:07 <roshi> #endmeeting