[08:09] <dholbach> good morning
[10:43] <Mirv> jaywink: on older Ubuntus we so far have just provided the Qt Creator + emulator etc, which means the old Ubuntu's older Qt version is used, which explains the problem. Soon everyone will be updated to a new SDK IDE package that contains a whole new Qt version (not conflicting with the system Qt version) too.
[10:44] <jaywink> Mirv, sounds good, thanks for the note! It's good to keep trusty as a valid dev host
[10:45] <Mirv> jaywink: exactly, that's how it will be. just before the upgrade supported run targets are hardware + emulator, not the desktop itself.
[10:45] <Mirv> but that'll soon change too
[13:52] <t1mp> hello there, what did I miss? ;)
[13:54] <ahayzen> t1mp, o/ bug 1514143 ;-)
[13:54] <ubot5`> bug 1514143 in ubuntu-ui-toolkit (Ubuntu) "While searching often times the keyboard hides while typing" [Critical,In progress] https://launchpad.net/bugs/1514143
[13:54] <t1mp> ahayzen: I'm on it :)
[13:54] <ahayzen> thanks man :-)
[13:54] <t1mp> ahayzen: victor's analysis was correct, we're a bit too eager to set 'moving' to true internally.
[13:54] <ahayzen> t1mp, is that likely to get into OTA8? :')
[13:55] <t1mp> ahayzen: I have a fix, writing some regression tests now.
[13:55] <t1mp> ahayzen: the fix will be in our staging this week for sure. I am not sure when the next landing to trunk is though
[13:55] <t1mp> when is OTA8?
[13:55] <ahayzen> 'soon', maybe this week :(
[13:55] <t1mp> (I just returned from my holidays, still need to catch up a bit)
[13:55]  * ahayzen wonders how many other apps that have already bumped this affects
[13:56] <ahayzen> like any that have a search in the header are likely affected
[13:56] <t1mp> right
[13:57] <t1mp> bzoltan, zsombi: what do I need to do to get a fix in OTA8?
[13:57] <zsombi> t1mp: luck :D
[13:57] <t1mp> and maybe more important, *when* do I need to get it done?
[13:57] <ahayzen> t1mp, buy QA a beer ;-)
[13:57] <zsombi> t1mp: and magic
[13:58] <zsombi> t1mp: OTA8 train has left the building :)
[13:58] <bzoltan> t1mp: You just give me the MR
[13:58] <bzoltan> t1mp:  against the trunk not the staging!
[13:58] <t1mp> bzoltan: I don't have the MR yet. I'm working on it. That's why I asked the *when* question.
[13:58] <bzoltan> t1mp:  two weeks ago
[13:58] <zsombi> t1mp: ota8 gates are closed for 6 days
[13:59] <bzoltan> zsombi:  :) exactly
[13:59] <zsombi> t1mp: so you missed that, ota9 maybe
[13:59] <t1mp> okay. It seems to me then that the fix for bug 1514143 will go to ota9
[13:59] <ubot5`> bug 1514143 in ubuntu-ui-toolkit (Ubuntu) "While searching often times the keyboard hides while typing" [Critical,In progress] https://launchpad.net/bugs/1514143
[13:59] <ahayzen> t1mp, does the address-book have a search? as it may affect that
[14:01] <ahayzen> t1mp, hmm address-book is fine when you search
[14:01] <t1mp> ahayzen: the address book has a locked header, and I think locked headers are not affected
[14:01] <ahayzen> ahhh thats why
[14:01] <t1mp> the problem occurs when the flickable contents height changes
[14:01] <ahayzen> ok that makes sense
[14:01] <t1mp> ahayzen: so I'll have it fixed soon, but too late for OTA8
[14:02] <ahayzen> :-/
[14:02] <t1mp> ahayzen:  you could temporarily lock your header
[14:02] <ahayzen> t1mp, yeah was about to say as a workaround, when entering search we could lock the header
[14:03] <ahayzen> t1mp, ok we'll do that then until OTA9 :-)
[14:03] <t1mp> okay, cool
[14:03] <t1mp> sorry for the breakage. I'll add a regression test so it won't happen again.
[14:05] <t1mp> bzoltan: I'll make the MR for staging and hopefully we can land that for OTA9
[14:05] <ahayzen> t1mp, thanks
[14:06] <bzoltan> t1mp: if that is fine with pmcgowan then it is good
[14:06] <t1mp> pmcgowan: ^ can the fix for bug 1514143 go to OTA9?
[14:06] <ubot5`> bug 1514143 in ubuntu-ui-toolkit (Ubuntu) "While searching often times the keyboard hides while typing" [Critical,In progress] https://launchpad.net/bugs/1514143
[14:25] <pmcgowan> bzoltan, once you have the fix we can decide whether to hotfix or wait for the ota, will see what QA things
[14:28] <bzoltan> pmcgowan: Thanks! I agree.
[14:28] <bzoltan> t1mp:  so just watch out to make it in a way that we can retarget if needed
[14:28] <t1mp> okay
[15:14] <popey> balloons, jenkins looks unwell.. lots of clocks https://core-apps-jenkins.ubuntu.com/
[15:14] <popey> (morning btw) :D
[15:17] <popey> looks like it's running against the wrong branch according to sverzegnassi_  balloons
[15:30] <balloons> popey, morning to you!
[15:30] <balloons> I'll look
[15:31] <balloons> ahh.. offline
[15:44] <beni_> hei
[15:45] <beni_> appdevs
[15:46] <beni_> are there any appdevs?
[15:51] <popey> beni_, ya
[18:45] <ahayzen> balloons, any idea why jenkins hasn't merged this? https://code.launchpad.net/~vthompson/music-app/music-uc1.3-now-playing-fix-1447428/+merge/275635
[19:25] <popey> oooh!
[19:26] <popey> ahayzen, jenkins was busted earlier today, it might need re-approving to nudge it? balloons ?
[19:26] <ahayzen> popey, oo
[19:26] <balloons> ahayzen, indeed, jenkins was broken this morning. I wasn't sure if the old jobs got re-run or not
[19:26] <popey> i believe it's supposed to be fixed now
[19:27] <balloons> ohh.. that merge has never been run by the new jenkins
[19:27] <ahayzen> balloons, that mp, and this one hasn't had jenkins comment on it yet https://code.launchpad.net/~ahayzen/music-app/fix-1514143-workaround/+merge/277611
[19:27] <ahayzen> yup, its all appproved :-)
[19:28] <balloons> interesting
[19:28] <balloons> let's look
[19:37] <balloons> ahayzen, d'oh!
[19:37] <balloons> found the issue
[19:37] <ahayzen> :-)
[19:38] <balloons> it's doing lots of stuff now
[19:38] <ahayzen> \o/
[19:38] <balloons> btw, it is lp:music-app, not lp:ubuntu-music-app
[19:38] <balloons> lol
[19:38] <ahayzen> balloons, up lp:music-app
[19:38] <ahayzen> *yup
[19:38] <ahayzen> lol
[19:39] <ahayzen> boom \o/ thanks balloons :-)
[19:40] <balloons> ahayzen, let me know if you see anymore weirdness, but yes, things should be happening now on music
[19:40] <balloons> sorry about that!
[19:40] <ahayzen> balloons, will do ... unrelated, and a bit obscure, was wondering if you can connect Vis to an app running on a device ?
[19:41] <ahayzen> i can use the print_tree as a sortof workaround but Vis is slightly nicer
[19:41] <balloons> in theory, yes. In practice, no
[19:41] <ahayzen> hah!