[09:41] <duflu> alan_g: Is there a rule of thumb for what to do in place of "static virtual"?
[09:41] <duflu> It's been years since I needed one
[09:41] <alan_g> What do you want it to do?
[09:42] <duflu> alan_g: Return a constant value. But that is configurable based on the class you ask
[09:42] <duflu> Hmm
[09:42] <duflu> Not static
[09:43] <alan_g> Determined at runtime or compile time?
[09:44] <duflu> alan_g: Compile time
[09:45] <duflu> But the implementation class isn't known till run time
[09:45] <duflu> I know it's theoretically reasonable but maybe not possible in C++
[09:45] <duflu> It's just like querying RTTI in a way
[09:46] <alan_g> virtual Value value() const = 0;
[11:35] <alan_g> didrocks: is there a CI problem? Jenkins doesn't seem to have done anything for 10 hours or so: https://code.launchpad.net/mir/+activereviews
[11:36] <didrocks> alan_g: you should ping the vanguard from the CI team for that I guess
[11:36] <didrocks> on #ubuntu-ci-eng
[11:36] <didrocks> (we are only doing the landings)
[13:22] <kgunn> alf__: hey, so josharenson is working on getting glmark2 running as part of our ci...however, glmark2 that's in archive for arm is only for x11
[13:22] <kgunn> my understanding is that there is a glmark2_es2_mir
[13:22] <kgunn> that can be built, but its not in the archive
[13:23] <kgunn> so i was hoping to add it, do you see any problem there ?
[13:23] <kgunn> mir is in universe as well, so should be fine...right?
[13:23] <kgunn> (need to do this in order to have the ability for the jenkins job to apt-get install glmark2-es2-mir as part of the ci run)
[13:26] <alf__> kgunn: when I released 2014.03 I also updated a packaging branch so that it produces packages for all variants https://code.launchpad.net/~glmark2-dev/glmark2/glmark2-package
[13:28] <Cimi> hello guys
[13:28] <Cimi> I import Unity.Application 0.1 in my qml
[13:28] <Cimi> I start this when unity8 is not running
[13:28] <Cimi> but still, my app crashes with this error
[13:29] <Cimi> [libprotobuf ERROR google/protobuf/descriptor_database.cc:57] File already exists in database: unityrpc.proto
[13:29] <Cimi> [libprotobuf FATAL google/protobuf/descriptor.cc:954] CHECK failed: generated_database_->Add(encoded_file_descriptor, size):
[13:29] <Cimi> terminate called after throwing an instance of 'google::protobuf::FatalException'
[13:29] <Cimi>   what():  CHECK failed: generated_database_->Add(encoded_file_descriptor, size):
[13:40] <kgunn> Cimi: so you start before unity8...but are you using unity-mir ? or...rather...are you trying to launch the mir server ? or going through  u-s-c's instance of the mir server ?
[13:41] <Cimi> kgunn, just running the app with upstart...
[13:41] <Cimi> kgunn, don't know the internals
[13:41] <Cimi> kgunn, so probably mir is already running
[13:42] <kgunn> Cimi: mmm...do you see the greeter ?
[13:42] <Cimi> kgunn, I'm starting on xsession-init
[13:42] <Cimi> nope
[13:42] <kgunn> Cimi: yeah...something needs to get you a mir server fired up...
[13:42] <kgunn> Cimi: are you just doing this for testing ? or is this actually how you're planning on doing it ?
[13:43] <kgunn> e.g. does the user see the greeter first? then dismiss into the welcome wizard ?
[13:43] <Cimi> kgunn, I suppose the welcome wizard needs to be before unity
[13:43] <kgunn> Cimi: sure...
[13:43] <Cimi> before everything
[13:43] <kgunn> it can be..
[13:43] <kgunn> Cimi: well....there's some effort there tho...
[13:43] <kgunn> wonder if you can just glom onto greeter ?
[13:43] <kgunn> mterry: ^
[13:44] <kgunn> seems Cimi needs a mir server....but wants to be "before everything else"
[13:44] <kgunn> should he start his own mir server ?
[13:45] <mterry> kgunn, Cimi: my plan was to insert it right before greeter
[13:45] <kgunn> Cimi: you're suffering since split hasn't landed yet
[13:46] <kgunn> Cimi: today there is only 1 mir server....shared by unity8 (session) & greeter (system)
[13:46] <mterry> kgunn, Cimi: well, with split greeter, you'd have same problem
[13:46] <Saviq> kgunn, mterry, Cimi, he doesn't need a mir server, thouhg
[13:46] <mterry> Why do we need a mir server?
[13:46] <Saviq> it could be just a client
[13:46] <mterry> This is for notifications?
[13:46] <Saviq> mterry, no, no need for a server
[13:46] <Saviq> mterry, we can be just a client
[13:47] <kgunn> Saviq: client to u-s-c's server ? or a 3 rd instance?
[13:47] <Saviq> kgunn, client should be good
[13:47] <Saviq> the current issue is that Cimi loads the Unity.Application API , which probably requires to be a mir server
[13:47] <Saviq> or well, wait
[13:47] <Saviq> I think he needs to be a server for the OSK
[13:48] <Saviq> we don't want the OSK to go directly to u-s-c do we
[13:48] <kgunn> mmm
[13:48] <kgunn> how is it handled in greeter for pin code before unity8 is started ?
[13:48] <kgunn> same case isn't it?
[13:48] <Saviq> yeah
[13:48] <Saviq> mterry, ↑ ?
[13:48] <Saviq> in split greeter, that is
[13:49] <mterry> kgunn, Saviq: in split greeter, maliit talks to split greeter, which is a server
[13:50] <greyback> The unity.Application  plugin can only be used by an application that instantiates a QMirServerApplication. Here's a simple example: lp:~gerboland/+junk/qml-demo-shell/
[13:50] <mterry> Saviq, out of curiosity, what is wrong with OSK talking to USC?
[13:50] <Saviq> mterry, you tell me :)
[13:51] <greyback> different users could have different OSKs...
[13:51] <mterry> I don't know enough about differences between mirservers, but I'd guess nothing
[13:51] <Saviq> mterry, I think at least one thing is that shell, greeter, wizard needs to control the input routing
[13:51] <mterry> greyback, yeah but this is a very special case (first boot wizard)
[13:51] <greyback> mterry: ah I was missing context, sorry
[13:52] <Saviq> mterry, greeter is not as special, though
[13:52] <Saviq> greyback, that would include the input areas and such, right?
[13:52] <mterry> Saviq, sure.  But greeter acts like unity8
[13:52] <greyback> Saviq: for USC, yes
[13:52] <Saviq> mterry, in that sense welcome wizard does, too, 'cause it's the only "shell" running at the time, even if the only client would be the OSK
[13:53] <Saviq> greyback, I mean if the welcome wizard wants to use import areas (which it needs for OSKController), it needs to be a QMirServerApplication?
[13:53] <mterry> Saviq, yeah...  but it's not a shell.  It's just a client itself
[13:54] <mterry> I mean, we can change it to be a server too.
[13:54] <Saviq> mterry, yeah, as long as it can control the input area of the OSK...
[13:54] <kgunn> but wait...isn't Cimi finding out he alreaday needs more clients (following the shell argument...like notifications, settings app)
[13:54] <greyback> Saviq: yes
[13:54] <mterry> kgunn, I don't think notifications are clients...  I think shell renders those
[13:54] <Cimi> kgunn, they are within the app
[13:54] <mterry> (Or whomever loads the Notifications plugin, which maybe could be wizard)
[13:54] <Saviq> notifications is in-surface
[13:55] <Saviq> settings? why?
[13:55] <Saviq> anyway, gtg for a bit
[13:55] <Saviq> actually, bringing the laptop with me...
[13:55] <kgunn> Cimi: do you launch settings ? or just pirate pieces of it ?
[13:55] <Cimi> kgunn, I import the plugins I need
[13:55] <Cimi> kgunn, it's standalone app
[13:57] <mterry> So looks like only client needed is OSK so far
[13:57] <kgunn> ok...so sounds like we're settled.... mir client ? mterry ?
[13:57] <kgunn> ;)
[13:58] <mterry> But sounds like it needs to be a server to manage the OSK
[13:58] <mterry> Cimi, we night need to make the wizard a little server...  greyback, do we have any experience with OSK and servers that aren't unity-mir?  Or should we just use unity-mir here too
[13:59] <greyback> the server needs logic to show/hide the OSK surface, and do a little input filtering (top of OSK surface transparent, so should not steal events)
[13:59] <mterry> greyback, is that stuff we get magically for being a server, or do we have to reimplement that logic?
[14:00] <greyback> mterry: you'll have to re-implement, if your server is not using unity-mir
[14:00] <greyback> which it isn't, it's using mostly default mir stuff, isn't it?
[14:00] <mterry> greyback, do you remember how closely tied unity-mir is to the unity8 shell?  Last time I remember looking, it was checking surface names and such
[14:01] <mterry> greyback, right now the wizard isn't a server at all
[14:01] <mterry> greyback, we were hoping to get away with just being a client
[14:01] <greyback> mterry: but the wizard is a client, and should stay that way
[14:01] <greyback> mterry: what is the server here?
[14:02] <greyback> unity-mir needs one thing from a shell, that it names its surface something particular. That's all.
[14:02] <mterry> greyback, well this is all up for debate.  But the plan I was envisioning was having wizard run under USC as a client with maliit server running beside it
[14:02] <greyback> mterry: that's fine. So USC needs logic to handle the OSK surface
[14:02] <mterry> Hrm
[14:03] <mterry> greyback, and that logic is stealable from unity-mir?
[14:03] <mterry> I don't know if I like USC adding that feature just for this one time wizard
[14:03] <greyback> mterry: it's mostly implemented in QML, but it's pretty easy
[14:03] <mterry> Ugh or gaining QML
[14:03] <greyback> 1) try to detect the OSK surface by its name
[14:04] <mterry> right now USC doesn't need to bother with the UI parts of Qt
[14:04] <greyback> 2) listen for maximize/minimize evnets from that surface, and when they happen, show/hide the surface
[14:04] <greyback> 3) set an input area on the OSK surface so the transparent part does not take events
[14:06] <mterry> greyback, out of curiosity, why doesn't OSK just show/hide itself and such?
[14:06] <mterry> And set it's size itself
[14:07] <greyback> mterry: because surfaces cannot do that. That's a shell's decision
[14:07] <mterry> Instead of needing to have a transparent part
[14:07] <greyback> ah the transparent part for hte top row of keys, when you press them, the letter pops up higher
[14:07] <mterry> Ah OK
[14:07] <mterry> Details details everywhere
[14:08] <greyback> indeed
[14:08] <greyback> some keyboard too, a long press pops up a accent selector, which needs to receive events
[14:08] <mterry> greyback, if we add those features to USC, I'd want to avoid QML.  How easy is it to do that input filtering without a nice Qml input area?
[14:09] <greyback> input filtering a Mir concept, I've just wrapped it for use in QML
[14:09] <mterry> Yar, just hoping it was easy
[14:09] <mterry> Still, feels weird to add this complexity to USC just for the wizard
[14:10]  * mterry wishes wizard didn't need OSK
[14:10] <greyback> think mir::shell::surface has a  installInputArea method, which takes a rectangle.
[14:10] <mterry> greyback, how ugly do you feel it would be to make wizard use unity-mir?
[14:10] <greyback> inside that rectangle, the surface gets the events. Else it doesn't.
[14:11] <greyback> mterry: then you're making the wizard a mir server. Which would work, yeah
[14:11] <mterry> greyback, we'd have to name the wizard surface like the shell does.  But it sounds like besides that, it'd work?
[14:12] <greyback> mterry: think so, yes. Maliit needs to connect to the wizard's mir socket, Then all should be good
[14:12] <mterry> Cimi, ^ what do you think?
[14:13]  * Cimi reads
[14:15] <Cimi> mterry, I like your simpler solution :D
[14:15] <mterry> Cimi, "simpler"  :)
[14:19] <mterry> Cimi, so to do that...  unity8 has src/main.cpp which dlopens unity-mir
[14:19] <Cimi> mterry, already saw it
[14:19] <mterry> Cimi, we probably don't need all the complexity it has (in particular, we don't need to worry about non-mir instances)
[14:20] <mterry> Cimi, and check unity-mir source.  Somewhere in there, it checks a surface name that we'll want to match to unity8
[14:21]  * Cimi looks
[14:28] <alf__> kgunn: greyback: https://code.launchpad.net/~afrantzis/mir/non-blocking-swap-buffers-spike , it's a spike not ready for an MP just yet, but it should work.
[14:28] <greyback> have a look at lp:~gerboland/+junk/qml-demo-shell/ for a simple exmaple
[14:29] <greyback> alf__: wow nice! Will test straight away
[15:30] <kdub> jenkins traffic jam
[16:55] <kdub> anyone know what's going on with autolanding?
[16:56] <alan_g> kdub: yeah, there's problems with the phones
[16:57] <kdub> alan_g, thanks
[16:58] <alan_g> I asked on #ubuntu-ci-eng and found that it had been announced on a mailing list I didn't know about
[18:19]  * mterry is seeing odd input bug with mir/devel + unity8...
[18:19] <mterry> I'm testing further, but if anyone has played with full stack lately, let me know
[19:23] <kgunn> mterry: got a description ?
[19:23] <kgunn> racarr: anpok ^
[19:23] <mterry> kgunn, I was seeing the greeter session come up but wasn't able to interact with it
[19:23] <mterry> kgunn, still not sure which component's fault it is yet.
[19:24] <kgunn> mterry: so like osk wouldn't invoke ? as well, you couldn't swipe?
[19:25] <mterry> kgunn, right, couldn't swipe.  didn't get as far as OSK
[19:25] <mterry> kgunn, nm, can't reproduce now...  :-/
[19:25] <mterry> kgunn, I have some updates for silo 002 if you have time
[19:26] <kgunn> sure
[19:27] <kgunn> hey...crap, meant to ask you mterry about
[19:27] <kgunn> https://code.launchpad.net/~mterry/gsettings-ubuntu-touch-schemas/volume/+merge/209158
[19:27] <kgunn> i have it in the landing sheet...but, i can't recall...did you want it landed in isolation or not ?
[19:27] <anpok> wasnt that one of the issues that crept in and got fixed with the surface restructuing? the thing that racarr looked at?
[19:27] <anpok> +r
[19:28] <anpok> hm most current greeter stuff is now in a different silo?
[19:28] <mterry> kgunn, it landed with indicator-sound in trusty already.  We can drop it
[19:29] <mterry> kgunn, for silo 002... add ~mterry/platform-api/mir-changes & ~alan-griffiths/unity-mir/compatibility-with-mir-changes & rebuild platform-api, unity-mir, and ubuntu-touch-session
[19:29] <mterry> kgunn, we can remove any indicator-sound or schema stuff in silo 002 now too, if any are lfet
[19:30] <mterry> anpok, we moved to silo 002 yeah
[19:30] <mterry> (from 004)
[19:30] <anpok> k
[19:31] <mterry> anpok, silo doesn't work right now due to mir churn, but it's about to because kgunn is a silo wizard
[19:49] <kgunn> mterry: building now
[19:51] <kgunn> gotta reboot..
[19:52] <mterry> racarr, do you know about any changes that would affect raising/focusing sessions?
[19:52] <mterry> Or anybody really
[19:54] <kdub> mterry, yeah, SurfaceRanker is gone
[19:54] <kdub> the raise() method moved to SurfaceConfigurator
[19:56]  * kdub always thought "surface rancor" when reading that one
[19:57] <racarr> mm
[19:57] <mterry> My USC changes to raise the spinner session don't seem to be working anymore
[19:57] <racarr> someone must have landed unity-mir/usc updates or it just wouldnt build right
[19:57] <mterry> hmm
[19:58] <mterry> racarr, my copy of mir/devel must be between re-organizations then
[20:00] <mterry> racarr, I don't see raise() in SurfaceConfigurator in mir/devel
[20:00] <racarr> maybe
[20:01] <racarr> I think kdub is right with investigate SurfaceRAnker...lots landing so might be easier to just try and see what is going on with GDB rather than guess at what change could have caused it
[20:01] <anpok> surface wanker removal has not landed yet
[20:01] <racarr> I can help tomorrow but right now am reloading chromium in to my head and doing updates etc
[20:01] <mterry> racarr, no worries
[20:02] <anpok> https://code.launchpad.net/~alan-griffiths/mir/make-use-of-scene-Surface/+merge/213894
[20:02] <racarr> anpok: Top 10 typos of 2014
[20:02] <racarr> Mm
[20:02] <anpok> :)
[20:02] <racarr> maybe something doesnt work
[20:02] <racarr> in the intermediate state
[20:02] <racarr> though
[20:03] <anpok> now i see it .. oh dear..
[20:04] <racarr> Hahahahaha
[20:04] <anpok> mterry: but it could also be related to other changes..
[20:04] <kdub> well, landing soon then :)
[20:52] <kgunn> bregma: so...i'm sure i did somethin' wrong...but, i added your unity8 desktop ppa, but i only installed indicator-session....as i wanted to test the usc thingy...
[20:52] <kgunn> and i am working off the assumption/knowledge that qtubuntu got update
[20:52] <kgunn> d
[20:52] <bregma> I believe it did, let me check on my most updated machine....
[20:52] <kgunn> and that lightdm is fixed for cursor
[20:53] <kgunn> bregma: yeah...i just didn't have an "option" on the greeter ?
[20:53] <kgunn> ( i assume its not guest...but that it would say "unity8 desktop" or some such)
[20:54] <bregma> is unity8-desktop-session-mir installed?  The one in universe is current
[20:56] <bregma> I have the qtubuntu-desktop installed from universe (0.54+14.04.20140402-0ubuntu1) and it's working for me
[20:57] <bregma> lightdm is from main 1.9.14-0ubuntu1
[20:58] <bregma> unity8-desktop-session-mir is from universe 1.0.10+14.04.20140402-0ubuntu1
[21:02] <kgunn> bregma: well i feel stupid....
[21:03] <kgunn> just installed
[22:00] <kgunn> bregma: still no luck...here's my usc log
[22:00] <kgunn> https://pastebin.canonical.com/107762/
[22:00] <kgunn> i gotta run...
[22:00] <kgunn> but you might want to give usc from the silo ppa a shot
[22:00] <kgunn> https://launchpad.net/~ci-train-ppa-service/+archive/landing-011
[22:01] <kgunn> if it works for you...then its me
[22:01] <kgunn> if it doesn't then something else went wonky with usc
[22:12] <bregma> good old "Failed to set DRM crtc"
[22:25] <kdub> unrelated :) but, its a real benefit for our interfaces that we have to look at things from the two platform's perspectives