[06:31] <Mirv> Saviq: forgot to answer, but no I'm not allowed to land it before all bugs are fixed and QA verified. the silo is preparation only so the components in there are not really locked.
[06:37] <Saviq> Mirv, ok thanks
[06:38] <Saviq> mzanetti, another one (or is it the same?) bug #1323347
[06:39] <Mirv> Saviq: the biggest problems currently are media playback, and the crashers.. I think unity8 is crashing too occasionally for some reason.
[06:39] <Saviq> Mirv, mhm
[06:41] <mzanetti> Saviq: the stack trace doesn't really tell me anything
[06:42] <Saviq> mzanetti, yeah I know, but did you land the one you thought would fix things?
[06:42] <mzanetti> Saviq: is it landed yet?
[06:42] <Saviq> mzanetti, where was it?
[06:42]  * mzanetti searches
[06:43] <mzanetti> Saviq: https://code.launchpad.net/~mzanetti/unity8/dont-crash-on-invalid-app/+merge/220636
[06:43] <Saviq> mzanetti, yup, just found it
[06:44] <mzanetti> Saviq: in any case, if this really fixes those crashes, we have a weird problem in ApplicationManager :/
[06:44] <Saviq> mzanetti, mhm
[06:56] <Saviq> mzanetti, could I ask you to prepare a silo with the MP queue we have ACKed for unity8
[06:56] <mhr3> tsdgeos, in meeting?
[06:56] <mzanetti> Saviq: sure
[06:57] <Saviq> mhr3, yeah, we're in Studio 1 with Mark and Jane talking over the dash
[06:57] <mhr3> k
[06:59] <mzanetti> Saviq: including? lp:~mterry/unity8/split
[07:00] <mterry> mzanetti, not that one, there will be conflicts
[07:00] <mzanetti> ok
[07:00] <mterry> mzanetti, I'll need to re-merge and have a separate silo landing
[07:00] <mzanetti> yup. that's what I thought. Doesn't sound like one to be just released in a pile of others
[07:13] <mzanetti> tsdgeos: can you confirm that the scopeview test failure in here is not caused by this branch? https://code.launchpad.net/~aacid/unity8/organiccgridcrash/+merge/220651
[07:31] <tsdgeos> mzanetti: yeah that should be fixed elsewhere
[07:31] <mzanetti> ack
[07:31] <tsdgeos> mzanetti: and organicgrid isn't even used yet in the qml :D
[07:32] <tsdgeos> mhr3: what you need?
[07:32] <mzanetti> how should I know :P
[07:32] <mhr3> tsdgeos, wanted to ask about the null vs "" thing in js
[07:32] <mhr3> tsdgeos, are we going to use it?
[07:32] <mhr3> tsdgeos, fwiw qt docs don't recommend differentiating the two
[07:33] <tsdgeos> mhr3: in qstring or in js?
[07:33] <mhr3> tsdgeos, qstring
[07:33] <tsdgeos> ok
[07:36] <tsdgeos> mhr3: i don't really care to be honest, if you prefer the bool, let's go with it
[07:37] <mhr3> tsdgeos, ok, bool it is
[07:38] <mhr3> tsdgeos, and another question i had, what's the order of operations when you activate a subdep?
[07:38] <mhr3> tsdgeos, get(), load(), get()?
[07:39] <tsdgeos> mhr3: can you add the bool to the pad?
[07:39] <mhr3> sure
[07:39] <tsdgeos> mhr3: honestly, the order is "random"
[07:39] <tsdgeos> mhr3: it's qml declarative stuff after all
[07:39] <tsdgeos> can't really "serialize" it easily
[07:39] <tsdgeos> is that a problem for you?
[07:40] <mhr3> tsdgeos, hm, shouldn't be, just wanted to make tests do things as closely as possible to what dash would do
[07:41] <tsdgeos> mhr3: so my understanding, i'll do load, then currentDepartment will change and i'll go a get
[07:47] <Saviq> vila, hey, meet mzanetti, he's got the MBP with nvidia turned off
[07:47] <Saviq> vila, and bug #1292830
[07:49] <vila> Saviq: ack, the switch VTs trick did work for me twice already, I subscribe to the bug
[07:49] <tsdgeos> mhr3: added a comment to the pad about the properties vs loaded
[07:50] <vila> mzanetti: where are you ?
[07:50] <mhr3> tsdgeos, ack
[07:50] <vila> mzanetti: and when do you have a few minutes to compare configs ? (I have a MBAir ~2nd gen)
[07:51] <mzanetti> vila: sure
[07:51] <mzanetti> vila: I'm in ballroom 2b atm
[07:51] <vila> mzanetti: coming to you ;)
[07:51] <mzanetti> ok
[07:52] <Cimi> tedg, what's the status of GPS/location system settings properties?
[07:54] <Saviq> mterry, "start on unity8-greeter-started" looks wrong?
[07:54] <Saviq> mterry, shouldn't it be "start on started unity8-greeter"?
[07:54] <mterry> Saviq, well...  unity8-greeter isn't a real job.  But it emits some "job like signals" -- namely starting and started -- so that other jobs can listen if they want (like welcome wizard)
[07:55] <tedg> Cimi, We're waiting on platform api changes, which are waiting on location service changes.
[07:55] <Saviq> mterry, ok got it
[07:55] <tedg> Cimi, Basically not useful until all of that lands.
[07:55] <mterry> Saviq, I chose to make them namespaced rather then emitting "start JOB=unity8-greeter" since I didn't want to make people think it was a real thing
[07:55] <Saviq> mterry, understood
[09:50] <mhr3> tsdgeos, getting close to having something testable, can we try the two branches together? (after lunch)
[11:06] <dpm> Hi Saviq, Wellark, do you happen to know where the CANCEL and DONE texts from the Unlock SIM dialog come from? I can't find them up for translation anywhere, but I'm not too sure which project to look at
[11:33] <luv> ChrisTownsend: hey, just curious - what's the progress on https://bugs.launchpad.net/compiz/+bug/1063617 ? Is it going to 14.04 ?
[11:33] <sil2100> pstolowski: hey
[11:33] <sil2100> pstolowski: so, we checked and see that there is something like dh_click, provided by click-dev
[11:34] <ChrisTownsend> luv: Yeah, we plan on getting it in 14.04 as an SRU, but the SRU process can take some time to complete.
[11:34] <pstolowski> sil2100, ok,and why is this failing sometimes?
[11:40] <sil2100> pstolowski: this is a good question - I guess it might be what you said that some nodes have it installed for some reasons and some might not, sadly I have no tools of checking that
[11:40] <sil2100> Oh, he's gone
[11:57] <dednick> mardy: hi
[11:58] <mardy> dednick: hi! Are you in Malta? :-)
[11:58] <dednick> mardy: yes, you?
[11:58] <mardy> dednick: nope, I was there last week
[11:59] <dednick> mardy: ah. ok, that might have helped if we were at the same time :)
[11:59] <dednick> mardy: There really is no way to get the mir connection from a qt app as I see it. Even if we used something like QPlatformNativeInterface::nativeResourceForIntegration, We would still only be accessing the platform-api abstraction.
[11:59] <dednick> mardy: And anyway, as I said, you cannot add a process by PID for a process which contains 2 mir connections.
[11:59] <dednick> *add a session
[12:00] <dednick> because we need to uniquely identify the session which we want to add to the trust session.
[12:00] <mardy> dednick: well, if we were able to get the mir connection, we wouldn't have 2 mir connections (we wouldn't create a second connection, but use the one from QGuiApplication to create the trusted session)
[12:01] <dednick> mardy: ok.
[12:03] <dednick> mardy: so what happens if 2 dbus requests come in for a trust session?
[12:03] <dednick> mardy: thinking ahead of time here
[12:04] <dednick> mardy: presumably you only have one process running for the online accounts daemon.
[12:04] <mardy> dednick: yes, it's a single process
[12:05] <mardy> dednick: since we can't have more than one trusted session at a time, I think we'd have to return an error
[12:05] <dednick> mardy: it's only one at a time for now.
[12:06] <dednick> mardy: we've just limited it for first phase. Not sure if you're doing the same.
[12:07] <mardy> dednick: at the moment we create a new QWindow for each request, but without trusted session support these look like "rogue" window, they are not made transient to the application which requested them
[12:07] <dednick> ok. so one app with multiple windows. hm.
[12:07] <dednick> i dont think thats supported in mir at the moment.
[12:07] <mardy> dednick: when we implement phase 1 of the trusted session, we'll accept the limitation of 1 window at a time
[12:08] <mardy> dednick: it seems to work :-)
[12:09] <dednick> mardy: in mir?
[12:09] <dednick> seeing 2 windows at once?
[12:09] <mardy> dednick: I admit that I didn't try making more than one request at the same time lately, but IIRC it was working at some time
[12:10] <dednick> hm. ok. i've never seen a multiple surface app working  before.
[12:10] <mardy> dednick: anyway, for the time being we are fine with the limitation
[12:11] <mardy> dednick: but I guess that eventually you'll have to support the case of one process having more than one window, if not for the desktop
[12:12] <dednick> mardy: let me talk to mir people. might be able to use a pre-created connection for a qt app.
[12:18] <Saviq> dpm, did you get a reply on the SIM screen translation?
[12:18] <Saviq> dpm, it's in unity8
[12:18] <tsdgeos> mhr3: https://code.launchpad.net/~aacid/unity8/departments
[12:18] <mhr3> tsdgeos, it should work with the scope-tool, right?
[12:19] <tsdgeos> mhr3: i hope so ^_^
[12:22] <tsdgeos> mhr3: want me to drop over
[12:22] <tsdgeos> ?
[12:22] <mhr3> tsdgeos, i'm coming :)
[12:23] <tsdgeos> ok, so didn't work :/
[12:24] <mhr3> tsdgeos, lp:~mhr3/unity-scopes-shell/department-support
[12:26] <dednick> mardy: how much work would it be to split dbus & gui processes? I'm not sure we're going to get another solution in time.
[12:29] <mardy> dednick: a lot, I'm afraid there might be no time for that either
[12:29] <mardy> dednick: it's risky, but not impossible
[12:30] <Cimi> Saviq, is the suru switch in a silo?
[12:30] <dednick> mardy: what is actually done over dbus? just the initiation of the UI?
[12:32] <mardy> dednick: mainly that, but the problem is that it's not a fire-and-forget thing, the two parts need to communicate to each other
[12:34] <dednick> mardy: what project is it in?
[12:34] <Saviq> Cimi, 006
[12:34] <Cimi> Saviq, thx
[12:35] <Saviq> Cimi, dednick, so, I did https://code.launchpad.net/~unity-team/ubuntu-settings-components/suru-theme/+merge/220739
[12:35] <Cimi> Saviq, yeah was reviewing that indeed
[12:35] <Saviq> Cimi, dednick, and https://code.launchpad.net/~unity-team/unity8/suru-switch/+merge/207991 has an abuse of the Event component
[12:36] <Saviq> Cimi, dednick, we could rename that component or maybe "fork" the Standard one
[12:36] <dednick> mardy: problem is that I don't think platform-api will ever give us direct access to a mir connection. Might have to actually create trust session apis in platform-api and then somehow call that from qt api.
[12:37] <dednick> Saviq: standard=event?
[12:38] <Saviq> dednick, well, event is just label + optional colorized icon and secondary label
[12:38] <Saviq> dednick, so we could just make it what it is
[12:38] <Saviq> s/make/name/
[12:38] <mardy> dednick: sorry, I missed your previous message. So, this is the latest code http://bazaar.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/signon-ui/files
[12:38] <mardy> dednick: look under src/main.cpp
[12:39] <dednick> Saviq: ok. can rename.
[12:40] <Saviq> dednick, if you do it - same branch? (it's under ~unity-team)
[12:40] <dednick> Saviq: ok. thanks
[12:41] <dednick> mardy: ok, i'll have a look in a bit.
[12:43] <mzanetti> Wellark: ping
[12:46] <dednick> Saviq: why did you change it from ListItem.Standard? The EventMenu is not really a "standard" one. I think i did it because the ListItem.Standard doesn't support icon colouring.
[12:47] <dednick> Saviq: in which case the settings-ui wont colour them
[12:47] <Saviq> dpm, PinLockscreen.qml in unity8
[12:48] <dednick> Saviq: technically, the event item should be a ListItem.Standard with a control: Label {}
[12:48] <Saviq> dednick, icon size
[12:49] <dednick> Saviq: does that not need fixing in ListItem.Standard as well?
[12:49] <Saviq> dednick, well that's what we discussed with Mathieu today
[12:49] <Saviq> dednick, but no outcome yet
[12:49] <dednick> Saviq: ok
[12:50] <Saviq> dednick, I didn't put a lot of thought into what I did, I just wanted to get it as close as possible
[12:50] <Saviq> dednick, with as little work as possible
[12:50] <Saviq> dednick, so if you have a better approach - by all means!
[12:53] <Wellark> mzanetti: pong
[12:54] <Cimi> Saviq, testing, looks fine
[12:55] <Cimi> Saviq, what was the icon in the indicator that needed the ubuntushape border to be removed?
[12:55] <Saviq> Cimi, not indicator
[12:55] <Saviq> Cimi, settings app
[12:56] <Cimi> ah right
[12:56] <Saviq> Cimi, in language - same issue ListItem.Standard vs. Event
[12:56] <Saviq> Cimi, http://people.canonical.com/~msawicz/unity8/suru-shots/
[12:57] <Wellark> Saviq: what about PinLockscreen.qml ?
[12:57] <Mirv> mourning shots
[12:57] <Wellark> are you modifying it?
[12:57] <Saviq> Wellark, just i18n.tr
[12:58] <Saviq> Wellark, we could add it to mzanetti's branch but it's landing already
[12:58] <Wellark> Saviq: hmm.. is there any strings in that?
[12:58] <Wellark> afaik there should not be.
[12:59] <Saviq> Wellark, "CANCEL", "DONE"
[12:59] <Wellark> Saviq: oh, right..
[13:05] <Wellark> Saviq: so, the mzanetti lockscreen work is landing currently?
[13:05] <Saviq> dpm, https://code.launchpad.net/~saviq/unity8/make-lockscreen-translatable/+merge/221084 - please let me know if you find more that we didn't...
[13:06] <Wellark> dpm: btw, due to unfortunate historical reasons the "Please Enter SIM PIN" that you see on the sim unlock dialog is currently hardcoded string in the unity8 tree
[13:06] <Saviq> Wellark, yes
[13:07] <Wellark> so, if there is an expo coming, just make sure nobody is getting to the PUK entry stage :)
[13:21] <elopio> mzanetti: do you have time to help me?
[13:23] <Saviq> elopio, maybe I can?
[13:24] <mhr3> tsdgeos, there's something weird in the model, i'm getting the issue as well in unit tests
[13:24] <tsdgeos> mhr3: ah, "good" i guess :D
[13:24] <mhr3> good for you anyway :)
[13:27] <mhr3> woo, fixed
[13:28] <tsdgeos> :)
[13:28] <dednick> Saviq: how do i run with the suru theme?
[13:30] <dednick> Saviq: nevermind
[14:26] <mzanetti> elopio: hey, yes, I would. are you around?
[14:39] <dpm> thanks Saviq for the translations update. Wellark, we must be using another string, then, as the prompt to enter the SIM PIN does appear translated to me. Only Cancel and Done were not translated
[14:46] <Cimi> Trevinho, https://twitter.com/honestburgers/status/471298858363142144/photo/1
[14:47] <Trevinho> Cimi: :-Q_____
[15:13] <mhr3> Saviq, in meetings? with albert?
[15:29] <elopio> mzanetti: Saviq already helped me.
[15:29] <elopio> I was doing something stupid, not addig the anchors to the component.
[15:29] <mzanetti> ah ok... sorry for missing your ping before
[15:29] <mzanetti> elopio: ^
[15:29] <elopio> mzanetti: I'll look for you or him when I get blocked again.