[08:03] <alan_g> RAOF: Did I answer your "Needs Info"? https://code.launchpad.net/~alan-griffiths/mir/placement-notification/+merge/305599
[08:06] <duflu> alan_g: Just a bit past his EOD
[08:06] <alan_g> Oh well...
[08:08] <alan_g> duflu: you picked up the crash releasing egl resources. You have an idea what's broken?
[08:08] <duflu> alan_g: Only started on it 15 seconds ago. Will comment soon if at all
[08:09] <duflu> Feels familiar but not sure why
[08:09]  * alan_g wants it NOW!! ;)
[08:09] <RAOF> Oh, I didn't respond to that.
[08:24] <duflu> Launchpad times out and becomes unusable
[08:24] <duflu> Must be morning in Europe
[08:25] <duflu> alan_g: I can't update bugs right now as LP times out. But it's just another Mesa 12.0.2 regression. 12.0.1 works
[08:26] <alan_g> duflu: I suspected as much, thanks
[08:26] <duflu> No problem. I still had the old debs handy from the other regression
[08:27] <duflu> alan_g: If LP works for you please just duplicate to https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1620994
[08:27] <ubot5> Ubuntu bug 1620994 in mesa (Ubuntu) "EGL clients with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate)" [Undecided,New]
[08:29] <alan_g> duflu: timing out just now. Will try again later
[08:29]  * duflu is glad that's not a geographical failure
[08:50] <duflu> Saviq: Are you confident it's just Mir missing a rebuild against protobuf3? https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1621746
[08:50] <ubot5> Ubuntu bug 1621746 in mir (Ubuntu) "Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)" [Critical,Confirmed]
[08:51] <Saviq> duflu, I just meant that was a requirement, didn't know whether it was enough
[08:52] <duflu> Saviq: OK well I believe alan_g already released the protobuf fix that we were waiting on
[08:52] <duflu> Just need the powers that be to rebuild
[08:52] <duflu> Who/wherever they are
[08:54] <alan_g> Saviq: duflu I gave doko a patchfile. AFAIK everything was fine after that
[08:54] <duflu> alan_g: It got released a while ago according to distro
[08:55] <duflu> Umm a weekago it hit proposed I mean: https://launchpad.net/ubuntu/+source/protobuf
[08:55] <duflu> Not sure *which* fix that was
[08:56] <duflu> It's a miracle. I have time to work on Xmir too
[08:56] <Saviq> duflu, it was the protobuf rebuild fix, that's in proposed for sure
[08:57] <duflu> Oh, cool
[08:57] <Saviq> 'cause we couldn't build u-s-c before
[08:57] <Saviq> now we could
[08:57] <duflu> That might be it
[13:20] <alan_g> greyback_: Did I answer your "Needs Info"? https://code.launchpad.net/~alan-griffiths/mir/placement-notification/+merge/305599
[13:22] <greyback_> alan_g: yep, no objection here
[13:22] <alan_g> kdub: can you explain what you're asking? https://code.launchpad.net/~alan-griffiths/mir/placement-notification/+merge/305599/comments/790524
[13:22] <greyback_> alan_g: "alam@octopull.co.uk" <- typo in your commit message email - in case you've it set up somewhere
[13:23] <alan_g> greyback_: Oops
[13:24] <alan_g> Thanks
[13:28] <kdub> alan_g, with the second part,  I didn't see why we had to have the reference that header from the top-level directory
[13:28] <kdub> and for the 1st part, that explanation makes sense, but wasn't obvious to me from reading the headers (as my guess was incorrect)
[13:29] <NotKit> are there any specific hacks needed for hwcomposer on PowerVR MediaTek devices?
[13:30] <alan_g> kdub: so the first part is answered by -r 3706?
[13:30] <kdub> alan_g, sure
[13:31] <alan_g> For the second part, that's consistent with what we do elsewhere.
[13:32] <kdub> well, why is it needed? (might find out for myself in a minute, compiling now)
[13:35] <alan_g> A lot of IDEs (including CLion that RAOF and I use) like project headers to be mentioned in the CMakeLists.txt files. We've been adding them for the last year or so.
[13:36] <NotKit> http://pastebin.com/deuQ3VEC - logcat
[13:37] <kdub> alan_g, ah, news to me
[13:38] <kdub> alan_g, alright, lgtm then
[13:38] <alan_g> kdub: RAOF and I thought no-one would even notice, so we didn't tell anyone.
[13:40] <kdub> alan_g, yeah, I don't mind as long as it has some purpose
[13:40] <alan_g> I *think* qtcreator likes it too, but it has been too long since I started it up to be sure
[13:41] <kdub> I'm still laboring under vim
[13:41] <alan_g> I use that a fair bit too
[13:42] <alan_g> But it is really nice to have a key-combo to build and run/debug just the test you're editing
[13:43] <kdub> yes, that does sound handy
[13:45] <alan_g> There's a lot of "understanding the language" stuff it makes easy. (A lot of textual manipulation stuff sends me back to vim)
[13:47] <kdub> yeah, will give it a try
[13:47] <kdub> there's only so many vim scripts one wants to write
[13:58] <anpok> did notice .. and thought - oh so visual studio isnt the only ide that needs that..
[14:03] <alan_g> attente: do you want to discuss further? Or shall we land this version? https://code.launchpad.net/~alan-griffiths/mir/placement-notification/+merge/305599
[14:05] <attente> alan_g: yeah. sorry, i didn't see the follow up
[14:44] <alan_g> attente: are you content with the current proposal?
[14:45] <attente> alan_g: how amenable is it to change? i still want the extra intermediate rectangle, so it would only be an api addition from here
[14:47] <alan_g> attente: adding another rectangle (and query for it) wouldn't break ABI. But I don't know what to put in it.
[14:47] <alan_g> So I guess we can land and discuss further
[14:49] <attente> alan_g: sounds reasonable, thanks. if you land it, i'll see if it's sufficient enough for gtk to infer the information it needs
[14:52] <alan_g> attente: OK. Meantime I can start adding in the "anchor to surface" constraints.
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader
=== dandrader_ is now known as dandrader
=== dandrader is now known as dandrader|afk
=== dandrader|afk is now known as dandrader