[08:07] <Saviq> robru, hey, if you still around - any word why u8 wasn't released overnight?
[08:12] <Saviq> morning, all
[08:13] <tsdgeos> moooornign
[08:38] <Saviq> tsdgeos, wanna do a nasty review?
[08:39] <Saviq> mzanetti, ↑ or you?
[08:39] <tsdgeos> Saviq: the cleanup one?
[08:40] <Saviq> tsdgeos, yeah https://code.launchpad.net/~saviq/unity8/clean-root/+merge/199314
[08:40] <Saviq> tsdgeos, it's basically moving stuff around
[08:40] <tsdgeos> yeah that one i was refering to
[08:40] <tsdgeos> Saviq: can do
[08:40] <Saviq> tsdgeos, thanks
[08:41] <Saviq> tsdgeos, the tests pass, so that's 95% confirmation it's fine
[08:41] <Saviq> tsdgeos, but stuff like ./build, ./run, ./run_on_device would be good to verify
[08:41] <tsdgeos> yep
[08:43] <Saviq> tsdgeos, one other thing that I want to do, but not sure I want to do now... is make them all QML imports, so import Unity.UI.Dash or something, instead of "../Dash" or so
[08:44] <tsdgeos> hmmm
[08:44] <tsdgeos> now = in this MR
[08:44] <tsdgeos> or
[08:44] <tsdgeos> now = after this MR
[08:44] <Saviq> tsdgeos, in
[08:44] <Saviq> tsdgeos, will prolly wait for dednick's indicator refactoring, though
[08:45] <tsdgeos> wouldn't do it in this one
[08:45] <Saviq> tsdgeos, +1
[09:04] <tsdgeos> Saviq: https://code.launchpad.net/~aacid/unity8/regenerate_pot_file/+merge/199413
[09:04] <tsdgeos> we need to get better at catching this stuff
[09:04] <Saviq> tsdgeos, true
[09:04] <Saviq> tsdgeos, but actually... that should not be our string to translat
[09:04] <Saviq> e
[09:05] <Saviq> tsdgeos, it should come from whoever asked for the SIM dialog
[09:05] <Saviq> tsdgeos, so let's see to fix that instead
[09:08] <tsdgeos> that i don't know D:
[09:09] <tsdgeos> asac:
[09:09] <tsdgeos> err
[09:09] <tsdgeos> asac: sorry
[09:09] <tsdgeos> Saviq: sure
[09:09] <tsdgeos> damnit
[09:09] <tsdgeos> run_on_device updated the libc7 of the phone
[09:09] <tsdgeos> and is now stuck in that "do you want to restart serveices" ncurses window
[09:09] <Saviq> tsdgeos, ouch... why would it upgrade it :?
[09:09] <tsdgeos> libc6 i mean
[09:09] <tsdgeos> Saviq: because there's a new version out :D
[09:10] <Saviq> tsdgeos, yeah, but we're not doing upgrade
[09:10] <Saviq> tsdgeos, well
[09:10] <Saviq> tsdgeos, probably something we're installing as deps
[09:10] <tsdgeos> something must depend on it i guess
[09:10] <Saviq> got built against the new one, yeah
[09:10] <tsdgeos> ok, let's reboot the phone and do this manuall
[09:10] <tsdgeos> y
[09:10] <Saviq> tsdgeos, no need to reboot
[09:11] <Saviq> tsdgeos, can do second shell and kill the dialog
[09:11] <tsdgeos> too late :D
[09:11] <tsdgeos> rebooting was easier ;-)
[09:11] <tsdgeos> Saviq: so you opening a bug for the "we should not have this text" thing?
[09:12] <Saviq> tsdgeos, fixing it, even
[09:13] <tsdgeos> cool
[09:15] <Saviq> mzanetti, you get a slap on the wrist for the fullscreen notifications, there's reaching out of scope all over ;P
[09:15] <mzanetti> Saviq: ?
[09:16] <Saviq> mzanetti, NotificationMenuItemFactory reaches to notification and notificationsList objects directly
[09:16] <mzanetti> ah
[09:17] <mzanetti> Saviq: I'll fix it
[09:17] <Saviq> mzanetti, almost there
[09:17] <Saviq> mzanetti, you'll review / test
[09:17] <mzanetti> ok
[09:17] <tsdgeos> Saviq: btw almost everyone's going to get a nice conflict after your clean-root thing :D
[09:17] <Saviq> tsdgeos, actually not really
[09:18] <Saviq> tsdgeos, I was expecting it, but bzr seems to deal fine with renames when merging
[09:18] <tsdgeos> nice thing
[09:18]  * mzanetti is afraid of merging the appmanager rework with that
[09:19] <mhr3_> the one feature that works well in bzr... renames
[09:19] <tsdgeos> Saviq: can i complain against the src/include thing?
[09:19] <Saviq> tsdgeos, yes you can
[09:20] <tsdgeos> Saviq: at least you should move src/Panel/Indicators/client/indicatorsclient.h to include to make it equally painful everywhere :D
[09:21] <tsdgeos> i'd prefer we'd do away with that artificial separation
[09:21] <tsdgeos> but oh well
[09:21] <tsdgeos> let's be artificual everywhere if we are going to be
[09:26] <Saviq> tsdgeos, I just didn't want "src" to be in include paths by default
[09:27] <Saviq> tsdgeos, while paths.h should be available virtually everywhere
[09:27] <Saviq> tsdgeos, so can we say that stuff that's only a header (paths.h, ApplicationArguments.h) would remain in include/
[09:27] <Saviq> tsdgeos, but h+cpp would go into src/ ?
[09:29] <tsdgeos> ApplicationArguments.h is cheating
[09:29] <tsdgeos> since i could split the code over to a .cpp and then you move it to src/ :D
[09:31] <tsdgeos> and it's only used by main.cpp so it would not hurt either
[09:31] <tsdgeos> if you want to leave paths.h.in in include, i'm fine with that
[09:31] <tsdgeos> noone ever edits that file
[09:33] <mhr3_> Saviq, ehm, any idea why https://code.launchpad.net/~unity-team/+archive/demo-stuff/+recipebuild/610784/+files/buildlog.txt.gz failed?
[09:34] <Saviq> mhr3_, which one is that?
[09:34] <mhr3_> scopes-api in demo-stuff
[09:35] <Saviq> mhr3_, I only just built unity-api in there, restarted scopes-api builds now
[09:35] <mhr3_> Saviq, i did that 5minutes ago, resulted in that error
[09:35] <Saviq> mhr3_, hmm maybe unity-api wasn't published yet?
[09:35] <mhr3_> it was
[09:35] <mhr3_> at least that's what the ppa page said
[09:35] <Saviq> mhr3_, in other words, no, no idea
[09:38] <Saviq> mzanetti, here's my diff, can you please take over, then - http://paste.ubuntu.com/6593292/
[09:40] <tsdgeos> Saviq: so what do you want to do with the include thing? leave it as it is? or rework?
[09:41] <Saviq> tsdgeos, true, AppArgs should be .cpp really
[09:41] <Saviq> tsdgeos, I'll fix those
[09:41] <tsdgeos> ok
[09:44] <mzanetti> Saviq: yes
[09:45] <Saviq> mzanetti, I'll have another one, that one breaks something
[09:45] <Saviq> mzanetti, http://paste.ubuntu.com/6593326/
[09:45] <Saviq> Notification vs. Item made it not start at all, for some reason :?
[09:46] <Saviq> mzanetti, are there no tests for the fullscreen notification btw? I don't even know how to trigger it?
[09:46] <mzanetti> Saviq: there should be AP tests for it afaik
[09:46] <dednick> Saviq: https://code.launchpad.net/~nick-dedekind/unity8/StrFTimeFormatter/+merge/192343 ?
[09:47] <Saviq> dednick, on it
[09:47] <mzanetti> Saviq: and there are qmltests for the content (tst_Lockscreen.qml)
[09:47] <dednick> Saviq: ta
[09:48] <Saviq> mhr3_, built now
[09:48] <Saviq> mhr3_, so must've been too early
[09:48] <mhr3_> Saviq, grrr....
[09:48] <tsdgeos> dandrader: seen that i added the "try" thing
[09:48] <tsdgeos> ?
[09:50] <Saviq> mzanetti, no tests added in https://code.launchpad.net/~macslow/unity8/notification-fullscreen-support/+merge/196308 at least
[09:50] <dandrader> tsdgeos, yep, will check it out now
[09:50] <Saviq> mzanetti, so it doesn't look like there are any
[09:51] <Saviq> dandrader, hey, re: the unity-api test crash... I got it on stable just as well
[09:52] <Saviq> dandrader, unless I did something wrong when building, but I tried not to
[09:52] <Saviq> dandrader, you made sure to test under i386?
[09:52] <dandrader> Saviq, yes
[09:53] <dandrader> Saviq, only if stable went sour since the last time I tried it
[09:53] <Saviq> dandrader, no, I actually tried the day after you tried or so
[09:53] <dandrader> Saviq, do you at least get the failure in testApplication?
[09:53]  * Saviq will try again
[09:54] <Saviq> dandrader, don't remember, let me rinse&repeat
[10:10] <dandrader> Saviq, is there a command to reload all unity7 indicators
[10:10] <dandrader> ?
[10:10] <Saviq> dandrader, yeah, start unity8 and Ctrl+C it ;)
[10:11] <dandrader> Saviq, no
[10:11] <Saviq> dandrader, you might also want "restart unity-panel-service"
[10:11] <dandrader> it does not bring all the original indicators back
[10:11] <Saviq> dandrader, the only remaining one should be "start indicator-application" I think
[10:11] <Saviq> dandrader, which one are you missing?
[10:11] <dandrader> indicator-multiload and the network one
[10:12] <Saviq> dandrader, start indicator-[TAB] will let you know which are not running and can be started
[10:12] <Saviq> huh, what's indicator-multiload?
[10:12] <Saviq> dandrader, network is nm-applet
[10:12] <Saviq> dandrader, no upstart integration, so just Alt+F2, nm-applet
[10:12] <dandrader> Saviq, "Graphical system load indicator for CPU, ram, etc."
[10:13] <Saviq> dandrader, k
[10:13] <dandrader> Saviq,  "start indicator-application" does the trick. thanks@
[10:13] <dandrader> !
[10:13] <Saviq> dandrader, cheers
[10:20] <Mirv> tsdgeos: thanks btw for nudging towards syncqt, it has solved all but one of my snapshot module problems
[10:20] <tsdgeos> cool
[10:21] <Mirv> so I'm running syncqt and generating a patch out of it, which fixed qtfeedback + qtsystems + qt3d, but qtpim seems to have some additional problem
[10:23] <Saviq> tsdgeos, pushed
[10:23] <Saviq> /food
[10:23] <tsdgeos> dandrader: noooo, i have a todo :D
[10:23] <tsdgeos> dandrader: or maybe we can do it after the merge happens
[10:24] <dandrader> tsdgeos, what todo?
[10:24] <tsdgeos> dandrader: as a smaller review?
[10:24] <tsdgeos>     // TODO Add support for additions/removals at end that are not reset calls
[10:24] <dandrader> ah
[10:24] <tsdgeos> maybe we can get this big chunk merged
[10:24] <tsdgeos> and then iterate on this small thing?
[10:25] <tsdgeos> it'll be an easier review too
[10:25] <tsdgeos> since it'll be smaller
[10:25] <dandrader> tsdgeos, yes, it won't break anything anyway
[10:25] <tsdgeos> oka
[10:25] <tsdgeos> thanks for the review :-)
[10:25] <tsdgeos> dandrader: btw don't know if you realized you can write a number in the try thing
[10:25] <tsdgeos> in the area below the add button
[10:25] <tsdgeos> i did not make it too obvious :D
[10:25] <dandrader> tsdgeos, it did. but just from reading the code
[10:26] <tsdgeos> ok :D
[10:27] <dandrader> tsdgeos, indeed looks almost like a hidden feature. I though about commenting about it but I concluded that I have already harassed you enough in this review
[10:27] <dandrader> and the buttons also look like they are disabled because their colors are washed out (greyish
[10:27] <dandrader> )
[10:28] <greyback> mzanetti: I can fix your flicker by adding a longer delay to the grantFocusTimer. I tried 100ms
[10:28] <mzanetti> greyback: yeah. but doesn't sound like a solution
[10:28] <greyback> mzanetti: the flicker was that Mir had changed the focused app before you had even started animating
[10:28] <mzanetti> greyback: yeah. and that's what I don't understand why
[10:29] <mzanetti> greyback: as I set the image to be visible and everything, then start a timer and only when the timer timeout is done, I tell Mir to actually switch the apps
[10:30] <mzanetti> greyback: so in theory there shouldn't be a timer needed at all. however I could understand that I have to trigger the event loop to reflect all the states. but for that an interval of 1 should be enough
[10:30] <mzanetti> greyback: the fact that an interval of 100 works around it, makes it even more scary imo
[10:31] <greyback> mzanetti: sure, I'm not saying it's the right thing to do, there's just some subtle timing issue cropping up
[10:32] <mzanetti> greyback: so you'd vote for going with an interval of 100 for now and hoping this will just vanish when we use real surfaces instead of screenshots?
[10:32] <mzanetti> (well, I'm sure this particular isse would go away using real surfaces...)
[10:34] <greyback> mzanetti: am wondering if it's due to the 2 separate event loops, one for Mir and one for Qt. Calling ApplicationManager.focusApplication causes Mir to immediately switch focus. But Qt hasn't yet generated a frame, that Mir composites, where the screenshots are visible
[10:34] <mzanetti> greyback: ahhh... yeah that would make sense
[10:34] <mzanetti> so Qt's event loop is actually done, but the results not yet processed by Mir's event loop
[10:35] <mzanetti> yeah, that would explain this behavior
[10:35] <mzanetti> and also this sounds like a thing we'd run into more often as more animations are implemented :/
[10:36] <greyback> mzanetti: when we switch to scenegraph, this won't be an issue, as there only 1 event loop will be managing all drawing
[10:36] <mzanetti> +1 for that
[10:36] <mzanetti> so it does sound indeed like I should go with the increased interval workaround for now
[10:37] <mzanetti> with a big fat FIXME to drop it again once we use the scenegraph stuff
[10:37] <greyback> switching focus at the end of the animation work maybe? Or at a preset stage during the animation?
[10:38] <mzanetti> yeah... I thought about that too... I guess I can do it.
[10:39] <mzanetti> greyback: but I really wanted to understand what's going on... thanks for the explanation.
[10:39] <greyback> mzanetti: you're welcome
[10:49] <nic-doffay> Saviq, who's a good person to talk to about CI issues?
[10:49] <mzanetti> Saviq: hmm... for some reason unity8 doesn't seem to register the notification service any more with ./run. It used to work if I did export `dbus-launch` and ran it in that shell. has there been a change you're aware of?
[10:50] <mzanetti> nic-doffay: what's the issue?
[10:50] <nic-doffay> mzanetti, I'm not sure.
[10:51] <mzanetti> nic-doffay: :) ok... so why do you want to talk to someone about CI then?
[10:52] <nic-doffay> mzanetti, because I think it's an irregular issue.
[10:52] <mzanetti> nic-doffay: any link or something?
[10:52] <nic-doffay> mzanetti, https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/fix-1242647/+merge/197176
[10:52] <nic-doffay> Not sure what's causing the two fails.
[10:53] <mzanetti> nic-doffay: hmm... according to the logs it seems to be a real issue, not some flakyness....
[10:54] <nic-doffay> mzanetti, yeah but I can't pin point what exactly it is...
[10:54] <Saviq> mzanetti, there's no need for dbus-launch any more
[10:54] <Saviq> mzanetti, it takes over the name from notify-osd
[10:54] <mzanetti> right.... you see my problem :P
[10:55] <mzanetti> Saviq: so it seems there is an issue if there is no notify-osd running before?
[10:55] <Saviq> mzanetti, shouldn't be
[10:55] <Saviq> mzanetti, /me tries
[10:55] <mzanetti> so in theory the dbus-launch thing should still work, right?
[10:56] <mzanetti> nic-doffay: building your branches... gimme a minunute
[10:56] <Saviq> mzanetti, yeah it should, works here
[10:56] <mzanetti> hmpf...
[10:57] <Saviq> mzanetti, well, just don't do dbus-launch, it actually stops unity8 from launching here for me
[10:58] <Saviq> mzanetti, and it makes sense, as it will wait for all the services that it expects on the dbus
[10:58] <mzanetti> Saviq: it starts fine here on a new session bus. just doesn't register stuff any more
[10:59] <mzanetti> Saviq: last time I tried it was starting too, but took like half a minute before it gave up connecting to the hud service
[10:59] <mzanetti> now it starts up immediately, but not notifications
[11:00] <Saviq> mzanetti, sounds like something weird in your env, any reason why you still want it under dbus-launch?
[11:00] <mzanetti> Saviq: yeah, s/notify-osd/knotify4/
[11:00] <Saviq> mzanetti, right, and knotify4 does not give up the name when asked politely...
[11:01] <mzanetti> yep
[11:01] <Saviq> mzanetti, kill it, then...
[11:01] <mzanetti> it's respowned by kded4 immediately (which I think is new too)
[11:01] <mzanetti> ok... I guess I can shut down the whole session for a bit
[11:01] <mzanetti> nic-doffay: that AP test fails here too
[11:02] <Saviq> mzanetti, or just switch to unity7 like a good employee ;)
[11:02] <mzanetti> Saviq: yeah... did that for a while. but it really sucks on this screen
[11:02] <Saviq> mzanetti, ah right - good thing is that bregma is working on it this cycle
[11:03] <mzanetti> nic-doffay: can't you reproduce the failure locally?
[11:03] <mzanetti> nic-doffay: http://paste.ubuntu.com/6593603
[11:04] <mzanetti> Saviq: to make up for not using unity on the desktop yet I started dogfooding the phone with the MWC release :D
[11:04] <Saviq> ;)
[11:05] <nic-doffay> mzanetti, I didn't run them locally, I figured the logs would be the same?
[11:05] <mzanetti> nic-doffay: yeah. but definitely easier to change to code and run the test again
[11:45] <mzanetti> Saviq: ok. running unity7 now (it did improve a bit already) but notifications still showing up in the desktop. even if I kill notify-osd
[11:45] <mzanetti> with unity8 latest trunk, doing a fresh ./build -c
[11:45] <Saviq> mzanetti, I was suspecting something's weird with your setup...
[11:47] <Saviq> mzanetti, can you see anything related in the log output?
[11:47] <mzanetti> Saviq: no... all fine in there
[11:49] <Saviq> mzanetti, sounds like you need to start looking into monitoring what happens on dbus
[11:49] <mzanetti> mhm
[11:51] <mzanetti> ok... got it... qtdeclarative5-unity-notifications-plugin was borked
[11:52] <mzanetti> duuude :D you broke the fullscreen notifications completely :D
[11:52] <Saviq> mzanetti, I'm sure I did :P
[11:52] <Saviq> mzanetti, couldn't test them, remember? ;P
[11:54] <mzanetti> noooo. qtcreator doesn't pick up fonts dpi inside unity7
[11:55] <Saviq> mzanetti, ouch
[11:57] <mzanetti> Saviq: can we merge this one now? https://code.launchpad.net/~mzanetti/unity8/lockscreen-default-variable-pinlength/+merge/197848
[11:57] <Saviq> mzanetti, wasn't it merged already?
[11:58] <Saviq> mzanetti, got it, ACK'ed
[11:59] <mzanetti> cheers
[12:07] <Saviq> biab
[12:11] <tsdgeos> dandrader: https://code.launchpad.net/~aacid/unity8/verticalJournalImprovements/+merge/199446
[12:12] <dandrader> tsdgeos, saw it. will wait for the original one to get merged before I review this one
[12:13] <tsdgeos> ok
[12:39] <tsdgeos> dandrader: there?
[12:40] <dandrader> tsdgeos, ?
[12:41] <tsdgeos> dandrader: just pinging ;-)
[12:41] <tsdgeos> dandrader: so i am doing the horizontaljournal
[12:41] <tsdgeos> that shares lots of code with the verticalone
[12:41] <tsdgeos> how would you prefer to review
[12:41] <tsdgeos> in two steps, horizontal journal is a "copy" of the verticla one and then introduce a class which both inherit from
[12:42] <tsdgeos> in one step that introduces both the horizontal journal and the class they both inherit from?
[12:43] <dandrader> tsdgeos, one step
[12:43] <tsdgeos> oki
[13:24]  * greyback having his half day, chat tomorrow
[14:23] <Saviq> kgunn, humm, weren't you supposed to be on holidays already?
[14:23] <kgunn> Saviq: not yet...
[14:23] <kgunn> are you trying to send me a hint :)
[14:24] <Saviq> kgunn, no, not really, but was convinced you were gone :)
[14:24] <kgunn> only mentally
[14:29] <Saviq> kgunn, we doing hangout today?
[14:30] <kgunn> Saviq: yes, let's do hangout...it'll be quick one i think
[14:30] <kgunn> let's do round robin first...then cover off 1/2 announcement + deeper dive on some topics
[14:30] <kgunn> it'll be quick i promise
[14:32] <Saviq> nic-doffay, hangout?
[14:32] <Saviq> Cimi, hangout?
[14:32] <nic-doffay> Saviq, one sec.
[14:59] <Cimi> Saviq, I got stuck.. I'm in now
[15:12] <Cimi> who can test ubuntu-ui-toolkit compilation on qt 5.2?
[15:15] <tsdgeos> dandrader|lunch: https://code.launchpad.net/~aacid/unity8/verticalJournalImprovements/+merge/199446 the parent branch has been aprroved and CI passes
[15:33] <kgunn> Cimi: i think you missed the part where we discussed some manual autopilot testing to dry run /pre-test side stage re-enabling
[15:34] <kgunn> Cimi: i'm putting together a list to divide that effort amongst the team...just didn't want to confuse you :) since some items got assigned to you
[15:34] <kgunn> Cimi: if you have questions feel free to hit me up
[16:02] <sil2100> Saviq: hi! You have a mako/maguro, right?
[16:07] <sil2100> Damn, what's wrong with my mako
[16:15] <tsdgeos> Saviq: i don't understand why you have columns for with and without sidestage
[16:21] <Saviq> sil2100, yes, I only don't have grouper
[16:22] <Saviq> tsdgeos, for comparison
[16:22] <tsdgeos> Saviq: but don't we have the official numbers for that?
[16:22] <Saviq> tsdgeos, in case there are failures, we need to know whether it's regressed or not
[16:22] <Saviq> tsdgeos, not for manta
[16:22] <tsdgeos> right
[16:22] <Saviq> kgunn, right ↑↑ we don't need "without sidestage" for mako/maguro
[16:23] <Saviq> kgunn, we have "official" results for that
[16:23] <kgunn> Saviq: yeah...you're right
[16:23] <kgunn> thanks....
[16:23] <Saviq> kgunn, tsdgeos done - two columns less
[16:23] <kgunn> that'll save some time
[16:24] <sil2100> Saviq: hmm... since I am using 'almost-latest-trunk' and I can't run all the tests, suddenly after some tests unity8 goes black and unresponsive
[16:24] <sil2100> Saviq: that happens relatively often
[16:24] <sil2100> Saviq: but it might be my device...
[16:24] <Saviq> sil2100, "black and unresponsive"?
[16:24] <Saviq> sil2100, as in you see it or not at all?
[16:25] <Saviq> sil2100, check if apport's not collecting .crashes for it maybe
[16:25] <kgunn> Saviq: tsdgeos ...just added one note...if you do get a failure on mako w/ sidestage...might want to back it out and retest the image
[16:25] <kgunn> but only in case of failure
[16:25] <Saviq> kgunn, yup
[16:25] <sil2100> Saviq: I see a black screen - no backlight, tests not moving - after pressing the power button first the backlight appears and after a few lazy seconds I see unity8 appearing
[16:25] <sil2100> But tests don't move forward
[16:26] <sil2100> Saviq: you guys didn't see symptoms like this, right?
[16:26] <Saviq> sil2100, no
[16:26] <sil2100> Let me try downgrading and seeing if I get the same, since as I said, I stopped trusting my device
[16:27] <Saviq> kgunn, I made the branch "needs review" to get packages out of CI
[16:27] <Saviq> kgunn, so that we don't have to build them ourselves
[16:28] <kgunn> Saviq: another excellent idea
[16:33] <Saviq> tsdgeos, how do you tell qt to not build qtwayland?
[16:34] <tsdgeos> Saviq: don't know :D
[16:34] <tsdgeos> never built it for me :D
[16:34] <Saviq> lol
[16:34] <tsdgeos> you're building the supercheckout thing?
[16:35] <Saviq> tsdgeos, ah, qt.pro should do ;)
[16:35] <Saviq> tsdgeos, yeah
[16:35] <tsdgeos> Saviq: ok, i just build the modules one by one
[17:25] <Saviq> dandrader, I take that back, indeed it seems like release fixes - and yeah am getting testApplication failure
[17:25] <Saviq> dandrader, I'll do some bisecting, then
[17:28] <dandrader> Saviq, reported a qt bug on the testApplication failure, btw
[17:28] <Saviq> dandrader, cheers
[17:31] <Saviq> dandrader, which QTBUG? make sure Mirv knows about it, please
[17:32] <dandrader> Saviq, I wrote about it on https://bugs.launchpad.net/bugs/1258057
[17:32] <Saviq> dandrader, ah great thanks
[17:33] <dandrader> Saviq, but, discussing it on qt-quick, that question made me scratch my head "<jpnurmi> aalpert-thoth: is importing singletons to a "global" namespace a supported use case?"
[17:33] <mhall119> Saviq: do we have a PPA that will let me build Unity 8 on Saucy yet/
[17:33] <mhall119> ?
[17:34] <Saviq> mhall119, there is a ppa, not one that will let you build unity8 on saucy I'm afraid, folks are looking into it, though
[17:34] <mhall119> ok
[17:34] <Saviq> mhall119, i.e. unity-scopes-api fails to build on saucy: https://launchpad.net/~phablet-team/+archive/desktop-deps/
[17:35] <Saviq> dandrader, yeah, it shouldn't be asked ;)
[17:35] <Saviq> dandrader, like WTH not?
[17:54] <dednick> mhr3_: ping
[18:13] <dednick> hm. so can't play videos on tablet yet?
[18:29] <kgunn> Saviq: is there something i'm doing wrong? ....i can't seem to download output.zip from them mp ?
[18:29] <kgunn> i'm on vpn
[18:31] <Saviq> kgunn, trying
[18:31] <Saviq> kgunn, the job failed to publish
[18:31] <kgunn> how does one come to know that ?
[18:32] <Saviq> kgunn, http://s-jenkins.ubuntu-ci:8080/job/unity-mir-trusty-armhf-ci/48/artifact/work/output/*zip*/output.zip
[18:32] <Saviq> kgunn, jenkins.qa.ubuntu.com is only a public frontend - it doesn't execute any jobs
[18:32] <kgunn> thanks...
[18:32] <Saviq> kgunn, the results get published to it by the real jenkins
[18:32] <Saviq> kgunn, but sometimes it fails
[18:33] <Saviq> kgunn, so if you get 404 from jenkins.qa.u.c - that's most probably that
[18:33] <kgunn> damn....jenkins and his evil twin not-so-public jenkins
[18:33] <Saviq> kgunn, published now
[18:34] <Saviq> kgunn, so the MP link works now, too
[18:36] <kgunn> Saviq: i was just antsy i guess
[18:36] <dednick> is anyone able to play a local video on device?
[18:36] <kgunn> dednick: you mean manta/nexus10 right ?
[18:37] <dednick> kgunn: yeah
[18:38] <kgunn> dednick: i don't have a manta...
[18:42] <kgunn> ricmm: ^ should we be able to play video on manta?
[18:42] <kgunn> rsalveti: ^
[18:43] <dednick> hm. I manually installed gstreamer1.0-libav so that mediascanner would pick up videos, but was crashing mediaplayer-app. I removed it and now I'm getting some audio, but no video...
[18:43] <dednick> ....sigh
[18:43] <giuseppe___> hello
[18:44] <giuseppe___> Is it possible for me to inigrate unity api in my distro???
[18:45] <giuseppe___> ???
[19:01] <rsalveti> kgunn: no, there's no video support for manta yet
[19:01] <rsalveti> dednick: ^
[19:09] <dednick> rsalveti: ta
[20:35] <kgunn> hmmm....anyone tried mako yet with sidestage ?
[20:35] <kgunn> going to reflash in case its me
[20:45] <mhall119> Saviq: how can I make an app respond to a user tapping one of the HUD's toolbar icons?
[21:01] <Saviq> mhall119, that's the wrong side of the integration you're asking me for ;)
[21:01] <Saviq> tedg, ↑↑?
[21:01] <tedg> mhall119, Ask a QML guy like Saviq
[21:02] <tedg> ;-)
[21:02] <tedg> I'm not sure of the QML way to do it exactly, but you need a "hud-toolbar-item" property on the Unity Action.
[21:22] <kgunn> ricmm: so i  just took latest trusty image on mako....dumped unity-mir deb in from jenkins build...installed it, but i don't get anything rendered onscreen
[21:23] <kgunn> ricmm: i double checked, even used devel-proposed...same thing
[21:24] <mhall119> tedg: so http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.Action/ needs to be expanded to include a hud-toolbar-item?
[21:24] <kgunn> ricmm: running top i can see unity8 running...and the screen is auto blanking & turning on from power button...but just no rendering
[21:25] <kgunn> ricmm: is this something you would have expected ??
[21:25] <kgunn> or just a bug on mako that needs fixing?
[21:27] <tedg> mhall119, I'm not sure what the property name is exactly, but something like that, yes.
[21:29] <kgunn> ricmm: or...am i doing something wrong ?
[21:36] <mhall119> tedg: is that a DBus property name?
[21:36] <tedg> mhall119, No, gmenu property name.
[21:40] <mhall119> tedg: Saviq: where can I find the source for Ubuntu.Unity.Action.Action?
[21:41] <tedg> mhall119, I think this is it: https://launchpad.net/unity-action-api
[21:42] <ricmm> kgunn: not sure, my mako is charging right now for that matter
[21:42] <ricmm> I havent tested it yet
[21:46] <mhall119> well, over my head
[21:46] <mhall119> tedg: Saviq: do either of you know of plans to make this possible via QML, and who's behind it?
[21:48] <tedg> mhall119, The action-api was done by Wellark_, he'd probably have more ideas there.
[21:49] <kgunn> ricmm: curious what you find....i'm reflashing & going to build natively...
[21:49] <kgunn> just in case
[21:50] <mhall119> Wellark_: ping about unity-action-api, QML and HUD toolbuttons