=== cyphase_ is now known as cyphase [06:04] thomi: hey, around? it seems there are a lot of QA tests failing (autopilot tests on autopilot) [06:04] thomi: https://jenkins.qa.ubuntu.com/job/ps-generic-autopilot-release-testing/370/ === jussi01 is now known as jussi [07:04] didrocks: already fixed in a MP :) [07:04] * thomi is EOD now [07:04] ! [07:04] thomi: oh, everything \o/ ;) [07:04] \o/ [07:04] sorry guys - I've been up since 2AM [07:04] hey sil2100! so it seems we can rerun the QA stack! [07:04] time to sleep [07:05] thomi, didrocks: yaay! [07:05] thomi: no, perfect, we'll rerun the stack now, rocking! :-) [07:05] * sil2100 was worried he'll miss thomi [07:05] thomi: enjoy, see you tomorrow :) [07:05] sil2100: quick quick quick! can't wait to see the QA stack passing :) [07:07] didrocks: all is merged already ;)? [07:08] ah, not sure what thomi meant in fact :) [07:08] sil2100: mind checking trunk and MPs if not there? ;) [07:08] I'm checking that [07:09] I see two MR's filled in approx an hour ago [07:11] sil2100: do you have enough knowledge to review them? [07:13] didrocks: those already got reviewed and approved by Martin it seems, just waiting for the merger to finish merging [07:13] But I wonder if all the commits will fix our problems, hmmm [07:13] sil2100: let's it give it a try once merged :) [07:14] sil2100: how are we on the other apps front? did you see that UTAH was behaving quite well tonight? [07:17] 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] didrocks: will look at trunks to see how this worked out in the end [07:18] didrocks: the webbrowser app should be fixed, as I verified the fix on jenkins by myself [07:18] 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] sil2100: excellent! :-) once you have looked over jenkins, please keep me posted (on webapps for now to finish the bootstrapping) [07:19] sil2100: any ETA for having everything fixed? [07:19] sil2100: as this is our almost last blocker to have -next enabled :) [07:20] 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] sil2100: ok, good :) [07:24] didrocks: btw. how's the new test framework going? [07:25] sil2100: jean-baptiste has a prototype, we'll work on it together today, just finishing the webapps stuff first [07:28] didrocks: excellent ;) [07:29] didrocks: regarding the apps AP's, it seems that fixes have been filled for all the failing projects besides notes-app [07:29] didrocks: I'll poke nerochiaro again about that, and if anything I'll create a patch myself [07:29] As I know the problem and a possible solution [07:30] sil2100: great news! :) [07:30] sil2100: even the media-apps? [07:30] didrocks: yes, both camera-app and mediaplayer-app had some fix landed [07:31] So I hope those would cover the failures we got [07:31] 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] didrocks: we should be fine, yes, I see the branches got merged so I'll re run the QA stack with rebuilding [07:38] sil2100: good, just rebuild the components that changed please :) [08:17] notepad-qml - Demos for Qt Components for Ubuntu [08:17] bad naming of the package? [08:17] anyone knows who do i ping? Ugo? [08:22] tsdgeos: yep I think Ugo. [08:22] what's wrong with the name? [08:22] " Demos for Qt Components for Ubuntu" ? [08:22] :D [08:23] seems it's fixed already though [08:23] at least can find that text in the repo [08:23] ah I see [08:23] yep, somehow i probably have something old in my desktop [08:23] phone is fine [08:26] Cimi: ping [08:30] MacSlow: hey. what was the issue with the failing test then? [08:33] mzanetti, waitForRendering() was the call needed [08:34] mzanetti, thanks to that I also was able to get rid of the wait(0) [08:34] MacSlow: ah right... yeah. that seems to be new since we use the proper mesa driver. [08:34] MacSlow: yeah. makes sense [08:34] mzanetti, test looks a much nicer now without the odd wait(0) [08:35] MacSlow: agreed [08:35] mzanetti, until you and/or Saviq looked over my branch again I'm back on frontend-backend work again helping Jussi [08:36] MacSlow: ok [08:36] basically checking was missing for things like "append", "replace" etc to work correctly [08:37] cool... with the working NotifyOSD backend-frontend running on my system, all regular notifications show up via the new renderer :) [08:38] 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] 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] mzanetti, already done [08:39] MacSlow, you can use "image://gicon/" as source [08:40] Saviq, ah... interesting... thx [08:40] MacSlow, or the Icon component from the SDK [08:40] MacSlow, which has a "name" property [08:40] ah. does that work on GIcon? [08:40] the Icon {} item [08:40] Saviq, I'll opt for the SDK-component then if possible [08:40] MacSlow: definitely [08:41] 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] MacSlow, http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/qml-ubuntu-components0-icon.html btw [08:42] Saviq, hm... [08:42] 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] MacSlow, but anyway, we accept both GIcon names and full paths for the notifications, no? [08:44] MacSlow, Icon only support GIcon names, so it's of not much use for us in that sense [08:45] MacSlow, what we did before is just checked if the given source has / at the beginning [08:45] MacSlow, and if not, prefix it with image://gicon/" [08:47] Saviq, yes that's what NotifyOSD currently does and what we want to keep with the new implementation [08:48] MacSlow, so yeah, Icon is of no use to us [08:49] * greyback moving to office, bbiab === gusch is now known as gusch|away [09:04] didrocks, hey :) [09:05] mzanetti, pong [09:05] Cimi: hey. wanted to ask whats the state/plans for your branch regarding the Launcher using Panel [09:06] mzanetti, I have other tasks pending, but I am happy to work on that [09:06] mzanetti, unfortunately the Panel branch that fixes the Panel is not review yet [09:07] mzanetti, we need this branch before the launcher work [09:07] Cimi: yeah... also dandrader changed the Launcher in a way it uses his dragging area [09:07] so I'm a bit lost on what I should wait or not [09:08] mzanetti, it should just use the panel [09:08] mzanetti, I guess we can remove dragging area from shell, what is it needed for? [09:09] Cimi: no, the new one Daniel is creating [09:09] Cimi: the one where it can find out if the drag should be used by the shell or by the running app [09:11] mmm I need to see this code [09:11] the goal was to use the SDK for those elements [09:11] Saviq, are you aware of daniel's work? [09:12] Cimi, yes I am, it will end up in the SDK ultimately, too [09:12] Saviq, what's its purpose? [09:13] Cimi, it's an directional drag detector [09:13] Saviq, isn't it colliding with the request of writing the Launcher using the Panel? [09:13] Panel or this smart dragging area? [09:13] Cimi, Panel will ultimately use this dragging area [09:14] I see [09:14] Saviq, but I was writing the Launcher using the Panel [09:14] Cimi, that's fine [09:14] Saviq, now he is writing the Launcher using the dragging area [09:14] Cimi, we won't be able to do everything in one go [09:14] which one shall we merge? [09:14] Cimi, even if we merge his for now [09:15] Cimi, once Panel uses Daniel's draggingArea [09:15] Cimi, we'll merge yours [09:15] Saviq, I would say it will be much better if he was simply working into integrating the new dragging area in SDK [09:15] Does Qt have an equivalent to gtk+'s gtk_icon_theme_append_search_path()? [09:16] MacSlow, I don't think it does [09:16] Saviq, Panel useg for launcher removes all references to dragging area [09:16] Saviq, it's work wasted [09:16] *usage [09:16] Cimi, no it's not, because once Panel uses the new DraggingArea (which can't be integrated into SDK yet) [09:17] Cimi, we'll just switch to what you did for the Launcher with panel [09:17] Saviq, which is basically removing bunch of code including dragging area [09:17] Saviq, which will mean removing his branch [09:17] 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] Cimi, yes, when it's integrated into the SDK, it will mean removing his branch [09:18] Cimi, but it will not happen for some time still [09:18] 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] Saviq, mumble? I am not understanding :) [09:19] Cimi, and until then we can use what you did to integrate with the current SDK Panel [09:20] 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] Saviq, we can discuss that in the after the stand-up today perhaps [09:28] 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] 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] mzanetti, we don't think the new dragging area will be integrated in the SDK before 2-3 weeks [09:29] Cimi: ok. thanks [09:29] mzanetti, so I'll probably propose a branch in 3-4 weeks time [09:29] MacSlow, it would probably be best to extend the GIconProvider to support adding custom paths [09:29] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/plugin/giconprovider.cpp [09:30] MacSlow, can you talk to the SDK guys on how to go about that? [09:30] Saviq, I can write a patch for it and mr it [09:30] Saviq, should not be too much work. [09:31] Saviq, who would be the first contact-person for discussion on the SDK-team? Tim? [09:32] MacSlow, sure, you could also talk to renato as he wrote it [09:32] Saviq, ok [09:50] didrocks: the autopilot tests from after the fixes are in, there are less failures but still not enough ;/ [09:50] didrocks: 13 failures on every platform [09:50] didrocks: I mean, per-platform [09:51] I see some import failures, maybe some missing dependencies this means - but that's just 3 of the 13 failures [09:52] I *might* be able to fix some of those then [09:52] sil2100: keep poking! :) [09:52] But Thomi and the other devs would be sweet to have right now ;p [09:52] davidcalle: hey, in a hangout, will be available afterwards :) [09:52] sil2100: right ;) [09:52] didrocks, ok === alan_g is now known as alan_g|cold [10:29] didrocks: https://code.launchpad.net/~sil2100/autopilot/autopilot_test_fixes/+merge/163886 <- some fixes related to the autopilot failures [10:29] fginther: ^ [10:29] Not all I guess, but that's always something [10:29] sweet, let's wait for some QA people for reviewing [10:29] didrocks: ah, wait, I'll also add a changelog entry for those [10:30] sil2100: as you wish, otherwise, it will take the commit log :) === matthijs is now known as htenkalsdfjsdf [10:30] 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 === htenkalsdfjsdf is now known as matthijs === dednick_ is now known as dednick [10:36] mardy: ping [10:36] dednick: pong :-) [10:37] dednick: I'm trying the QMenuModel example file (render-menumodel.qml), but I always get an empty view [10:38] dednick: I changed the busName and path to "com.canonical.indicator.messages" and /com/canonical/indicator/messages/menu [10:39] 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] dednick: but the view still stays empty [10:39] mzanetti, got a moment? [10:39] dednick: any idea of what's wrong? Does it work for you? [10:40] dednick: (and, are you the right person to be bothered about this? :-) ) [10:40] mardy: i havent actually used it myself. :) [10:42] dednick: OK, I'll ask Renato [10:42] mardy: yeah, i was just going to suggest that [10:44] nic-doffay: hey [10:44] nic-doffay: yes [10:45] 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] At the moment it's created by the greeter. [10:47] nic-doffay: I don't really understand the question [10:49] nic-doffay: Isn't the Infographic already separated in Infographics.qml? [10:49] mzanetti, it is. [10:49] nic-doffay: what exactly is the problem then? [10:50] mzanetti, basically should the tests be a part of the greeter or for the component specifically. [10:50] nic-doffay: ah. for the component specifically [10:50] mzanetti, right on, cheers! === gusch|away is now known as gusch === MacSlow is now known as MacSlow|lunch [11:10] mzanetti, just reading through your comments, thanks for the thorough review of the branch. [11:11] cyphermox_: hi :-) [11:11] cyphermox_: see the backlog, about 20 lines ago :-) [11:11] nic-doffay: :) [11:12] urgh [11:13] mardy: not sure I can help you with how QMenuModel works quite yet ;) [11:14] cyphermox_: np, I'll wait for Renato then :-) [11:22] davidcalle: available now :) [11:22] pete-woods: hey [11:22] mzanetti: hi! [11:22] pete-woods: still don't really understand the reason for the QVariantListModel [11:23] perhaps it's a result of my lack of Qt understanding [11:23] basically I want my API to provide two QAbstractItemModels [11:23] didrocks, super small mp https://code.launchpad.net/~davidc3/cupstream2distro-config/100scopes-remove-imdb/+merge/163864 [11:24] and I wanted the quickest implementation I could do [11:24] davidcalle: ok, doing it :) [11:24] so I based it on QStringListModel [11:24] davidcalle: it's removed from the scope json file? [11:24] pete-woods: you want the backend API providing 2 models and aggregate them in the frontend into 1 model? [11:24] didrocks, hmm. Of course not^^ Will mp it in a moment, need to go :) [11:25] pete-woods, are you going to handle this: https://pastebin.canonical.com/91011/ [11:25] I just want to provide two lists [11:25] that can provide change notification - i.e. element changed, row inserted, etc [11:25] nic-doffay: I've already done that one :) [11:26] nic-doffay: I [11:26] didrocks, by the way, not sure you know about that website: http://framli.eu/scopes_browser/index.html?scope=unity-scope-yahoostock [11:26] nic-doffay: I've basically left you the animation and more QML-y ones [11:26] pete-woods, ok wicked [11:27] davidcalle: oh, nice, the name rings a bell to me, but I didn't remember what it was :) [11:28] didrocks, don't trust all the data in it, though, still working on the parser :) [11:28] 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] heh ;) [11:32] 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] But it looks like that wasn't the case. [11:40] JohnLea, ping ! [11:40] JohnLea, your document says: Ctrl + Super + Cursor Left or Right Semi-maximises current window [11:41] which is actually something else than what Grid does as Grid not only semi-maximizes, but also moves the window [11:41] we can of course have shortcuts to just semi-maximize as well [11:42] regarding the other problem: [11:42] it would be (easily) possible to have 2 different shortcuts doing the same thing, so I can implement that for Grid without any problems... === greyback is now known as greyback|lunch === _salem is now known as salem_ [11:55] MCR_; hyia! [11:55] 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] MCR_; scroll down to the end of that doc ;-) [11:56] MCR_; if this is something you could take a look at, could you revert the status of that bug back to triaged? [11:56] MCR_; Thanks ;-) [11:57] JohnLea, yep [11:58] 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] and if there is a system-wide plugin installed, it will be used [11:58] Saviq: the LightDM mock is already there before this branch [11:59] pete-woods, yeah, I know [11:59] shouldn't it be moved in a separate MR? === mmrazik is now known as mmrazik|afk [11:59] pete-woods, that's what I meant by "I missed that in the lightdm review" [11:59] oh, okay :) [11:59] Saviq: we are fine with having Digia LGPL code included, are we? [11:59] pete-woods, sure, we could have a separate MR for that [11:59] JohnLea, consider this bug fixed [12:00] MCR_; awesome! [12:00] mzanetti, depends where, I'd say [12:00] Saviq: real code [12:00] Saviq: not just tests as the other from albert [12:00] mzanetti, well, yeah should be fine [12:00] Saviq: talking about the QVariantListModel [12:00] mzanetti, yeah I gathered === cyphermox_ is now known as cyphermox [12:06] JohnLea, I cannot set to "Triaged" -> I have no rights for that... [12:06] MCR_; no worries, I have already done that ;-) [12:07] JohnLea, I've updated the report with a HOWTO [12:07] mzanetti, huh, is it normal that jenkins/pbuilder works in non-UTF-8 locale (LANG=C, probably?) [12:07] mzanetti, https://jenkins.qa.ubuntu.com/job/unity-api-raring-i386-ci/5/console [12:08] Saviq: don't know. I don't think that has changed lately tho [12:08] mzanetti, no it probably didn't [12:09] mzanetti, was just surprised (and it only showed up because my name is non-ascii ;)) [12:09] I have seen this exact error in autopilot _because_ we were using UTF [12:09] Saviq: ^ [12:09] Saviq: exporting LANG=C before running autopilot tests works around it [12:10] mzanetti, it probably wasn't this exact error ;) [12:10] mzanetti, otherwise setting LANG=C wouldn't help :D [12:11] mzanetti, as setting LANG=C here actually exposes this issue (it's fine in my default locale) [12:11] Saviq: https://bugs.launchpad.net/autopilot/+bug/1154107 [12:11] Launchpad bug 1154107 in Autopilot "autopilot crashes on failed test" [Critical,Incomplete] [12:15] 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] mzanetti, pete-woods well, the LANG=C is for sure not fixing anything - just hacking around an autopilot bug [12:17] fair enough :) [12:17] autopilot | testtools [12:17] yep [12:17] but OTOH having LANG=C in there makes sure that we're explicit about some things [12:18] instead of assuming everything is UTF-8, so it has some advantages === MacSlow|lunch is now known as MacSlow [12:44] fginther: ping === greyback|lunch is now known as greyback [13:03] how can I import unity next in qt creator? http://unity.ubuntu.com/getinvolved/development/unitynext/ lp:unity/phablet [13:03] 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] " Any idea? [13:03] vesar can you start qt creator? [13:03] Mirv, I saw a bug report relating on this: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1178147 [13:03] Launchpad bug 1178147 in qtdeclarative-opensource-src (Ubuntu) "qmlscene not pulling all required dependencies" [Undecided,Confirmed] [13:04] GuidoPallemans, yes [13:04] Qt Creator works just fine [13:04] hmm, I had the same error earlier when launching qt creator [13:04] fixed it by just reinstalling everything qt* [13:04] but you may not want to do that... [13:06] 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] I guess the reason is somehow related to different Qt versions btw my machine and device [13:07] hmm [13:09] mterry: https://code.launchpad.net/~mzanetti/unity/phablet-tease-launcher/+merge/163906 [13:09] how can I import unity next in qt creator? http://unity.ubuntu.com/getinvolved/development/unitynext/ [13:15] GuidoPallemans, just open the CMakeLists.txt file and the .qmlproject file [13:15] GuidoPallemans, unfortunately QtCreator can't have a CMake project that also has QML files currently [13:16] vesar, apt-get upgrade [13:17] vesar, Qt on the image uses 5.0.1 still, but when you install new packages they are already 5.0.2 [13:19] didrocks, in test_parameters, what is "packages" for? [13:19] is that the packages that the test provides coverage for? [13:19] essentially what it tests integration for [13:20] 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] ok [13:20] kenvandine: normally it's only the binaries from the stack that we want to install [13:20] thought so [13:20] (all the rest being in the iso) [13:20] but in this case, we need qt and so on, as it's not in the iso :) [13:20] i got webcred autopilot tests now :) [13:20] about to submit the MP [13:21] \o/ [13:21] although 1 test is failing in jenkins... that isn't failing for me [13:22] * didrocks publishes webapps [13:22] robru: FYI ^ === mmrazik|afk is now known as mmrazik [13:25] vesar: try to run apt-get dist-upgrade? [13:26] Mirv, Saviq : both give me just 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. [13:26] 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] Mirv, oh ok will try that. [13:27] vesar, apt-cache policy libqt5declarative5 ? [13:27] vesar, a potential "apt-get update" might be needed on the device, but you should get 5.0.2 for sure [13:30] Saviq, Mirv: ok running apt-get update + upgrade helped. Thanks! [13:37] Saviq: nic-doffay: standup? [13:37] greyback, good idea [13:37] Cimi: ^^ [13:37] vesar: ok, cool [13:39] greyback, sorry in another hangout [13:39] totally forgot [13:46] MacSlow: thanks for fixing my summary, it's hard to listen & type properly ;) [13:46] greyback, sure np yw... it's always hard to listen (and understand) and write everything down [13:47] 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] greyback, I'm having lunch… thought we were skipping stand ups this week with the uds [13:47] Cimi: first I heard of that :) No worries anyway [13:48] greyback, we did skip last vUDS [13:48] greyback, ooh, OK. Can you describe them to me? I could try to test the lightdm setup that way [13:49] mzanetti, can you vote on https://code.launchpad.net/~macslow/unity/phablet-notification-renderer/+merge/155512 please? [13:49] Saviq: sure [13:49] mterry: sure. Where do you want to test, on your PC, or on a phone/tablet? [13:50] greyback, I guess on my nexus7 [13:51] mterry: ok cool, that's supported [13:51] Saviq: done [13:51] mterry: first, update it, as recent changes landed in mir that you need [13:51] mterry: half watching this...what are you going to run on nexus7? [13:51] if mir...you'll need a special package from kdub [13:51] kgunn, mir, then testing lightdm workflow [13:52] mterry: kgunn: oh that's right, I forgot that [13:57] bregma, Are you on saucy? I'm getting a panel-service crash everytime I close a window. [13:58] tedg, I do have a saucy test machine, would you like me to verify? [13:58] bregma, Uhm, sure. It'd help to know if I'm crazy or not :-) [13:59] Trying to see if I have any locally installed packages that'd matter here. [13:59] 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] dandrader, btw, some interestning read Mr. Voß pointed me at today: http://yangl.org/pdf/gstudio.pdf [14:08] hmm [14:10] mzanetti, in what cases should verify() and tryCompare() used in the QML tests? [14:11] nic-doffay: use compare() and tryCompare() whenever possible [14:11] nic-doffay: there are some cases where they won't work and you have to use verify() [14:13] 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] Ok cheers. What's the difference between tryCompare and compare though mzanetti ? [14:14] nic-doffay: compare() does it NOW while tryCompare() waits a certain amount of time for the condition to become true [14:15] ah, holy crud, my trackpad has gone wild after I upgraded Saucy [14:17] Saviq, did you read it? [14:17] dandrader, not yet [14:17] dandrader, just skimmed === olli_ is now known as olli [14:23] didrocks: sil2100, any luck with the autopilot run? [14:23] thomi: there are still some issues. sil2100 fixed more, but I guess there are some failures [14:23] sorry I didn't stick around any longer yesterday, I was about ready to fall asleep standing up [14:23] didrocks: got a link? I can fix them up today [14:24] thomi: no worry, it was already way too late :) [14:24] * didrocks looks for a link [14:24] thomi: http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/385/ [14:25] * thomi looks [14:25] thomi: sil2100 has a MP to fix some I guess, but not all [14:25] ahh ok [14:25] will look there first then [14:25] https://code.launchpad.net/~sil2100/autopilot/autopilot_test_fixes/+merge/163886 [14:25] thomi: ^ [14:25] cheers [14:27] tedg, yes, I get the crash in unity-panel-service [14:27] \o/ [14:27] Oh, wait. [14:28] * bregma speculates on perhaps there are other explanations for tedg's madness [14:29] it seems apport experiences problems reporting bugs and wants to report a problem about reporting problems [14:29] bregma, Do you have libunity-gtk3-parser0 installed? [14:33] tedg, nope, according to dpkg... this is a clean 13.04 install upgraded to current Saucy with no added extras [14:33] sil2100: can you ping me when you get a moment please? [14:34] bregma, Okay, that kills one theory. [14:34] I also see a crash in unity-greeter related to libido3 [14:35] bregma, tedg: unity-panel-service segfaulting is a known issue/being fixed [14:35] I didn't follow the start of the discussion [14:35] just pointing that [14:35] Oh, cool! [14:36] seb128, Also, do you know when unity-gtk-parser is going into saucy? [14:36] 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] tedg, http://bazaar.launchpad.net/~dbusmenu-team/libdbusmenu/trunk.13.10/revision/442 [14:37] bregma, it should be new since yesterday (side effect of the new glib exposing a libdbusmenu bug) [14:37] bregma, ^ that's the fix [14:37] it happens when you close a win [14:38] tedg, no, cyphermox/sil2100 might know, I think the autopilot issues got resolved, not sure what else is missing [14:39] excellent, not my team's fault (this time) [14:39] tedg: unity-gtk-module was ready afaik, I enabled it last week, perhaps it's just failing tests atm [14:39] sil2100: ? [14:39] cyphermox, do you plan to land libdbusmenu from trunk to saucy now that the fix is in for that? [14:42] I do, just waiting for autopilot to finish so I can override the results. [14:43] great [14:56] * tsdgeos hits greyback and mzanetti with a trout [14:56] tsdgeos: huh? [14:56] now you smell fishy :D [14:57]