=== chihchun_afk is now known as chihchun
=== faenil is now known as faenil_
alan_ggreyback: do you know the intended usage of mir/shell/persistent_surface_store.h? Or is that something for dandrader?08:56
greybackalan_g: not exactly. I see it claims to enable surface position/size persistence across session lifetimes, so WM would find it handy08:59
alan_gNote "todo Persistence across shell restarts is as-yet unimplemented."09:00
greybackyeah. "claims" :)09:01
greybackwe're not using it in qtmir/unity809:01
alan_gYeah, the server APIs are only published in Mir-0.2409:02
alan_gSo I'm a bit short of clues on what MiraAL should expose09:03
alan_gIIRC the current intended usage is for identifying "foreign" surfaces for WM09:05
RAOFalan_g: That was a happy accident.09:08
RAOFOr, rather, a happy repurposing. It's intended to be the identifier that you use for persistence across restarts, indeed.09:09
RAOFSince 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:10
alan_gRAOF: As dandrader published the headers I assume that he has plans to use them. (I'd be good with DTRT)09:12
alan_gSo you see no reason to land any version of https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/302408?09:13
RAOFI think you're correct, and WindowManagerTools::window_for_id() is likely to be the winner.09:14
RAOF(Commented on the branch)09:20
=== hikiko is now known as hikiko|ln
greybackalan_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/30253111:22
alan_ggreyback: I understand the reasons.11:23
=== chihchun is now known as chihchun_afk
=== hikiko|ln is now known as hikiko
=== mterry_ is now known as mterry
oSoMoNdoes Mir have support for client-side decorations?13:11
alan_goSoMoN: no13:14
oSoMoNalan_g, thanks. Are there any plans to support them in the future?13:15
alan_goSoMoN: bug 1398849 has probably the latest info13:17
ubot5bug 1398849 in gtk+3.0 (Ubuntu) "Support client-side window decorations (I can see two title bars for GTK on Mir)" [Wishlist,Triaged] https://launchpad.net/bugs/139884913:17
alan_gdandrader: do you agree with the last comment? https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/30240813:51
* dandrader checks13:52
dandraderalan_g, not familiar enough with miral context to give any useful opinion right now...13:59
=== dandrader is now known as dandrader|afk
alan_gdandrader|afk: the basic question is whether we currently expect shells to want more than identifying a surface from an id14:01
=== davmor2_ is now known as davmor2
=== dandrader|afk is now known as dandrader
dandraderalan_g, any usecase in mind?14:25
alan_gOh. I thought you were the one that "published" the PSS headers in Mir. My mistake.14:26
alan_gdednick: do you agree with the last comment? https://code.launchpad.net/~alan-griffiths/miral/persistant-surface-store/+merge/30240814:28
dednickalan_g: looking14:29
dednickalan_g: we need id_for_surface, so unless there's another way getting it...14:32
dednickalan_g: i added that functionality in mir http://bazaar.launchpad.net/~mir-team/mir/development-branch/revision/355314:33
dednickfor the application menus14:34
alan_gdednick: presently not exposed through miral. What's the usecase?14:34
dednickalan_g: application menus are exposed through dbus using persistent surface id. unity8 need to get the surface for those published ids.14:35
alan_gThat's "surface_for_id" not "id_for_surface"14:36
dednickalan_g: no, unity8 gets the ids from dbus. need to get the surfaces for those ids.14:37
alan_g@"<dednick> alan_g: we need id_for_surface," do you have a usecase for id_for_surface()?14:38
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
dednickalan_g: huh?14:40
dednickalan_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:40
alan_gto get the surface you call "surface_for_id(the_id)" and get a surface14:41
dednickalan_g: lol. of course you do! sorry. apparently my brain isnt working14:42
alan_gjounih_: probably a problem with the VMware drivers14:42
jounih_Is there a way to get it working?14:42
dednickalan_g: in that case, no, there is no current usecase for id_for_surface14: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:42
dednickalan_g: in the server. only in the client14:43
jounih_I can put logs on gist if anyone wants to have a look?14:43
alan_gjounih_: https://bugs.launchpad.net/mir/+filebug14:44
greybackjounih_: it's crashing, someone needs to investigate why14:44
jounih_ok I filed a bug14:49
ubot5Launchpad bug 1611804 in Mir "Unity8 session is crashing in VMWare" [Undecided,New]14:49
alan_gjounih_: thanks!14:55
mhall119jounih_: 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 that15:24
jounih_I did, he is here15:24
jounih_he pointed me to bregma who pointed me here15:24
bregmajounih_, did you ever check for a unity8 crash log in /var/crash in your VM?15:27
jounih_not yet, i’ll atttach those to the bug now15:30
greybackbregma: fyi: https://bugs.launchpad.net/mir/+bug/1611804/comments/116:00
ubot5Launchpad bug 1611804 in Mir "Unity8 session is crashing in VMWare" [Undecided,New]16:00
=== dandrader is now known as dandrader|bbl
=== dandrader|bbl is now known as dandrader
=== davmor2 is now known as davmor2_Hols

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!