=== _salem is now known as salem_ === salem_ is now known as _salem === asac` is now known as asac [07:21] Saviq: morning [07:21] Saviq: jenkins finally approved this: https://code.launchpad.net/~unity-team/unity8/launcher-backend/+merge/173189 [07:22] so if you're still happy with it I think we can try to land it [07:43] MacSlow: hey [07:43] MacSlow: all the notification tests fail for various reasons here [07:43] MacSlow: but not the one you said :D [07:44] mzanetti, did you kill notify-osd? [07:45] MacSlow: I started a new dbus session [07:45] MacSlow: the notification shows up just fine [07:45] MacSlow: but then everything starts going wrong [07:46] mzanetti, I have never seen an issue with the opacity [07:47] mzanetti, I'm not starting a new dbus-session... just getting rid of notify-osd [07:48] MacSlow: no... I don't want to reboot my machine every time I run your tests :D [07:48] MacSlow: the d-bus session is just fine... the notifications show up as expected [07:48] btw... Frank Zappa looks way better than the name would suggest [07:48] mzanetti, :) [07:49] mzanetti, I had to use the stock assets :) [07:49] :D [07:50] mzanetti, so you just started the notification ap-test with "autopilot run unity8.tests.testnotifications"? [07:50] MacSlow: autopilot run unity8.tests.testnotifications.TestNotifications.test_sd_incoming_call [07:50] but yeah [07:51] mzanetti, ah ok... just the single one... I see. [07:51] MacSlow: the shell comes up, it unlocks the greeter and the incoming notification shows up. [07:51] MacSlow: then it times out because it waits for the opacity to become 1 while it stays at 0.99.. [07:52] * mzanetti believes that might be related to the layer.enabled: true thingie [07:52] * mzanetti tries [07:53] mzanetti, I get some warnings/failures too... but not any issue with opacity (http://pastebin.ubuntu.com/5860909) [07:54] mzanetti, I'll try on my laptop [07:54] MacSlow: hmm.... Indeed adding print()s to onOpacityChanged shows it never goes to 1. [07:54] mzanetti, re: launcher-backend yeah, I rebuilt it to get the actually fixed shell for testing with packages on device [07:54] MacSlow: and also, I can see the header from the dash behind shining through [07:54] mzanetti, will test now and skim through again [07:55] Saviq: cool, thanks [07:57] MacSlow: I changed the check to be Eventually(GreaterThan(0.999999)) [07:57] seems to work [07:57] MacSlow: so now I can reproduce your fail [07:58] MacSlow: this one? [07:58] self.assertThat (self.action_send_message_triggered, Equals(True)) [07:58] mzanetti, your issue with the opacity-check is odd still... it also works on veebers machine like that [07:58] MismatchError: True != False [07:58] mzanetti, yeah... that's the issue with the callback not touching the bool flag [07:58] MacSlow: yeah... its odd... no idea why it doesn't really go to 1 [07:59] Saviq: any idea perhaps?^ [08:00] MacSlow: actually... the heightBehavior.enabled=true would never be called in my case then [08:00] MacSlow, mzanetti: I'm not sure it's an autopilot issue. I tried a really simple example in a script and couldn't get my callback called [08:00] mzanetti, doh... still need to pull updates on my laptop... still seeing the "black button"-problem there [08:00] veebers, you think it's a general python-issue then? [08:00] veebers: hi! Big thanks for fixing the autopilot issue ;) [08:01] MacSlow you're using the Ubuntu easings etc.? [08:01] veebers, mzanetti: should we try a newer python? atm 2.7 is used iirc [08:01] MacSlow: or I'm not constructing the callback et. al correctly :-P [08:01] MacSlow: shouldn't matter [08:01] Saviq, for the anims... yes. [08:01] I guess you guys are talking about the latest failures with opacity checks? [08:01] MacSlow, mzanetti I suspect the same issue we found in the SDK yesterday [08:01] sil2100: no worries, this was the failing tests one yes? [08:01] ah... [08:01] Saviq, like what issue? [08:01] https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1199550 [08:01] Ubuntu bug 1199550 in Ubuntu UI Toolkit "Panel.animating doesn't return to "false"" [Undecided,Fix committed] [08:01] Saviq: good point [08:02] MacSlow the bezier easing added in rev 600 of the toolkit http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/600 [08:02] MacSlow, seems to not reach 1.0 [08:02] MacSlow, some rounding error [08:02] veebers, well there's one "difference" between the autopilot tests and the plain python-regression-tests... [08:03] MacSlow, ideally you should look to the animation's running prop, not compare reals [08:03] MacSlow, mzanetti although I would consider that a bug that an animation that's supposed to reach 1.0 doesn't because of some interpolation error [08:04] Kaleo wasn't convinced yesterday, but I'll have a chat with him about this later today [08:04] veebers, mzanetti: since we had to do this "from gi.repository import GLib, Notify" I had to change the parameters passed to add_action() ... needs two additional arguments now otherwise it fails [08:04] Saviq: yeah... but the panel.animating never becoming false might be caused by the same... some thing never reaching the final state because of the same [08:04] Saviq: to me that's an error, especially that we sometimes assume it reaches 1.0 [08:04] sil2100, exactly, you expect it to [08:05] mzanetti, it definitely is (fixed in toolkit trunk) [08:05] (like with opacity, suddenly causing failures in many autopilot tests ;p) [08:05] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/revision/601 [08:05] Saviq, ok. [08:05] s/fixed/workarounded/ [08:06] Saviq: yeah... that doesn't seem like a proper fix [08:07] mzanetti, well, it fixes the issue at hand, but not all the others [08:07] Saviq: it fixes one of the symptoms, but not the cause [08:09] mzanetti, yup, what I meant [08:10] now... what's a bit more of a problem is that I replaced the UbuntuNumberAnimation with a NumberAnimation and I still see the issue [08:11] MacSlow: ugh, I can get it working if I look at these examples: http://hashbang.fr/tutoriel-notify.html [08:11] MacSlow: it's using Gtk.main() at the end [08:11] morning [08:11] anyone from the am working in unity 7, that can help me debug a bug on 13.10 ? thanks [08:11] veebers, hm... in the regression-tests I'm using a dedicated Gtk-mainloop too [08:12] veebers, but I did assume that I don't need that in autopilot-tests [08:14] veebers, http://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/view/head:/examples/interactive-notification.py#L65 [08:14] veebers, http://bazaar.launchpad.net/~unity-api-team/unity-notifications/trunk/view/head:/examples/sd-example-incoming-call.py#L102 [08:14] veebers, just for reference [08:15] MacSlow, mzanetti can you check the output from http://pastebin.ubuntu.com/5860941/ [08:15] MacSlow: hmm thanks. I might have to ask thomi re: that one tomorrow [08:15] veebers, ok... at least we're a bit closer now to sort it out [08:15] MacSlow: aye [08:16] Saviq: yeah... thats the cause [08:16] Saviq: stays at 0.999999999634 [08:16] Saviq, "true 0 [08:16] false 1 [08:16] " [08:17] MacSlow: you need to upgrade to the latest ubuntu-ui-toolkit to reproduce the bug [08:17] MacSlow: well, don't... [08:17] mzanetti, :) [08:17] Saviq: here's the exact output: [08:18] mzanetti, this could even cause some unnecessary blending [08:18] true 0 [08:18] false 0.9999999999361473 [08:18] Saviq: yes, it does. I can see the background of the notifications shining through [08:18] mzanetti, that's expected, actually ;D [08:18] Saviq: huh? [08:18] mzanetti, they're see-through - that's per-design [08:19] mzanetti, certainly... at least in the "black" area [08:19] Saviq: If I change all the UbuntuNumberAnimations to just NumberAnimations its not the case any more [08:19] well, I'm talking about the icon mostly [08:19] mzanetti, only buttons, text and icons are meant to be opaque [08:19] mzanetti, I doubt it's visible (I doubt 8 bits can represent the difference) [08:19] when rendered into ARGB [08:20] right... I just checked more carefully again.. its still there [08:20] but tests are passing again [08:20] mzanetti, if you can see through the avatar, for example, that's a visual bug [08:20] Saviq: I do [08:21] but only with the black icon... not with the Frank Zappa lady :D [08:21] mzanetti, Saviq: maybe another newly introduced issue with the SDK? I don't have that here on my desktop-machine... let me look at the version of the installed SDK [08:21] mzanetti, what should I be looking at? [08:22] MacSlow: actually... why does the same test, the incoming call one most of the times have the picture of that woman, but sometimes some grey abstract thingie? [08:22] mzanetti, ? [08:22] mzanetti, never seen that issue [08:23] * mzanetti tries to reproduce [08:23] yeah... just happened again [08:23] running this "autopilot run unity8.tests.testnotifications.TestNotifications.test_sd_incoming_call" [08:24] most of the times I get that lady in the icon. Sometimes only some grey icons with slightly orange stripes in it. thats when the background shines through... [08:24] Saviq: ^ [08:24] mzanetti, sil2100, MacSlow bug #1199662 [08:24] bug 1199662 in Ubuntu UI Toolkit "New easing causes animations not to reach their target values" [Undecided,New] https://launchpad.net/bugs/1199662 [08:24] Saviq, mzanetti: for what it's worth... I've 0.1.46+13.10.20130709-0ubuntu1 of qtdeclarative5-ubuntu-ui-toolkit-plugin installed here on my desktop [08:24] mzanetti, which branch btw? [08:24] Saviq: ~macslow/unity8/notification-autopilot-tests/ [08:26] Saviq: I'm looking at putting together a scope to expose recent apps on the phone (something that is currently handled via custom UI). Do you know if the API it uses to get the list of running applications is available outside of the shell process? [08:26] tsdgeos, http://pastebin.ubuntu.com/5860963/ [08:27] Saviq: yeah [08:27] no clue where that warning comes from tbh [08:27] had a look at the define [08:27] and it has just one param :/ [08:27] tsdgeos, k [08:27] jamesh, it is / could be, but I don't believe that's what you should be looking at [08:27] jamesh, I believe we should use zeitgeist there [08:28] Saviq: i'll have a second look [08:28] jamesh, while a specialized renederer in the shell would pick up the snapshots [08:28] jamesh, running apps are going to be killed arbitrarily to save resources [08:29] jamesh, so your "Recent apps" would start disappearing randomly [08:29] but yeah, all QSKIP in Qt code are like that [08:29] Saviq: I remember you saying that, but when I was talking with thostr_ he said that the design still calls for it to show running apps :( [08:29] ./auto/corelib/io/qfile/tst_qfile.cpp:1900: QSKIP("Not enough space to run test"); [08:29] jamesh, that's because they don't have a clue what a running app is ;) [08:30] jamesh, i.e. there can't be a notion of a running app if we're killing and restarting them all the time [08:30] tsdgeos, k, throw a #pragma at it maybe at some point [08:30] jamesh, but we talked about this yesterday [08:30] jamesh, in the dash sync [08:30] jamesh, and I think the agreement is that we should use zeitgeist [08:31] jamesh, granted, you need to be able to "close" such a recent app [08:31] okay. [08:31] jamesh, and that would actually kill the app, if it's running, but otherwise it should just disappear from the recent ones, that's it [08:31] so I guess we still need an API to identify the apps that are currently running? [08:31] Saviq, since the OptionSelector has so many variations for content, should the delegate be set externally be the user? [08:31] *by [08:31] jamesh, the shell does, the scope doesn't [08:32] jamesh, but please confirm with thostr that's where we're goinf [08:32] going [08:32] okay [08:32] jamesh, both launching and closing apps should be events in zeitgeist, I think [08:33] jamesh, and you should just look at that and compile a list that were recently launched but not yet closed [08:33] jamesh, ordering might be tricky, though - we might need to put focus events in, too :/ [08:34] jamesh, as in "app focused" event to order by [08:34] now it does feel like zg is maybe not the best place [08:35] jamesh, greyback we might need to build a volatile stack of "apps launched, but not closed" [08:35] okay [08:35] jamesh, greyback is working on unity8 integration with Mir where all of this will happen [08:36] Saviq: ok. I'd expected as much [08:36] greyback, that's for "running apps", that aren't necessarily running anymore (lifecycle) [08:37] greyback, do you think it'd make sense for jamesh to build a scope that would talk to the current observer on Surfaceflinger [08:37] greyback, or would the new API be different enough that he should target the new api straight away? [08:38] Saviq: yep. I'd assumed App Manager will have list of all apps running or suspended or killed-with-resume-data [08:41] Saviq: ‌thinking... it doesn't really make sense to do the SF work, if it'll be thrown away within a few weeks. [08:41] greyback, I agree [08:42] greyback, will app manager know the difference between app-with-resume-data and app-with-no-resume-data? [08:42] Saviq: that I have to learn. [08:42] jamesh, greyback can you please sync up on those topics? [08:42] Saviq: it will be the one sending the kill signal, so I expect so [08:43] jamesh: hey, let's have a meeting on this, so we can swap info [08:45] greyback: sure. I currently don't have any code for this, so there isn't any legacy concerns if there is a new API in development [08:46] jamesh: indeed. [08:49] jamesh: meeting scheduled, does hte time suit you? [08:52] greyback: looks good. [08:52] jamesh: cool [08:53] Saviq: quick'n'easy one: https://code.launchpad.net/~mzanetti/unity8/fix-1199622/+merge/173883 [08:53] mzanetti, obviously the "Critical" there was tongue-in-cheek ;) [08:53] mzanetti, I'd never have noticed (nor did our designers, so...) [08:53] yeah... [08:54] Saviq: but funnily Cimi noticed the same for the separator line, but not for the icon [08:54] mzanetti, yeah remember that :) [08:55] mzanetti, oh michael [08:55] mzanetti, off topic [08:55] hehe [08:55] mzanetti, a friend told me that the ubuntu icon is flipped [08:55] Cimi: haha [08:55] mzanetti, is he right? don't have the phone running now [08:55] just fixed that [08:55] ok [08:55] good [08:55] Cimi: https://plus.google.com/u/0/photos/104438618743851678614/albums/5898788268517651553/5898788275502369234?cfem=1&pid=5898788275502369234&oid=104438618743851678614 [09:17] andyrock: hello! [09:18] sil2100, hey [09:19] andyrock: do you know what's the status with compiz on saucy? Can we re-enable it for daily release? [09:19] sil2100, nope... there is a bad regression [09:19] Oh? [09:19] sil2100, let me find the bug number [09:20] sil2100, https://bugs.launchpad.net/compiz/+bug/1198000 [09:20] Ubuntu bug 1198000 in compiz (Ubuntu) "Regression: r3751 causes all unmaxed windows to shrink both horizontally and vertically on each subsequent opening, probably by exactly the size of the decoration" [Critical,Triaged] [09:20] we can revert that revision [09:20] but than we have another regression with qml5 apps [09:20] *qt5 [09:21] oh shit [09:21] Ok, so there's a deadlock right now, hm - I see no one is assigned here [09:22] i'm trying to fix it, but decor.cpp is not that simple :D [09:23] hohoho [09:23] Ooooh no it isn't ;) I had my share of that file [09:23] andyrock, sil2100, also i can't build trunk compiz because of some gmock issues [09:25] andyrock: ^ ? Did anything change regarding that? [09:25] sil2100, mhr3 nope, maybe there is some cmake issue with xorg-gtest? [09:26] well, i saw gmock fixes proposed for nux and unity.. so definitely something wrong there [09:28] sil2100, btw is unity still failing on the dbus issues? [09:28] mhr3, yeah but I still can build compiz trunk here [09:28] andyrock, from clean tree? on s? [09:28] mhr3, let me clean it [09:29] yeah on S sure [09:29] mhr3: not sure, didn't see the DBus hang this week, but there are a lot of tests failing anyway [09:30] sil2100, well that is the dbus hang [09:30] It is? But it's only around 21 failures per platform and all seem to be preview tests [09:30] sil2100, all those other super-hangs were caused by the recordmydesktop issue [09:30] MismatchError: After 10.0 seconds test on DashView.preview_displaying failed: True != dbus.Boolean(False, variant_level=1) [09:31] These are because of DBus? [09:32] http://10.97.0.1:8080/job/autopilot-saucy-daily_release/387/testReport/ <- that's why I wanted someone to take a look at yesterdays failures, since to me those looked like normal failures [09:32] But I might be mistaken [09:33] sil2100, i see preview failures, hud failures, search timeouts, bamf failures, all dbus stuff [09:34] https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199696 [09:34] Ubuntu bug 1199696 in unity (Ubuntu) "SIGSEGV, unity-panel-service crashes and eats a core" [Undecided,New] [09:34] if anyone from unity7 can look it up [09:35] sil2100, is there any way to re-run the testing with bustle-pcap running? [09:35] sil2100, but probably just for one run, cause 50minute bustle-pcap session will produce a file that will be a few hundred mb === dandrader is now known as dandrader|afk [10:22] mhr3: hm, I guess we could do that, but not sure how to do it only for one run, although we might modify the configuration of otto temporarily and then resume it back to the way it was [10:23] mhr3: good to know it's all caused by dbus issues [10:23] mhr3: since really, the logs don't say anything about that [10:23] At least not explicitly [10:23] sil2100, guess we can just connect to the lxc once the testing starts and run it manually === dandrader|afk is now known as dandrader [10:24] sil2100, although i see that libunity on powerpc failed [10:24] Yes, and one scope, looking into that [10:24] (for i386) === hikiko is now known as hikiko|lunch [10:25] Need to re-try the jobs [10:25] sil2100, ping me once the ap testing will be about to start i'll try to do the bustle capture [10:27] jibel, if i want a log file to survive and be exported as a result in jenkins is it enough to just put it some special dir? [10:27] mhr3: ok - what about the libunity failure for powerpc? I saw some unit test failing I think... although I also think we're not really caring about the powerpc status [10:27] mhr3: I think it's sufficient if it land in some non /tmp directory [10:27] We can fetch if from the diff then [10:27] sil2100, looks like some odd race, just re-run [10:29] k [10:33] Saviq: https://bugreports.qt-project.org/browse/QTBUG-32338#comment-209093 and https://codereview.qt-project.org/#change,60809 [10:34] mhr3, put it in /var/local/autopilot/ [10:34] and it will be attached as artifact under results/autopilot/ [10:34] jibel, great, thx [10:40] Saviq: nic-doffay: any reason this is not top-approved? https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173752 [10:42] mhr3: re-ran the stack, will poke you once the check job gets pushed to otto [10:42] sil2100, cool thx [10:43] mhr3: ok, autopilot job started [10:43] mhr3: http://10.97.0.1:8080/job/autopilot-saucy-daily_release/396/ [10:51] Saviq, figured you might want someone else to take a look. But I'll do it now. === 6JTAA2M02 is now known as tvoss === MacSlow is now known as MacSlow|lunch === hikiko|lunch is now known as hikiko| === hikiko| is now known as hikiko [11:17] nic-doffay, this is a simple enough change, and easy to test (did you get to test on a Nexus 10, where the slowness is most visible?) [11:18] nic-doffay, but it's mostly about assuring that you see no regressions [11:19] tsdgeos, awesome [11:21] tsdgeos, src/quick/items/qquickgridview.cpp only has whitespace change, is that allowed in Qt patches? [11:21] Saviq: hmmm, hmmm [11:21] * tsdgeos looks at the code [11:22] tsdgeos, scratch that [11:22] ok [11:22] tsdgeos, I just can't read the gerrit diff [11:22] i moved the code outside the if [11:22] tsdgeos, yeah [11:22] tsdgeos, too bleak colors there :) [11:23] he he [11:27] Saviq, I didn't test on a Nexus 10 which is part of the reason I held off. === alan_g is now known as alan_g|afk [11:27] nic-doffay, you don't have one, right? [11:27] Saviq, negative. [11:28] tsdgeos, mzanetti you guys have a n10? [11:28] Saviq: I do [11:28] i do [11:28] mzanetti, could you look at https://code.launchpad.net/~saviq/unity8/improve-openeffect/+merge/173752 quickly [11:28] Saviq: sure [11:28] tsdgeos, if you want to, try that↑, too [11:28] it's a simple fix for nasty UX :) [11:28] well, it'll take ages [11:29] have to charge, flash, try :D [11:29] same here ^^ [11:29] lol [11:30] at least I already have the flipped image on it... so maybe a reflash is not required [11:30] guys, it only takes like 10 minutes to download & flash here ;P [11:31] and anyway most of the download is common between devices, so :P [11:31] Saviq: yeah... but charging it enough to survive a flash takes a bit longer [11:31] mzanetti, :P [11:31] Saviq: nah... 10 mins should be ok [11:32] mhr3: any luck? [11:33] sil2100, did it finish yet? [11:34] mhr3: still running - did you start bustle-pcap? [11:35] sil2100, yea, it's half a gig already :) [11:35] ohshit [11:35] jibel: hope there's enough space for that? [11:35] ^ [11:35] that's why didn't want to do it on every run :) === alan_g|afk is now known as alan_g [11:40] sil2100, enough space for what where ? :) [11:42] jibel: additional logs from bustle-pcap - it weights over 0.5GB already! ;) [11:42] (just for one run) [11:42] tsdgeos, some of the filters are taken from unity-2d, so © Kaleo 2011 might be right :) [11:42] ®©™ [11:42] ahhh [11:42] * Saviq loves compose :D [11:43] sil2100, it will be fine on the test host but will maybe causes some problem with the publication to jenkins.qa.u.c [11:44] jibel: can we not publish that one build? [11:44] tsdgeos, I just love how small the Qt patch is :) [11:44] yep :-) [11:44] sil2100, if it's running it's too late [11:44] tsdgeos, it might actually get in upstream :D [11:45] booo... [11:45] tsdgeos, will setting null / undefined to those props call reset*? [11:46] that is a good question [11:46] i was wondering what uses the RESET property function [11:46] tbh not sure [11:46] that's why i added the Q_INVOKABLE to reset* [11:47] let me see if undefined indeed calls the reset* and then don't need the Q_INVOKABLEs === dandrader is now known as dandrader|afk === MacSlow|lunch is now known as MacSlow [12:07] tsdgeos, btw, should we allow only setting one of them? I know it doesn't make much sense... and printing debugs will just spew errors out on normal usage due to lack of sync [12:07] * Saviq wants tuples ;) [12:12] Saviq: improves things a little yes. [12:12] Saviq: there is still a small hickup when it loads the image for the first time [12:12] Saviq: but once that happened, its perfectly smooth now [12:13] mzanetti, yeah, the hiccup... hickup? hikkup? stupid speller [12:13] mzanetti, it's the Image / UbuntuShape [12:13] mzanetti, we have the same in the dash views now when whole categories are created at a time [12:14] mzanetti, we should try and isolate that to either and make sure we fix it if it's the shape [12:15] can anyone point me in the direction of the media player app's QML plugin for the MPRIS API? [12:15] I knew it was "hiccup", both en_US and en_GB, stupid aspell or whichever [12:15] I'm told it uses the C API generated from http://bazaar.launchpad.net/~unity-team/libunity/trunk/view/head:/src/unity-sound-menu-mpris.vala [12:15] but I just can't see it in the mediaplayer-app [12:15] pete-woods, jhodapp and renato would be the best PoCs [12:15] Saviq: thanks [12:15] pete-woods, they might not be here yet [12:16] Saviq: okay, seems everyone I need today is in the wrong timezone :) === greyback is now known as greyback|lunch [12:20] * mzanetti wonders if its actually a good idea that we install app-specific plugins (not intended for usage in other apps) int QT_QML_DIR [12:21] mzanetti: not sure what QT_QML_DIR is set to, but it should be some kind of libexec//(plugin?) as a private library dir [12:22] didrocks: QT_QML_DIR is /usr/lib//qt5/qml/ [12:22] didrocks: basically where Qt stuff itself is too [12:22] yeah, should s/qt5// IMHO [12:22] didrocks: yeah. I agree [12:22] if it's not going to be reused by multiple apps [12:24] mzanetti, didrocks +1, what we did for the shell [12:24] mzanetti, which plugins are you thinking? [12:25] Saviq: PhoneApp, Browser, CameraApp... [12:25] Saviq: bascially everything in there except Qt stuff itself and Ubuntu.Components [12:25] and a few other exceptions [12:25] lide Dee probably [12:25] like [12:26] ShareApp might be an exception too... depending on whats in there [12:29] mzanetti, then yeah, +1 [12:29] mzanetti, they should be installed in private under $LIBDIR//qml [12:31] * mzanetti just realized that the terminal-app uses KDE's konsole :) [12:31] tsdgeos: ^ === pete-woods is now known as pete-woods-away [12:34] the terminal-app could do with exiting when you type exit! :p [12:34] mhr3: the AP tests finished [12:35] sil2100, yep, downloading the log [12:35] mhr3: 511 MB ;) === pete-woods-away is now known as pete-woods [12:42] Saviq: ping [12:43] kgunn, pong === dandrader|afk is now known as dandrader [12:56] mzanetti: yep [13:01] mzanetti, add =2 to pkg_check_modules(LAUNCHER_API REQUIRED unity-shell-launcher) maybe? [13:01] Saviq: is that really a question? [13:02] mzanetti, you decide :D [13:02] dude [13:02] :SD [13:02] mzanetti, it'll fail if the version is different, so yeah, probably makes sense :) [13:02] yes. I agree [13:02] * mzanetti fixes === greyback|lunch is now known as greyback [13:08] Saviq: pushed [13:08] mzanetti, thanks [13:20] sil2100, ehm, so great, the bustle tools can't really handle huge captures [13:20] $ bustle --count dbus.bustle [13:20] Stack space overflow: current size 8388608 bytes. [13:21] oh and yes, it was using 6gb of ram [13:23] lol [13:25] eeh [13:25] So we're again with nothing? Or can you [13:25] read something from what we got? [13:25] (or we got nothing) === zoktar_ is now known as zoktar === broder_ is now known as broder [13:32] mzanetti, hmm =2 didn't work [13:32] so... who is going to take notes... Saviq or Cimi? [13:33] Saviq: jenkins approve!! [13:33] Saviq: hmm. I did a test run here... printed "found launcher (version 2)" [13:33] dednick, nice [13:33] mzanetti, yeah, change it to 1 or 3 [13:33] mzanetti, says that it found (version 1) etc. [13:33]