[08:56] <alan_g> greyback: do you know the intended usage of mir/shell/persistent_surface_store.h? Or is that something for dandrader?
[08:59] <greyback> alan_g: not exactly. I see it claims to enable surface position/size persistence across session lifetimes, so WM would find it handy
[09:00] <alan_g> Note "todo Persistence across shell restarts is as-yet unimplemented."
[09:01] <greyback> yeah. "claims" :)
[09:01] <greyback> we're not using it in qtmir/unity8
[09:02] <alan_g> Yeah, the server APIs are only published in Mir-0.24
[09:03] <alan_g> So I'm a bit short of clues on what MiraAL should expose
[09:05] <alan_g> IIRC the current intended usage is for identifying "foreign" surfaces for WM
[09:08] <RAOF> alan_g: That was a happy accident.
[09:09] <RAOF> Or, rather, a happy repurposing. It's intended to be the identifier that you use for persistence across restarts, indeed.
[09:10] <RAOF> Since nothing's using it currently it's not something that'd be interesting to expose from MirAL ATM, and it might not want to be exposed at all (it seems to be something that MirAL could reasonably hide and just DTRT with)
[09:12] <alan_g> RAOF: As dandrader published the headers I assume that he has plans to use them. (I'd be good with DTRT)
[09:13] <alan_g> So you see no reason to land any version of https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/302408?
[09:14] <RAOF> I think you're correct, and WindowManagerTools::window_for_id() is likely to be the winner.
[09:20] <RAOF> (Commented on the branch)
[09:20] <alan_g> thanks
[11:22] <greyback> alan_g: sorry, it is a bit of a monster, I'm unsure how I can break it up into more manageable chunks: https://code.launchpad.net/~gerboland/miral/add-interactivity-to-WM/+merge/302531
[11:23] <alan_g> greyback: I understand the reasons.
[13:11] <oSoMoN> does Mir have support for client-side decorations?
[13:14] <alan_g> oSoMoN: no
[13:15] <oSoMoN> alan_g, thanks. Are there any plans to support them in the future?
[13:17] <alan_g> oSoMoN: bug 1398849 has probably the latest info
[13:23] <oSoMoN> thanks!
[13:51] <alan_g> dandrader: do you agree with the last comment? https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/302408
[13:52]  * dandrader checks
[13:59] <dandrader> alan_g, not familiar enough with miral context to give any useful opinion right now...
[14:01] <alan_g> dandrader|afk: the basic question is whether we currently expect shells to want more than identifying a surface from an id
[14:25] <dandrader> alan_g, any usecase in mind?
[14:26] <alan_g> Oh. I thought you were the one that "published" the PSS headers in Mir. My mistake.
[14:28] <alan_g> dednick: do you agree with the last comment? https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/302408
[14:29] <dednick> alan_g: looking
[14:32] <dednick> alan_g: we need id_for_surface, so unless there's another way getting it...
[14:33] <dednick> alan_g: i added that functionality in mir http://bazaar.launchpad.net/~mir-team/mir/development-branch/revision/3553
[14:34] <dednick> for the application menus
[14:34] <alan_g> dednick: presently not exposed through miral. What's the usecase?
[14:35] <dednick> alan_g: application menus are exposed through dbus using persistent surface id. unity8 need to get the surface for those published ids.
[14:36] <alan_g> That's "surface_for_id" not "id_for_surface"
[14:37] <dednick> alan_g: no, unity8 gets the ids from dbus. need to get the surfaces for those ids.
[14:38] <alan_g> @"<dednick> alan_g: we need id_for_surface," do you have a usecase for id_for_surface()?
[14:40] <jounih_> hi, I’m trying to run Unity8 on 16.04 in VMWare but getting a black screen after starting the unity8 session from the greeter. Any ideas?
[14:40] <dednick> alan_g: huh?
[14:40] <dednick> alan_g: i just gave you the use case for id_for_surface(). unity8 has the ids, but needs to get the surface. so uses "Id PersistentSurfaceStore::id_for_surface(std::shared_ptr<mir::scene::Surface> const& surface)
[14:41] <alan_g> to get the surface you call "surface_for_id(the_id)" and get a surface
[14:42] <dednick> alan_g: lol. of course you do! sorry. apparently my brain isnt working
[14:42] <alan_g> jounih_: probably a problem with the VMware drivers
[14:42] <jounih_> Is there a way to get it working?
[14:42] <dednick> alan_g: in that case, no, there is no current usecase for id_for_surface
[14:42] <jounih_> it’s the latest version of VMWare and instructions for installing Unity8 from here - http://mhall119.com/2016/05/dogfooding-unity-8/
[14:43] <dednick> alan_g: in the server. only in the client
[14:43] <jounih_> I can put logs on gist if anyone wants to have a look?
[14:44] <jounih_> https://gist.github.com/jounih/96cae2256280f298dfb3f27f922d04c2
[14:44] <alan_g> jounih_: https://bugs.launchpad.net/mir/+filebug
[14:44] <greyback> jounih_: it's crashing, someone needs to investigate why
[14:49] <jounih_> ok I filed a bug
[14:49] <jounih_> https://bugs.launchpad.net/mir/+bug/1611804
[14:55] <alan_g> jounih_: thanks!
[15:24] <mhall119> jounih_: give willcooke a ping, we talked to him yesterday about having a vm or live iso for testing unity 8 and he was going to look into that
[15:24] <jounih_> I did, he is here
[15:24] <jounih_> he pointed me to bregma who pointed me here
[15:27] <bregma> jounih_, did you ever check for a unity8 crash log in /var/crash in your VM?
[15:30] <jounih_> not yet, i’ll atttach those to the bug now
[16:00] <greyback> bregma: fyi: https://bugs.launchpad.net/mir/+bug/1611804/comments/1