[06:04] <didrocks> thomi: hey, around? it seems there are a lot of QA tests failing (autopilot tests on autopilot)
[06:04] <didrocks> thomi: https://jenkins.qa.ubuntu.com/job/ps-generic-autopilot-release-testing/370/
[07:04] <thomi> didrocks: already fixed in a MP :)
[07:04]  * thomi is EOD now
[07:04] <sil2100> !
[07:04] <didrocks> thomi: oh, everything \o/ ;)
[07:04] <sil2100> \o/
[07:04] <thomi> sorry guys - I've been up since 2AM
[07:04] <didrocks> hey sil2100! so it seems we can rerun the QA stack!
[07:04] <thomi> time to sleep
[07:05] <sil2100> thomi, didrocks: yaay!
[07:05] <didrocks> thomi: no, perfect, we'll rerun the stack now, rocking! :-)
[07:05]  * sil2100 was worried he'll miss thomi 
[07:05] <didrocks> thomi: enjoy, see you tomorrow :)
[07:05] <didrocks> sil2100: quick quick quick! can't wait to see the QA stack passing :)
[07:07] <sil2100> didrocks: all is merged already ;)?
[07:08] <didrocks> ah, not sure what thomi meant in fact :)
[07:08] <didrocks> sil2100: mind checking trunk and MPs if not there? ;)
[07:08] <sil2100> I'm checking that
[07:09] <sil2100> I see two MR's filled in approx an hour ago
[07:11] <didrocks> sil2100: do you have enough knowledge to review them?
[07:13] <sil2100> didrocks: those already got reviewed and approved by Martin it seems, just waiting for the merger to finish merging
[07:13] <sil2100> But I wonder if all the commits will fix our problems, hmmm
[07:13] <didrocks> sil2100: let's it give it a try once merged :)
[07:14] <didrocks> sil2100: how are we on the other apps front? did you see that UTAH was behaving quite well tonight?
[07:17] <sil2100> didrocks: didn't look at the stacks fully yet, but I was pushing upstreams about fixes to their respective projects yesterday - some fixes have been filled in, some have still been worked on
[07:17] <sil2100> didrocks: will look at trunks to see how this worked out in the end
[07:18] <sil2100> didrocks: the webbrowser app should be fixed, as I verified the fix on jenkins by myself
[07:18] <sil2100> didrocks: also, I had a chat with Omer, and we'll be re-enabling mediumtests for all the apps once those issues get patched up
[07:18] <didrocks> sil2100: excellent! :-) once you have looked over jenkins, please keep me posted (on webapps for now to finish the bootstrapping)
[07:19] <didrocks> sil2100: any ETA for having everything fixed?
[07:19] <didrocks> sil2100: as this is our almost last blocker to have -next enabled :)
[07:20] <sil2100> didrocks: I was hoping yesterday evening ;p But let me check if there is progress, as I helped with finding those issues as much as I could - Omer also was poking people
[07:20] <didrocks> sil2100: ok, good :)
[07:24] <sil2100> didrocks: btw. how's the new test framework going?
[07:25] <didrocks> sil2100: jean-baptiste has a prototype, we'll work on it together today, just finishing the webapps stuff first
[07:28] <sil2100> didrocks: excellent ;)
[07:29] <sil2100> didrocks: regarding the apps AP's, it seems that fixes have been filled for all the failing projects besides notes-app
[07:29] <sil2100> didrocks: I'll poke nerochiaro again about that, and if anything I'll create a patch myself
[07:29] <sil2100> As I know the problem and a possible solution
[07:30] <didrocks> sil2100: great news! :)
[07:30] <didrocks> sil2100: even the media-apps?
[07:30] <sil2100> didrocks: yes, both camera-app and mediaplayer-app had some fix landed
[07:31] <sil2100> So I hope those would cover the failures we got
[07:31] <didrocks> sil2100: so to sum up, apart from QA that we don't know the status, SDK that Mirv is working on, and note-apps that you are looking, eveyrything's fine?
[07:33] <sil2100> didrocks: we should be fine, yes, I see the branches got merged so I'll re run the QA stack with rebuilding
[07:38] <didrocks> sil2100: good, just rebuild the components that changed please :)
[08:17] <tsdgeos> notepad-qml - Demos for Qt Components for Ubuntu
[08:17] <tsdgeos> bad naming of the package?
[08:17] <tsdgeos> anyone knows who do i ping? Ugo?
[08:22] <greyback> tsdgeos: yep I think Ugo.
[08:22] <greyback> what's wrong with the name?
[08:22] <tsdgeos> " Demos for Qt Components for Ubuntu" ?
[08:22] <tsdgeos> :D
[08:23] <tsdgeos> seems it's fixed already though
[08:23] <tsdgeos> at least can find that text in the repo
[08:23] <greyback> ah I see
[08:23] <tsdgeos> yep, somehow i probably have something old in my desktop
[08:23] <tsdgeos> phone is fine
[08:26] <mzanetti> Cimi: ping
[08:30] <mzanetti> MacSlow: hey. what was the issue with the failing test then?
[08:33] <MacSlow> mzanetti, waitForRendering() was the call needed
[08:34] <MacSlow> mzanetti, thanks to that I also was able to get rid of the wait(0)
[08:34] <mzanetti> MacSlow: ah right... yeah. that seems to be new since we use the proper mesa driver.
[08:34] <mzanetti> MacSlow: yeah. makes sense
[08:34] <MacSlow> mzanetti, test looks a much nicer now without the odd wait(0)
[08:35] <mzanetti> MacSlow: agreed
[08:35] <MacSlow> mzanetti, until you and/or Saviq looked over my branch again I'm back on frontend-backend work again helping Jussi
[08:36] <mzanetti> MacSlow: ok
[08:36] <MacSlow> basically checking was missing for things like "append", "replace" etc to work correctly
[08:37] <MacSlow> cool... with the working NotifyOSD backend-frontend running on my system, all regular notifications show up via the new renderer :)
[08:38] <MacSlow> Saviq, mzanetti: btw... what's the deal with GIcon support in Qt/QML? What's the best starting point to read up on it?
[08:39] <mzanetti> MacSlow: hmm... I don't know much about GIcon. But I would start looking if registering a QQmlImageProvider and converting the GIcons into a QPixmap somehow is an option
[08:39] <Saviq> mzanetti, already done
[08:39] <Saviq> MacSlow, you can use "image://gicon/" as source
[08:40] <MacSlow> Saviq, ah... interesting... thx
[08:40] <Saviq> MacSlow, or the Icon component from the SDK
[08:40] <Saviq> MacSlow, which has a "name" property
[08:40] <mzanetti> ah. does that work on GIcon?
[08:40] <mzanetti> the Icon {} item
[08:40] <MacSlow> Saviq, I'll opt for the SDK-component then if possible
[08:40] <mzanetti> MacSlow: definitely
[08:41] <Saviq> MacSlow, there's one caveat: you can't use Icon with a UbuntuShape
[08:41]  * mzanetti fixes his code in the ubuntu port of xbmcremote :D
[08:42] <Saviq> MacSlow, http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/qml-ubuntu-components0-icon.html btw
[08:42] <MacSlow> Saviq, hm...
[08:42] <Saviq> MacSlow, but the thing is so small anyway - http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/Icon.qml
[08:43] <Saviq> MacSlow, but anyway, we accept both GIcon names and full paths for the notifications, no?
[08:44] <Saviq> MacSlow, Icon only support GIcon names, so it's of not much use for us in that sense
[08:45] <Saviq> MacSlow, what we did before is just checked if the given source has / at the beginning
[08:45] <Saviq> MacSlow, and if not, prefix it with image://gicon/"
[08:47] <MacSlow> Saviq, yes that's what NotifyOSD currently does and what we want to keep with the new implementation
[08:48] <Saviq> MacSlow, so yeah, Icon is of no use to us
[08:49]  * greyback moving to office, bbiab
[09:04] <davidcalle> didrocks, hey :)
[09:05] <Cimi> mzanetti, pong
[09:05] <mzanetti> Cimi: hey. wanted to ask whats the state/plans for your branch regarding the Launcher using Panel
[09:06] <Cimi> mzanetti, I have other tasks pending, but I am happy to work on that
[09:06] <Cimi> mzanetti, unfortunately the Panel branch that fixes the Panel is not review yet
[09:07] <Cimi> mzanetti, we need this branch before the launcher work
[09:07] <mzanetti> Cimi: yeah... also dandrader changed the Launcher in a way it uses his dragging area
[09:07] <mzanetti> so I'm a bit lost on what I should wait or not
[09:08] <Cimi> mzanetti, it should just use the panel
[09:08] <Cimi> mzanetti, I guess we can remove dragging area from shell, what is it needed for?
[09:09] <mzanetti> Cimi: no, the new one Daniel is creating
[09:09] <mzanetti> Cimi: the one where it can find out if the drag should be used by the shell or by the running app
[09:11] <Cimi> mmm I need to see this code
[09:11] <Cimi> the goal was to use the SDK for those elements
[09:11] <Cimi> Saviq, are you aware of daniel's work?
[09:12] <Saviq> Cimi, yes I am, it will end up in the SDK ultimately, too
[09:12] <Cimi> Saviq, what's its purpose?
[09:13] <Saviq> Cimi, it's an directional drag detector
[09:13] <Cimi> Saviq, isn't it colliding with the request of writing the Launcher using the Panel?
[09:13] <Cimi> Panel or this smart dragging area?
[09:13] <Saviq> Cimi, Panel will ultimately use this dragging area
[09:14] <Cimi> I see
[09:14] <Cimi> Saviq, but I was writing the Launcher using the Panel
[09:14] <Saviq> Cimi, that's fine
[09:14] <Cimi> Saviq, now he is writing the Launcher using the dragging area
[09:14] <Saviq> Cimi, we won't be able to do everything in one go
[09:14] <Cimi> which one shall we merge?
[09:14] <Saviq> Cimi, even if we merge his for now
[09:15] <Saviq> Cimi, once Panel uses Daniel's draggingArea
[09:15] <Saviq> Cimi, we'll merge yours
[09:15] <Cimi> Saviq, I would say it will be much better if he was simply working into integrating the new dragging area in SDK
[09:15] <MacSlow> Does Qt have an equivalent to gtk+'s gtk_icon_theme_append_search_path()?
[09:16] <Saviq> MacSlow, I don't think it does
[09:16] <Cimi> Saviq, Panel useg for launcher removes all references to dragging area
[09:16] <Cimi> Saviq, it's work wasted
[09:16] <Cimi> *usage
[09:16] <Saviq> Cimi, no it's not, because once Panel uses the new DraggingArea (which can't be integrated into SDK yet)
[09:17] <Saviq> Cimi, we'll just switch to what you did for the Launcher with panel
[09:17] <Cimi> Saviq, which is basically removing bunch of code including dragging area
[09:17] <Cimi> Saviq, which will mean removing his branch
[09:17] <MacSlow> Saviq, hm... then we either have to use that call in the new NotifyOSD or relocate the special icons we have for NotifyOSD (see https://wiki.ubuntu.com/NotifyOSD#Icon)
[09:18] <Saviq> Cimi, yes, when it's integrated into the SDK, it will mean removing his branch
[09:18] <Saviq> Cimi, but it will not happen for some time still
[09:18] <MacSlow> Saviq, the special icons currently live in /usr/share/notify-osd/icons and that path gets added to the icon-theme search-path in NotifyOSD
[09:19] <Cimi> Saviq, mumble? I am not understanding :)
[09:19] <Saviq> Cimi, and until then we can use what you did to integrate with the current SDK Panel
[09:20] <MacSlow> Saviq, btw... I've already added the support for "image://gicon" in the backend-frontend merge and it works nicely... just not yet for the special notification icon-set
[09:20] <MacSlow> Saviq, we can discuss that in the after the stand-up today perhaps
[09:28] <Cimi> mzanetti, had a chat with Saviq … essentially my work on integrating the Panel with the Launcher is on hold until daniel's dragging area will be proposed and merged into the SDK
[09:28] <Cimi> mzanetti, his dragging area is supposed to be much better than the current state of the Panel, so it does worth the wait
[09:29] <Cimi> mzanetti, we don't think the new dragging area will be integrated in the SDK before 2-3 weeks
[09:29] <mzanetti> Cimi: ok. thanks
[09:29] <Cimi> mzanetti, so I'll probably propose a branch in 3-4 weeks time
[09:29] <Saviq> MacSlow, it would probably be best to extend the GIconProvider to support adding custom paths
[09:29] <Saviq> http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/plugin/giconprovider.cpp
[09:30] <Saviq> MacSlow, can you talk to the SDK guys on how to go about that?
[09:30] <MacSlow> Saviq, I can write a patch for it and mr it
[09:30] <MacSlow> Saviq, should not be too much work.
[09:31] <MacSlow> Saviq, who would be the first contact-person for discussion on the SDK-team? Tim?
[09:32] <Saviq> MacSlow, sure, you could also talk to renato as he wrote it
[09:32] <MacSlow> Saviq, ok
[09:50] <sil2100> didrocks: the autopilot tests from after the fixes are in, there are less failures but still not enough ;/
[09:50] <sil2100> didrocks: 13 failures on every platform
[09:50] <sil2100> didrocks: I mean, per-platform
[09:51] <sil2100> I see some import failures, maybe some missing dependencies this means - but that's just 3 of the 13 failures
[09:52] <sil2100> I *might* be able to fix some of those then
[09:52] <didrocks> sil2100: keep poking! :)
[09:52] <sil2100> But Thomi and the other devs would be sweet to have right now ;p
[09:52] <didrocks> davidcalle: hey, in a hangout, will be available afterwards :)
[09:52] <didrocks> sil2100: right ;)
[09:52] <davidcalle> didrocks, ok
[10:29] <sil2100> didrocks: https://code.launchpad.net/~sil2100/autopilot/autopilot_test_fixes/+merge/163886 <- some fixes related to the autopilot failures
[10:29] <sil2100> fginther: ^
[10:29] <sil2100> Not all I guess, but that's always something
[10:29] <didrocks> sweet, let's wait for some QA people for reviewing
[10:29] <sil2100> didrocks: ah, wait, I'll also add a changelog entry for those
[10:30] <didrocks> sil2100: as you wish, otherwise, it will take the commit log :)
[10:30] <smspillaz> fyi people - https://code.launchpad.net/~compiz-team/compiz/compiz.fix_1170013/+merge/161183 <- should be easy to make AP autopkgtests out of that one
[10:36] <dednick> mardy: ping
[10:36] <mardy> dednick: pong :-)
[10:37] <mardy> dednick: I'm trying the QMenuModel example file (render-menumodel.qml), but I always get an empty view
[10:38] <mardy> dednick: I changed the busName and path to "com.canonical.indicator.messages" and /com/canonical/indicator/messages/menu
[10:39] <mardy> dednick: and I added a few qDebugs here and there. I see that the model is connected, and that QMenuModel::onItemsChanged() is called with "added" > 0
[10:39] <mardy> dednick: but the view still stays empty
[10:39] <nic-doffay> mzanetti, got a moment?
[10:39] <mardy> dednick: any idea of what's wrong? Does it work for you?
[10:40] <mardy> dednick: (and, are you the right person to be bothered about this? :-) )
[10:40] <dednick> mardy: i havent actually used it myself. :)
[10:42] <mardy> dednick: OK, I'll ask Renato
[10:42] <dednick> mardy: yeah, i was just going to suggest that
[10:44] <mzanetti> nic-doffay: hey
[10:44] <mzanetti> nic-doffay: yes
[10:45] <nic-doffay> mzanetti, regarding the infographics QML tests. Would the best approach be to create a standalone Infographics and create whatever tests need to be done for it?
[10:45] <nic-doffay> At the moment it's created by the greeter.
[10:47] <mzanetti> nic-doffay: I don't really understand the question
[10:49] <mzanetti> nic-doffay: Isn't the Infographic already separated in Infographics.qml?
[10:49] <nic-doffay> mzanetti, it is.
[10:49] <mzanetti> nic-doffay: what exactly is the problem then?
[10:50] <nic-doffay> mzanetti, basically should the tests be a part of the greeter or for the component specifically.
[10:50] <mzanetti> nic-doffay: ah. for the component specifically
[10:50] <nic-doffay> mzanetti, right on, cheers!
[11:10] <nic-doffay> mzanetti, just reading through your comments, thanks for the thorough review of the branch.
[11:11] <mardy> cyphermox_: hi :-)
[11:11] <mardy> cyphermox_: see the backlog, about 20 lines ago :-)
[11:11] <mzanetti> nic-doffay: :)
[11:12] <cyphermox_> urgh
[11:13] <cyphermox_> mardy: not sure I can help you with how QMenuModel works quite yet ;)
[11:14] <mardy> cyphermox_: np, I'll wait for Renato then :-)
[11:22] <didrocks> davidcalle: available now :)
[11:22] <mzanetti> pete-woods: hey
[11:22] <pete-woods> mzanetti: hi!
[11:22] <mzanetti> pete-woods: still don't really understand the reason for the QVariantListModel
[11:23] <pete-woods> perhaps it's a result of my lack of Qt understanding
[11:23] <pete-woods> basically I want my API to provide two QAbstractItemModels
[11:23] <davidcalle> didrocks, super small mp https://code.launchpad.net/~davidc3/cupstream2distro-config/100scopes-remove-imdb/+merge/163864
[11:24] <pete-woods> and I wanted the quickest implementation I could do
[11:24] <didrocks> davidcalle: ok, doing it :)
[11:24] <pete-woods> so I based it on QStringListModel
[11:24] <didrocks> davidcalle: it's removed from the scope json file?
[11:24] <mzanetti> pete-woods: you want the backend API providing 2 models and aggregate them in the frontend into 1 model?
[11:24] <davidcalle> didrocks, hmm. Of course not^^ Will mp it in a moment, need to go :)
[11:25] <nic-doffay> pete-woods, are you going to handle this: https://pastebin.canonical.com/91011/
[11:25] <pete-woods> I just want to provide two lists
[11:25] <pete-woods> that can provide change notification - i.e. element changed, row inserted, etc
[11:25] <pete-woods> nic-doffay: I've already done that one :)
[11:26] <pete-woods> nic-doffay: I
[11:26] <davidcalle> didrocks, by the way, not sure you know about that website: http://framli.eu/scopes_browser/index.html?scope=unity-scope-yahoostock
[11:26] <pete-woods> nic-doffay: I've basically left you the animation and more QML-y ones
[11:26] <nic-doffay> pete-woods, ok wicked
[11:27] <didrocks> davidcalle: oh, nice, the name rings a bell to me, but I didn't remember what it was :)
[11:28] <davidcalle> didrocks, don't trust all the data in it, though, still working on the parser :)
[11:28] <pete-woods> mzanetti: I thought what I was doing was pretty simple? Qt should really have a QVariantListModel built in, so that you don't have to extend QAbstractItemList all the time :)
[11:28] <didrocks> heh ;)
[11:32] <nic-doffay> mzanetti, not to worry, I was holding off on the tests in case I had butchered a lot of the QML and needed to redo it ;P
[11:33] <nic-doffay> But it looks like that wasn't the case.
[11:40] <MCR_> JohnLea, ping !
[11:40] <MCR_> JohnLea, your document says: Ctrl + Super + Cursor Left or Right	Semi-maximises current window
[11:41] <MCR_> which is actually something else than what Grid does as Grid not only semi-maximizes, but also moves the window
[11:41] <MCR_> we can of course have shortcuts to just semi-maximize as well
[11:42] <MCR_> regarding the other problem:
[11:42] <MCR_> it would be (easily) possible to have 2 different shortcuts doing the same thing, so I can implement that for Grid without any problems...
[11:55] <JohnLea> MCR_; hyia!
[11:55] <JohnLea> MCR_; yes, ideally it would be good to do both.  The "Ctrl + Super + Cursor Left or Right" is the more important of the 2 though
[11:56] <JohnLea> MCR_; scroll down to the end of that doc ;-)
[11:56] <JohnLea> MCR_; if this is something you could take a look at, could you revert the status of that bug back to triaged?
[11:56] <JohnLea> MCR_; Thanks ;-)
[11:57] <MCR_> JohnLea, yep
[11:58] <Saviq> mzanetti, pete-woods re: mock vs. real implementation, we already have a mechanism in place that will "favour" system-wide installations if available and fall back to those from tests/mocks - I missed that in the lightdm review, but we should do the same - just put the LightDM plugin under tests/mocks now
[11:58] <Saviq> and if there is a system-wide plugin installed, it will be used
[11:58] <pete-woods> Saviq: the LightDM mock is already there before this branch
[11:59] <Saviq> pete-woods, yeah, I know
[11:59] <pete-woods> shouldn't it be moved in a separate MR?
[11:59] <Saviq> pete-woods, that's what I meant by "I missed that in the lightdm review"
[11:59] <pete-woods> oh, okay :)
[11:59] <mzanetti> Saviq: we are fine with having Digia LGPL code included, are we?
[11:59] <Saviq> pete-woods, sure, we could have a separate MR for that
[11:59] <MCR_> JohnLea, consider this bug fixed
[12:00] <JohnLea> MCR_; awesome!
[12:00] <Saviq> mzanetti, depends where, I'd say
[12:00] <mzanetti> Saviq: real code
[12:00] <mzanetti> Saviq: not just tests as the other from albert
[12:00] <Saviq> mzanetti, well, yeah should be fine
[12:00] <mzanetti> Saviq: talking about the QVariantListModel
[12:00] <Saviq> mzanetti, yeah I gathered
[12:06] <MCR_> JohnLea, I cannot set to "Triaged" -> I have no rights for that...
[12:06] <JohnLea> MCR_; no worries, I have already done that ;-)
[12:07] <MCR_> JohnLea, I've updated the report with a HOWTO
[12:07] <Saviq> mzanetti, huh, is it normal that jenkins/pbuilder works in non-UTF-8 locale (LANG=C, probably?)
[12:07] <Saviq> mzanetti, https://jenkins.qa.ubuntu.com/job/unity-api-raring-i386-ci/5/console
[12:08] <mzanetti> Saviq: don't know. I don't think that has changed lately tho
[12:08] <Saviq> mzanetti, no it probably didn't
[12:09] <Saviq> mzanetti, was just surprised (and it only showed up because my name is non-ascii ;))
[12:09] <mzanetti> I have seen this exact error in autopilot _because_ we were using UTF
[12:09] <mzanetti> Saviq: ^
[12:09] <mzanetti> Saviq: exporting LANG=C before running autopilot tests works around it
[12:10] <Saviq> mzanetti, it probably wasn't this exact error ;)
[12:10] <Saviq> mzanetti, otherwise setting LANG=C wouldn't help :D
[12:11] <Saviq> mzanetti, as setting LANG=C here actually exposes this issue (it's fine in my default locale)
[12:11] <mzanetti> Saviq: https://bugs.launchpad.net/autopilot/+bug/1154107
[12:11] <ubot5`> Launchpad bug 1154107 in Autopilot "autopilot crashes on failed test" [Critical,Incomplete]
[12:15] <pete-woods> Saviq: LANG=C is what it's been set to for a while I think - I had this problem when adding tests for some gettext related stuff in HUD
[12:16] <Saviq> mzanetti, pete-woods well, the LANG=C is for sure not fixing anything - just hacking around an autopilot bug
[12:17] <pete-woods> fair enough :)
[12:17] <Saviq> autopilot | testtools
[12:17] <mzanetti> yep
[12:17] <Saviq> but OTOH having LANG=C in there makes sure that we're explicit about some things
[12:18] <Saviq> instead of assuming everything is UTF-8, so it has some advantages
[12:44] <sil2100> fginther: ping
[13:03] <GuidoPallemans> how can I import unity next in qt creator? http://unity.ubuntu.com/getinvolved/development/unitynext/ lp:unity/phablet
[13:03] <vesar> Mirv, or anyone else, I'm trying to run my shell version on device with run_on_device script but as a result I'm getting: "Cannot mix incompatible Qt library (version 0x50001) with this library (version 0x50002)
[13:03] <vesar> " Any idea?
[13:03] <GuidoPallemans> vesar can you start qt creator?
[13:03] <vesar> Mirv, I saw a bug report relating on this: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1178147
[13:03] <ubot5`> Launchpad bug 1178147 in qtdeclarative-opensource-src (Ubuntu) "qmlscene not pulling all required dependencies" [Undecided,Confirmed]
[13:04] <vesar> GuidoPallemans, yes
[13:04] <vesar> Qt Creator works just fine
[13:04] <GuidoPallemans> hmm, I had the same error earlier when launching qt creator
[13:04] <GuidoPallemans> fixed it by just reinstalling everything qt*
[13:04] <GuidoPallemans> but you may not want to do that...
[13:06] <vesar> GuidoPallemans, yeah sounds a bit excessive. I would expect that someone would have had the same issue when trying to run on device,
[13:06] <vesar> I guess the reason is somehow related to different Qt versions btw my machine and device
[13:07] <GuidoPallemans> hmm
[13:09] <mzanetti> mterry: https://code.launchpad.net/~mzanetti/unity/phablet-tease-launcher/+merge/163906
[13:09] <GuidoPallemans> how can I import unity next in qt creator? http://unity.ubuntu.com/getinvolved/development/unitynext/
[13:15] <Saviq> GuidoPallemans, just open the CMakeLists.txt file and the .qmlproject file
[13:15] <Saviq> GuidoPallemans, unfortunately QtCreator can't have a CMake project that also has QML files currently
[13:16] <Saviq> vesar, apt-get upgrade
[13:17] <Saviq> vesar, Qt on the image uses 5.0.1 still, but when you install new packages they are already 5.0.2
[13:19] <kenvandine> didrocks, in test_parameters, what is "packages" for?
[13:19] <kenvandine> is that the packages that the test provides coverage for?
[13:19] <kenvandine> essentially what it tests integration for
[13:20] <didrocks> kenvandine: yeah, it's the list of all packages we need to install from the ppa to get the new set of packages tested
[13:20] <kenvandine> ok
[13:20] <didrocks> kenvandine: normally it's only the binaries from the stack that we want to install
[13:20] <kenvandine> thought so
[13:20] <didrocks> (all the rest being in the iso)
[13:20] <didrocks> but in this case, we need qt and so on, as it's not in the iso :)
[13:20] <kenvandine> i got webcred autopilot tests now :)
[13:20] <kenvandine> about to submit the MP
[13:21] <didrocks> \o/
[13:21] <kenvandine> although 1 test is failing in jenkins... that isn't failing for me
[13:22]  * didrocks publishes webapps
[13:22] <didrocks> robru: FYI ^
[13:25] <Mirv> vesar: try to run apt-get dist-upgrade?
[13:26] <vesar> Mirv, Saviq : both give me just 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[13:26] <Mirv> vesar: on the device that is. but I don't have a good insight on how the ubuntu plugin works when you order it to run on device
[13:27] <vesar> Mirv, oh ok will try that.
[13:27] <Saviq> vesar, apt-cache policy libqt5declarative5 ?
[13:27] <Saviq> vesar, a potential "apt-get update" might be needed on the device, but you should get 5.0.2 for sure
[13:30] <vesar> Saviq, Mirv: ok running apt-get update + upgrade helped. Thanks!
[13:37] <greyback> Saviq: nic-doffay: standup?
[13:37] <Saviq> greyback, good idea
[13:37] <greyback> Cimi: ^^
[13:37] <Mirv> vesar: ok, cool
[13:39] <nic-doffay> greyback, sorry in another hangout
[13:39] <nic-doffay> totally forgot
[13:46] <greyback> MacSlow: thanks for fixing my summary, it's hard to listen & type properly ;)
[13:46] <MacSlow> greyback, sure np yw... it's always hard to listen (and understand) and write everything down
[13:47] <greyback> mterry: ok, what do you need? If you update your phone, it should be possible to get Mir running now. You just need to do a few things
[13:47] <Cimi> greyback, I'm having lunch… thought we were skipping stand ups this week with the uds
[13:47] <greyback> Cimi: first I heard of that :) No worries anyway
[13:48] <Cimi> greyback, we did skip last vUDS
[13:48] <mterry> greyback, ooh, OK.  Can you describe them to me?  I could try to test the lightdm setup that way
[13:49] <Saviq> mzanetti, can you vote on https://code.launchpad.net/~macslow/unity/phablet-notification-renderer/+merge/155512 please?
[13:49] <mzanetti> Saviq: sure
[13:49] <greyback> mterry: sure. Where do you want to test, on your PC, or on a phone/tablet?
[13:50] <mterry> greyback, I guess on my nexus7
[13:51] <greyback> mterry: ok cool, that's supported
[13:51] <mzanetti> Saviq: done
[13:51] <greyback> mterry: first, update it, as recent changes landed in mir that you need
[13:51] <kgunn> mterry: half watching this...what are you going to run on nexus7?
[13:51] <kgunn> if mir...you'll need a special package from kdub
[13:51] <mterry> kgunn, mir, then testing lightdm workflow
[13:52] <greyback> mterry: kgunn: oh that's right, I forgot that
[13:57] <tedg> bregma, Are you on saucy?  I'm getting a panel-service crash everytime I close a window.
[13:58] <bregma> tedg, I do have a saucy test machine, would you like me to verify?
[13:58] <tedg> bregma, Uhm, sure.  It'd help to know if I'm crazy or not :-)
[13:59] <tedg> Trying to see if I have any locally installed packages that'd matter here.
[13:59] <bregma> I don't get that right now, let me upgrade to the latest packages
[14:01]  * bregma hums a random tune while his computers fight for internet bandwidth
[14:03]  * tedg has his money on the little one
[14:08] <Saviq> dandrader, btw, some interestning read Mr. Voß pointed me at today: http://yangl.org/pdf/gstudio.pdf
[14:08] <dandrader> hmm
[14:10] <nic-doffay> mzanetti, in what cases should verify() and tryCompare() used in the QML tests?
[14:11] <mzanetti> nic-doffay: use compare() and tryCompare() whenever possible
[14:11] <mzanetti> nic-doffay: there are some cases where they won't work and you have to use verify()
[14:13] <MacSlow> When changing/updating an item in a model, does the delegate displaying that item get notified automatically ? Or is there something else, which needs to be triggerd?
[14:13] <nic-doffay> Ok  cheers. What's the difference between tryCompare and compare though mzanetti ?
[14:14] <mzanetti> nic-doffay: compare() does it NOW while tryCompare() waits a certain amount of time for the condition to become true
[14:15] <bregma> ah, holy crud, my trackpad has gone wild after I upgraded Saucy
[14:17] <dandrader> Saviq, did you read it?
[14:17] <Saviq> dandrader, not yet
[14:17] <Saviq> dandrader, just skimmed
[14:23] <thomi> didrocks: sil2100, any luck with the autopilot run?
[14:23] <didrocks> thomi: there are still some issues. sil2100 fixed more, but I guess there are some failures
[14:23] <thomi> sorry I didn't stick around any longer yesterday, I was about ready to fall asleep standing up
[14:23] <thomi> didrocks: got a link? I can fix them up today
[14:24] <didrocks> thomi: no worry, it was already way too late :)
[14:24]  * didrocks looks for a link
[14:24] <didrocks> thomi: http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/385/
[14:25]  * thomi looks
[14:25] <didrocks> thomi: sil2100 has a MP to fix some I guess, but not all
[14:25] <thomi> ahh ok
[14:25] <thomi> will look there first then
[14:25] <didrocks> https://code.launchpad.net/~sil2100/autopilot/autopilot_test_fixes/+merge/163886
[14:25] <didrocks> thomi: ^
[14:25] <thomi> cheers
[14:27] <bregma> tedg, yes, I get the crash in unity-panel-service
[14:27] <tedg> \o/
[14:27] <tedg> Oh, wait.
[14:28]  * bregma speculates on perhaps there are other explanations for tedg's madness
[14:29] <bregma> it seems apport experiences problems reporting bugs and wants to report a problem about reporting problems
[14:29] <tedg> bregma, Do you have libunity-gtk3-parser0 installed?
[14:33] <bregma> tedg, nope, according to dpkg...  this is a clean 13.04 install upgraded to current Saucy with no added extras
[14:33] <thomi> sil2100: can you ping me when you get a moment please?
[14:34] <tedg> bregma, Okay, that kills one theory.
[14:34] <bregma> I also see a crash in unity-greeter related to libido3
[14:35] <seb128> bregma, tedg: unity-panel-service segfaulting is a known issue/being fixed
[14:35] <seb128> I didn't follow the start of the discussion
[14:35] <seb128> just pointing that
[14:35] <tedg> Oh, cool!
[14:36] <tedg> seb128, Also, do you know when unity-gtk-parser is going into saucy?
[14:36] <bregma> unity-panel-service has many many outstanding segfault bugs, this crash is new as of the last week or so and is consistently reproducable
[14:36] <seb128> tedg, http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.13.10/revision/442
[14:37] <seb128> bregma, it should be new since yesterday (side effect of the new glib exposing a libdbusmenu bug)
[14:37] <seb128> bregma, ^ that's the fix
[14:37] <seb128> it happens when you close a win
[14:38] <seb128> tedg, no, cyphermox/sil2100 might know, I think the autopilot issues got resolved, not sure what else is missing
[14:39] <bregma> excellent, not my team's fault (this time)
[14:39] <cyphermox> tedg: unity-gtk-module was ready afaik, I enabled it last week, perhaps it's just failing tests atm
[14:39] <cyphermox> sil2100: ?
[14:39] <seb128> cyphermox, do you plan to land libdbusmenu from trunk to saucy now that the fix is in for that?
[14:42] <cyphermox> I do, just waiting for autopilot to finish so I can override the results.
[14:43] <seb128> great
[14:56]  * tsdgeos hits greyback and mzanetti with a trout
[14:56] <mzanetti> tsdgeos: huh?
[14:56] <tsdgeos> now you smell fishy :D
[14:57] <tsdgeos> tst_ListViewWithPageHeader.qml is full of broken tryCompare
[14:57] <mzanetti> is it?
[14:57] <greyback> why?
[14:57] <tsdgeos> tryCompare(listView.view.contentY, -1);
[14:57] <tsdgeos> bad
[14:57] <mzanetti> hehe
[14:57] <tsdgeos> tryCompare(listView.view, "contentY", -1);
[14:57] <tsdgeos> good
[14:57] <mzanetti> it sucks quite hard that this evaluates to true
[14:57] <tsdgeos> yep
[14:57] <tsdgeos> it does
[14:57] <greyback> ah that's my bad
[14:57] <robru> didrocks: how'd the webapps publishing go? everything in saucy yet?
[14:57] <mzanetti> and mine :/ did the review
[14:58] <tsdgeos> wonder if it would be patcheable to fail
[14:58]  * tsdgeos is fixing
[14:58] <mzanetti> yeah, that'd be awesome
[14:58] <greyback> it could check to make sure 3 args were passed
[14:59] <didrocks> robru: look at saucy-changes :)
[14:59] <didrocks> robru: however, some components are yellow as you can see on jenkins
[14:59] <didrocks> robru: so they need to be reconciled I guess
[14:59] <mterry> greyback, I got distracted, but am coming back.  So what's this package from kdub?
[15:00] <greyback> mterry: nexus7 not supported in mir trunk. Need kdub to supply you with a patch, so you'd best ask him (I don't have it, sorry)
[15:01] <mterry> k
[15:08] <robru> didrocks: I don't know how to fix this... yellow means there's a newer version in the PPA? how did that happen?
[15:08] <didrocks> robru: hum, let me look
[15:08] <didrocks> robru: which ppa? it's checking the dest
[15:09] <didrocks> robru: A version (2.2ubuntu1) is available at the destination for that component but is not in trunk which is still at 2.2ubuntu1daily13.05.14.1ubuntu.unity.next-0ubuntu1.
[15:10] <didrocks> let me look distro
[15:10] <robru> didrocks: that's a weird version number
[15:10] <didrocks> robru: see saucy?
[15:10] <didrocks> robru: 2.2ubuntu1 release (universe) 2013-04-25
[15:11] <kenvandine> didrocks, i have a MP for the friends scope, for libunity7 compatibility, is that landing today?
[15:11] <didrocks> kenvandine: not sure, sil2100?
[15:11] <robru> didrocks: I don't know how that release exists or what to do about it; it's not in the changelog or anything
[15:11] <kenvandine> i don't want to approve it and get broken builds :)
[15:11] <didrocks> robru: I don't see 2.2ubuntu1 in debian/changelog
[15:12] <didrocks> robru: so someone uploaded that to distro and it needs to be backported to trunk :)
[15:12] <robru> didrocks: well is there a debdiff of what's in the distro that isn't in trunk? I expect it's trivial
[15:12] <didrocks> robru: it's a security to ensure we don't overwrite stuff that were manually upload to distro
[15:13] <didrocks> robru: I would say download the source package and create the debdigg
[15:13] <didrocks> debdiff
[15:13] <didrocks> or you can check what was uploaded to 2.2ubuntu1
[15:13] <didrocks> robru: http://launchpadlibrarian.net/125703135/unity-webapps-facebookapps_2.2_2.2ubuntu1.diff.gz
[15:13] <didrocks> robru: I think it's part of the manual SRU I had to do some months ago
[15:14] <didrocks> robru: check the other, but I guess it's the same
[15:14] <robru> didrocks: so let's say I get the debdiff and discover that it's a trivial change and they just forgot to update the changelog or something. How would I go about forcing this through jenkins? just add the version number to debian/changelog?
[15:14] <didrocks> robru: right, just add it to debian/changelog (prefer ordering it properly)
[15:14] <didrocks> if the change is really in
[15:14] <didrocks> (I think it is, but better to check)
[15:15] <robru> didrocks: ooooh, it actually isn't. tricksy!
[15:20] <robru> didrocks: https://code.launchpad.net/~robru/unity-webapps-facebookapps/backport-sru-to-trunk/+merge/163968
[15:21] <didrocks> robru: do you mind fixing that with ken? (same for the other components?). I'm working on the utah replacement ;)
[15:21] <didrocks> robru: btw, see that this check is useful? we would have overwritten a security fix otherwise ;)
[15:21] <didrocks> (it looks good to me FYI)
[15:22] <robru> kenvandine: ^^
[15:22] <robru> didrocks: yes, it's good we didn't regress a security fix, but i don't know how comfortable I am that our security team is pushing fixes directly to distro without getting them landed in trunk first...
[15:22] <kenvandine> oh joy... these are the reasons we need daily releases :)
[15:22] <robru> (or at all)
[15:23] <kenvandine> this prevents us from reverting those fixes
[15:23] <kenvandine> so all good
[15:23] <tsdgeos> greyback: yep, that seems ot work, i'll submit a MR for 5.1
[15:23] <kenvandine> we'll have to catch these and make sure the fixes land
[15:24] <robru> kenvandine: didrocks: oh, it seems amazoncloudreader has the security fix in trunk already, but facebookapps didn't
[15:24] <greyback> tsdgeos: kewl. You could also check the second argument is a string, but perhaps that's too much
[15:24] <tsdgeos> greyback: well, i guess that'll fail if not a string, no
[15:24] <tsdgeos> ?
[15:24] <greyback> tsdgeos: probably yeah
[15:25] <tsdgeos> yep it does
[15:25] <tsdgeos> FAIL!  : qmltestrunner::ListViewWithPageHeader::test_upSwipeCausingBounceKeepsHeaderHidden() Uncaught exception: atYEnd is not defined
[15:25] <tsdgeos> when using
[15:25] <tsdgeos>             tryCompare(listView.view, atYEnd, true);
[15:26] <tsdgeos> greyback: can you handle https://code.launchpad.net/~aacid/unity/fix_tryCompare/+merge/163970  ?
[15:26] <greyback> tsdgeos: ok
[15:28] <robru> kenvandine: https://code.launchpad.net/~robru/unity-webapps-amazoncloudreader/fix-changelog/+merge/163972
[15:31] <tsdgeos> greyback: mzanetti: https://codereview.qt-project.org/#change,56222
[15:32] <tsdgeos> i actually suggest you manually edit /usr/lib/x86_64-linux-gnu/qt5/qml/QtTest/TestCase.qml and add those two lines
[15:32] <tsdgeos> Saviq: ↑↑↑
[15:32] <greyback> tsdgeos: agreed
[15:32] <mzanetti> tsdgeos: better :D
[15:33] <mzanetti> tsdgeos: will that cause all our tests to fail? :D
[15:33] <tsdgeos> mzanetti: i already fixed the other one that failed
[15:33] <tsdgeos> tst_PageHeader
[15:33] <Saviq> tsdgeos, could you add msg to it? ;d
[15:34] <tsdgeos> Saviq: ?
[15:34] <Saviq> tsdgeos, there's no way to set a failure message with tryCompare
[15:35] <tsdgeos> ah
[15:35] <mzanetti> damn javascript... undefined [15:35] <mzanetti> even though it sometimes is only undefined == undefined
[15:36] <tsdgeos> Saviq: could do that, but would mean having to pass the timeout all the time
[15:36] <Saviq> tsdgeos, or undefined
[15:36] <Saviq> for default
[15:36] <tsdgeos> Saviq: sure, i mean the parameter
[15:36] <Saviq> tsdgeos, yeah, I know
[15:36] <Saviq> tsdgeos, still, better than nothing...
[15:38] <tsdgeos> Saviq: sure, can do, should be 5 min, but let me have this one merged first since the other touches the same line and it'll conlficted and don't want to go having to update requests given how hard is sometimes to get hold of people :D
[15:38] <Saviq> tsdgeos, sure, I was just complaining ;)
[15:40] <robru> kenvandine: last one: https://code.launchpad.net/~robru/unity-webapps-twitter/fix-changelog-manifest/+merge/163980
[15:41] <robru> kenvandine: if we get these merged, webapps can finally land ;-)
[15:44] <kenvandine> robru, you need commit messages on the first 2
[15:44] <robru> bah
[15:49] <robru> kenvandine: ok, can you rerun the stack for me once these land?
[15:49] <kenvandine> sure
[15:50] <robru> kenvandine: thanks
[16:23] <nic-doffay> Saviq, any idea what I need for the Unity.Test module?
[16:24] <nic-doffay> I already have qtdeclarative5-test-plugin
[16:24] <Saviq> nic-doffay, it's in tests/utils/modules
[16:24] <nic-doffay> Saviq, cool cheers.
[16:24] <Saviq> nic-doffay, if you try to run with qmlscene just go `qmlscene -I builddir/tests/utils/modules ...`
[16:25] <Saviq> nic-doffay, if you add a test in tests/qmltests via the CMakeLists.txt - that should Just Work™
[16:25] <Saviq> thanks to the qmltest_DEFAULT_IMPORT_PATHS setting
[16:26] <nic-doffay> Saviq, I've been trying to run qmltestrunner -input <filehere>
[16:26] <Saviq> nic-doffay, in that case
[16:26] <Saviq> nic-doffay, you need -import builddir/tests/utils/modules/
[16:26] <nic-doffay> Saviq, cool thanks!
[16:33] <nic-doffay> Saviq, still not getting any joy. This is what I'm doing from test/qmltests/Greeter - qmltestrunner -input tst_Infographics.qml -import ../../utils/modules/
[16:33] <Saviq> nic-doffay, you need to go to builddir
[16:34] <Saviq> nic-doffay, also, you can "make testInfographics" in the builddir
[16:34] <Saviq> assuming Infographics is added as a test in tests/qmltests/CMakeLists.txt
[16:35] <Saviq> nic-doffay, I mean you can't import from the source tree, because Unity.Test is a module that needs to be compiled
[16:35] <Saviq> nic-doffay, so you need to import builddir/test/utils/modules
[16:38] <nic-doffay> Saviq, I see.
[17:23] <mterry> Saviq, mzanetti: After using ./run_on_device, it seems that my device doesn't boot normally.  Do I have to re-flash it to get it back to a good state?
[17:24] <Saviq> mterry, you mean you get a black screen?
[17:24] <mterry> Saviq, yeah
[17:24] <mterry> It runs fine when I do the first run_on_device
[17:25] <Saviq> mterry, your /etc/tablet-services got broken probably
[17:25] <mterry> I'm just talking about, say, the next day when I boot the device up
[17:25] <Saviq> mterry, http://pastebin.ubuntu.com/5668288/ here's the right content
[17:25] <mterry> Saviq, will try
[17:25] <Saviq> mterry, it happens when you use run_on_device
[17:25] <Saviq> mterry, and you disconnect the device without killing the shell first
[17:25] <Saviq> mterry, unfortunately that also happens when you lock the Nexus 10
[17:25] <Saviq> mterry, as it disconnects adb :/
[17:32] <mterry> Saviq, yup, thanks.  The qml-phone-shell line is missing and with it back, everything works
[18:12] <kgunn> mterry: Saviq so is this this http://pastebin.ubuntu.com/5668288/ something you have to do from the android shell ?
[18:13] <Saviq> kgunn, it's just the contents of /etc/{tablet,phone}-services
[18:13] <mterry> kgunn, yeah
[18:13] <Saviq> kgunn, which we need to mangle when doing ./run_on_device
[18:13] <mterry> kgunn, from either the ubuntu_chroot shell bit or modifying /data/ubuntu/etc/tablet-services from the android shell
[18:14] <Saviq> or ssh into the device and do it straight in ubuntu
[18:14] <kgunn> Saviq: mterry thanks....just thinking instructions on wiki
[18:14] <Saviq> kgunn, yeah, might make sense to add there
[18:15] <Saviq> and/or we should maybe try and make sure that we don't break that file...
[18:15] <kgunn> Saviq: made a note of it... :)
[19:12]  * greyback eod
[19:52] <sil2100> thomi: ping!
[19:52] <thomi> sil2100: hey, I commented on your autopilot MP
[19:53] <sil2100> thomi: I saw, thanks! I replied ;)
[19:53] <thomi> oh ... I guess I'll go read it
[20:00] <thomi> sil2100: ahhh, of coure. hmmmm
[20:01] <thomi> ideally we'd not run that code unless -r was specified. but OK, I'm happy with the MP
[20:03] <sil2100> thomi: me and fginther were anyway wondering whether to include the additional python-evdev dependency for python-autopilot-tests or not
[20:03] <sil2100> thomi: or maybe we should just skip those tests
[20:03] <bschaefer> sil2100, hey, i've got a question for you when you get moment :)
[20:03] <bschaefer> get a*
[20:06] <sil2100> bschaefer: hi! What's up? ;)
[20:06] <bschaefer> sil2100, hey! So whats the policy on SRUs that break ABI?
[20:07] <bschaefer> (it would be in Nux, and I would also be SRUing a fix to unity as wel...)
[20:09] <sil2100> Uuuuuuuuuu
[20:09] <sil2100> uuuuu
[20:09] <sil2100> We no like!
[20:10] <bschaefer> i know :(, the XIM fix in 13.04 is wanted in 12.04 annnd it breaks the ABI, but getting around that could be dangerous
[20:10] <bschaefer> (getting around the ABI breakage)
[20:10] <sil2100> bschaefer: is it a very big bug that's being fixed?
[20:10] <bschaefer> sil2100, yes :)
[20:11]  * bschaefer digs up the bug report
[20:11] <bschaefer> sil2100, https://bugs.launchpad.net/unity/5.0/+bug/983254
[20:11] <ubot5`> Launchpad bug 5 in Launchpad itself "Plone Placeless Translation Service metadata missing from po files" [Low,Fix released]
[20:11] <bschaefer> opp?
[20:11] <bschaefer> https://bugs.launchpad.net/unity/5.0/+bug/983254
[20:11] <bschaefer> o haha, bot parsed the milestone haha
[20:12] <bschaefer> sil2100, the problem, is I need to fix this as well in the backport: https://bugs.launchpad.net/nux/+bug/1112044
[20:12] <ubot5`> Launchpad bug 1112044 in nux (Ubuntu) "Fcitx can't input word group more than 6 Chinese characters in Dash. Causes a crash if entering to many characters." [Critical,In progress]
[20:12] <bschaefer> which I need to change the event header to handle dynamic allocation of text :(
[20:17] <sil2100> hmmm
[20:17] <sil2100> Troublesome indeed
[20:18] <sil2100> Normally we do not accept any ABI-breakage changes to SRU releases already released, but hm
[20:19] <bschaefer> hmm well I can keep trying to find a way around it, nux just doesn't handle events that can generate more then char text[16] size....
[20:20] <bschaefer> all the work arounds are at someone a stopping point, causing memory leaking, mixing up static/dynamic memory...which can lead to some bad problems
[20:20] <sil2100> I'll have a chat with the SRU team about that, let me bookmark it
[20:20] <bschaefer> are at somewhat* of a
[20:20] <bschaefer> sil2100, thanks!
[20:20]  * bschaefer will try to come up with a way around it..