[14:35] <taiebot> Hi all, Was wondering if the crashof unity-8  when closing apps on vivid Ubuntu-touch was likely to be fixed.  I believe it must have been fixed upstream but it's quite frustrating to see unity 8 reboot quite often on the phone. i am asking that because if there is no plan for the foreseeable future i might finally switch to the droid.
[14:36] <taiebot> BTW the crash happens more easily with the browser app and a video running.
[14:48] <Saviq> taiebot, I'm afraid not, we've stopped doing any work on vivid, other than any critical security updates
[14:48] <Saviq> sorry I don't have better news
[14:49] <taiebot> saviq: it's ok my phone is old (still using Nexus 4) i feel more for all the developers. So much work went into those phones.
[19:24] <dandrader> tedg, in Manager::focusRequest, why do you need an answer?
[19:27] <tedg> dandrader: We don't yet, but eventually we'll allow unity to reject it.
[19:27] <tedg> I imagine some sort of focus mode or something.
[19:27] <dandrader> tedg, and what would be the difference in UAL's perpective if shell accepted or rejected? focus is a concept that lives inside shell
[19:28] <tedg> dandrader: We're return error to the caller.
[19:28] <tedg> We'd
[19:28] <tedg> dandrader: So that happen on launch() if the app is already running.
[19:28] <tedg> happens...wow.
[19:29]  * tedg checks if Google translate can help here
[19:29] <dandrader> ?
[19:29] <tedg> Bad Typer -> English
[19:30] <tedg> I really think XMir is dropping keystrokes, but I can't really prove it isn't me.
[19:30] <dandrader> oh, you're really dogfooding :)
[19:31] <tedg> Haha, I've used Unity8 for months :-)
[19:31] <tedg> Somedays are better than others.
[19:31] <tedg> Having the shadow on the windows back today is really awesome though. Missed that.
[19:37] <dandrader> tedg, I think it's really odd to get the reponse to a focus request thorugh ual. the real response will be received when the applications' mir window receives focus
[19:37] <dandrader> *through
[19:38] <tedg> dandrader: Sure, but this case isn't an app requesting. It's like someone sending a URL to URL Dispatcher and getting an error there.
[19:38] <tedg> dandrader: Apps themselves don't use UAL.
[19:38] <dandrader> hmm
[19:38] <tedg> Different kind of focus request really. It's a "change application" request by the system.
[19:39] <boiko> hi guys, is this autopkg test failure known or is it something new: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-2629/xenial/i386/u/unity8/20170403_185700_c0929@/log.gz ?
[19:43] <dandrader> tedg, any side-effects on Manager::resumeRequest response?
[19:44] <dandrader> tedg, it will only resume when shell calss Instance::resume anyway, right?
[19:44] <dandrader> *calls
[19:44] <tedg> dandrader: So right now the code will just assume Unity doesn't know what it's talking about and timeout. But the goal is to make it so that Unity8 controls those items.
[19:44] <tedg> dandrader: I would say that you should return true unless you have a reason to object, and then we'll start making it more powerful.
[19:45] <dandrader> tedg, but an instance only gets resumed when untiy8 calls Instance::resume(), right?
[19:46] <tedg> dandrader: In practice yes, though there's no technical limitation on who could call that.
[19:46] <dandrader> tedg, what I mean is that returning true on Manager::resumeRequest won't by itself cause an instance to be resumed, right?
[19:50] <tedg> dandrader: Corret
[19:50] <tedg> Correct
[19:50] <tedg> Okay, now I am tryng to type slow. Nope still missed a couple characters.