[02:06] <mterry> Heyo!  Does anyone know what drives the creation of the autopilot-finger device in Mir when running under autopilot?  It's not being created correctly in the nested case
[02:06] <thomi> mterry: I probably do
[02:06] <thomi> mterry: but I'm not sure I understand the questino :)
[02:06]  * mterry jumps on thomi and doesn't let go
[02:06] <thomi> *question, even
[02:07] <mterry> thomi, I'm looking at running unity8 in 'nested mode' which is where there is a system Mir and a user Mir
[02:07] <mterry> thomi, input works fine normally
[02:07] <mterry> thomi, but when under autopilot, the Mir autopilot-finger device gets created as an external pointer, instead of an internal touchscreen, as it should
[02:09] <thomi> so, when you say "external pointer, instead of an internal touchscreen", is the problem that it shows up as a mouse device, and not a touch device?
[02:09] <thomi> or the "external" vs "internal" bit?
[02:10] <mterry> thomi, I believe the problem is that it's a pointer, not a touchscreen.  Because the symptom I'm seeing is that drags don't happen.  And movement with a pointer probably isn't translated into a drag without a button down
[02:12] <thomi> hmm, so autopilot only supports multi-touch under mir. In order for it to create a mouse device it needs xlib bindings
[02:14] <mterry> thomi, well, I suppose those are installed.  But I'm not sure why it would decide to do that?
[02:15] <thomi> it wouldn't, unless the test case asked it to
[02:15] <thomi> I suspect the problem is elsewhere
[02:15] <mterry> thomi, I'm running the same test case just with different Mir config
[02:15] <thomi> do you have a test log from the failure?
[02:15] <mterry> thomi, yeah  :-/
[02:15] <mterry> thomi, yeah I've got a log, but with quite a bit of me-specific Mir debugging printfs in it
[02:15] <mterry> thomi, I'm guessing this is a Mir bug, not an autopilot one
[02:16] <thomi> so in the AP log, if you see '_uinput' lines, you're using uinput, which means multitouch
[02:18] <mterry> thomi, well, it makes two devices, one is "py-evdev-uinput" and one is "autopilot-finger", which I'm guessing means it's using uinput
[02:19] <thomi> mterry: right - the first is the keyboard device
[02:20] <thomi> the second is the multi-touch device
[02:20] <mterry> thomi, ah, ok
[12:02] <alan_g> alf_: any thoughts on https://code.launchpad.net/~robertcarr/mir/client-input-report/+merge/194028 (if not I'll just top-approve)
[12:26] <alf__> alan_g: sorry, network problems, I am ok with the MP
[12:27] <alan_g> alf__: nw
[15:04] <alan_g> alf__: I was just referring to the C++ standard and could not help noticing that the declaration style there is the one Daniel thinks is used by a few eccentrics.
[15:12] <alf__> alan_g: Some people argue that all C++ users are eccentrics, and we should just go back to C ;)
[15:13] <alan_g> Some people are welcome to put that into practice (so long as they stop bothering me)
[16:06] <kgunn> Mirv: just a heads up...we're wanting to update our mir trunk & we have an abi break that needs coordinating, i'll ping you on monday as i understand you guys are struggling to get back to green
[16:57] <racarr> Morning
[16:57] <alan_g> kdub: any guess what bug 1249019 might be?
[16:57] <kdub> alan_g, perhaps unity8 is running?
[16:57] <kdub> let me try
[16:58] <racarr> alan_g: Try running
[16:58] <alan_g> kdub: Nope - it fails the first iteration then
[16:58] <racarr> powerd-cli active
[16:58] <racarr> and backgroundingit
[16:58] <kdub> yes, could be that too
[16:58] <racarr> powerd can put the screen in to a suspsned state that mir cant remove attimes
[16:59] <alan_g> This is a pass once fail second time scenario
[17:01] <alan_g> racarr: "powerd-cli active" says "Press ctrl-c to exit."
[17:05] <racarr> alan_g: Yes you background it
[17:05] <racarr> the functionisas long as it is alive
[17:05] <racarr> it keeps powerd in the active state
[17:05] <racarr> weird interface
[17:06] <alan_g> racarr: still get a SIGABRT on the second test cycle
[17:16] <racarr> alan_g: :*
[17:16] <racarr> :(*
[17:17] <racarr> not aware of it then
[17:18] <alan_g> racarr: I'm guessing it is a teardown problem - If I repeatedly run the test executable it doesn't show a problem
[17:18] <racarr> ah
[20:28] <racarr> I love writing the literal for a null function "[](){}" lol
[20:43] <kdub> racarr, hah, yeah
[20:44] <kdub> ({[](){},[](){}})
[20:44] <kdub> initializer list of null functions
[21:01] <racarr> kdub: Code is poetry ;)
[21:02] <racarr> poetry is just getting reallymodern
[21:02] <racarr> lol
[21:02] <sarnold> lol
[22:53] <RAOF> Whee! Alarm clock malfunction - Zoë didn't wake up until almost 9 this morning.
[22:53] <RAOF> In her defence, she woke up quite a lot during the night :/
[23:10] <olli_> RAOF, and what exactly are you giving her? can i get this in the US or can you send some over?
[23:12] <kgunn> kdub: hey...so the 4 integration tests we were chatting about earlier...if i do apt-get install mir-test-tools will that pull those in ? or do i have to build them ?....i guess i should just ask...how to build and run the 4 tests :) ?
[23:14] <kgunn> kdub: just a matter of curiosity...i noticed the cmakelist.txt for test_client_render has a if( MIR_PLATFORM STREQUAL "android")
[23:14] <kgunn> but the others (buffer, display, internal_client) don't....
[23:14] <kgunn> even tho they're under graphics/android...
[23:15] <kdub> kgunn, that directory is disabled
[23:15] <kgunn> kdub: disabled in a sense, those don't become part of mir-test-tools ?
[23:16] <kgunn> brb...picking up man-child
[23:16] <kdub> kgunn, http://bazaar.launchpad.net/~mir-team/mir/trusty/view/head:/tests/integration-tests/CMakeLists.txt#L21
[23:16] <kdub> all of them are compiled on android, but not gbm
[23:16] <kgunn> ah
[23:16] <kdub> not really sure what goes in that package, have to check
[23:17] <kgunn> ok...wife going now...
[23:17] <kgunn> so what package do those tests go into is the better question kdub
[23:17] <kgunn> ?
[23:21] <kdub> kgunn, i'll send an email
[23:23] <kgunn> kdub: thanks dude!
[23:23] <racarr> Oh yeah deleting
[23:23] <racarr> morecode :D
[23:33] <kdub> racarr, i'm having that experience too over in the android code world
[23:33] <kdub> 'whoohoo, less code!'
[23:34] <kgunn> that's good to hear
[23:52] <racarr> kgunn: It should all be gone by january at the latest