[04:44] RAOF, was / is there an XMir git branch (i.e. with the actual changes on git master and not with a debian/ dir like fdo:~mlankhorst/xserver [04:44] Trying to work out correct attribution for xmir.patch [04:45] robert_ancell: I presume Maarten has a branch somewhere, but I've only got https://github.com/raof/xserver [04:45] Which isn't the one that you're after. [04:48] robert_ancell: Some quick searching shows up http://cgit.freedesktop.org/~mlankhorst/xserver/ [04:48] RAOF, that just has debian/ added and everything in the patch file [04:49] Yeah, dunno, sorry. [04:49] np [04:49] He presumably had a git tree to develop in, though. [04:51] Presumably [04:51] robert_ancell: It's documented in the obvious place :) [04:52] robert_ancell: https://code.launchpad.net/xmir [04:52] But yeah we definitely need to move it [04:53] duflu, again, that's pointing at a branch containing debian/patches, i.e. not a branch based off master with the changes done inline [04:53] duflu, I am moving it now [04:53] And without the original branch we're going to lose attribution. But it's probably not a big deal. [04:53] robert_ancell: I know it's ugly. I doubt Maarten did maintain anything inline. He was always patches [04:54] I'm going to split up the changes anyway so we can get them upstream at some point [04:54] robert_ancell: I never did figure out how to build in manually too... Only got a successful build from debuild [04:54] (strange compiler errors otherwise) [04:59] Obviously the secret sauce is in debian/ [04:59] * duflu goes to get some sunlight [06:26] Man touchscreen hardware really sucks. Even when you eliminate all the graphics lag, touchscreens are still slow. Plugging a mouse into the same device is dramatically more responsive. [08:25] alf_: have you had a chance to look at the power off/on/off/on/... crash? [08:27] alan_g: yes, the crash happens in a GL call, I am trying to figure out why... [08:28] alf_: ack. I'll leave you to it. :) [08:28] * alan_g goes to port glmark2-mir to contemporary API [08:32] alan_g: You'll also want to wait till the client ABI bump before updating glmark2-mir in wily. Or else we'll have to do it twice [08:33] duflu: we need to decide how to work around https://code.launchpad.net/~alan-griffiths/mir/bump-client-ABI/+merge/258769/comments/646197 [08:33] But at least I can get the code ready [08:36] alan_g: Take it out of CI temporarily I guess. BTW that is https://bugs.launchpad.net/mir/+bug/1341490 [08:36] Ubuntu bug 1341490 in Mir "Bumping the client ABI causes CI failures" [Medium,Triaged] === chihchun_afk is now known as chihchun [09:10] alan_g: @glmark2, I already have an upstream branch for the update [09:11] alf_: ok, I'll drop mine then [09:11] alan_g: but we will need to update the ubuntu packages [10:05] alf_: Booo.... requires ES3 - https://www.khronos.org/opengles/sdk/docs/man3/html/glReadBuffer.xhtml [10:05] Sigh [10:05] And even then still not FRONT [10:06] ES is surprisingly limited, again [10:17] * alan_g does a clean build from trunk and gets "ClientSurfaceEvents.surface_receives_state_events...Segmentation fault (core dumped)" [10:32] * alan_g realise he did something stupid [11:17] alan_g: https://code.launchpad.net/~afrantzis/mir/fix-1454201-usc-crash-for-0.13/+merge/258863 [11:17] alf_: thanks! [11:18] alan_g: More investigation is needed to figure out why the workaround is needed (and if it's really our fault or the driver's), but this should be enough to unblock the release [11:18] understood [11:41] alf_: any ideas? https://code.launchpad.net/~afrantzis/mir/fix-1454201-usc-crash-for-0.13/+merge/258863/comments/646452 [11:46] The test diagnostic is rather unhelpful. :( [11:47] alan_g: I knew I was forgetting something (to check the tests!) [11:48] alan_g: I will fix and update the branch [11:50] alf_: thanks. [Non-urgent: does the diagnostic need to be so far removed from the actual problem?] [11:56] alan_g: the issue you spotted yesterday in silo21 did you resolve it at all? [11:59] davmor2: we're (well alf_) closing on it. I expect to rebuild and test after lunch. [11:59] * alan_g goes to lunch while alf_ does the work. [11:59] alan_g: that's great just remembered about it so thought I'd ask while it was in my head :) === alan_g is now known as alan_g|lunch === dandrader_ is now known as dandrader === alan_g|lunch is now known as alan_g [13:23] I've mir_proving_server running on my laptop as root. Is it possible to run mir clients without being root? [13:24] I did "sudo chmod a+rwx mir_socket" but trying mir_demo_client_egltriangle without root still gives me "Can't get connection" [13:25] ok, manually pointing out the location of the mir_socket did the trick: "/tmp$ mir_demo_client_egltriangle -m mir_socket" [13:26] wonder why I don't have to do so when I run the client as root [13:27] dandrader: the socket location depends on some environment variables that are set differently [13:29] alan_g, where/how can I find a list of env vars that mir looks for? [13:30] mir_proving_server --help ... "Socket filename [string:default=$XDG_RUNTIME_DIR/mir_socket or /tmp/mir_socket]" [13:32] alan_g, so this translates to having a MIR_SERVER_HOST_SOCKET in the environment of the client app? [13:33] dandrader: I usually set MIR_SOCKET=/tmp/mir_socket [13:33] If you run as root then $XDG_RUNTIME_DIR isn't set so server and client look at /tmp/mir_socket [13:33] If you run as non-root then it is usually set [13:35] alan_g, I got it from the help text. but what's the name of the env var I should use for the client? [13:36] alan_g, it says nothing aboutn the existence of the MIR_SOCKET env var [13:36] greyback_, thanks! [13:42] So...autolanding is down I guess? [13:59] alan_g: fyi, qtmir had some landings. I'm working on fixing up qtmir/devel-mir-next to suit [13:59] greyback_: Oh. I'll need to roll that into silo 021 [14:00] alan_g: yep, exactly why I'm doing it [14:00] Thanks. Is it a long job? [14:00] alan_g: nah, almost there, just 2 new tests I'm being careful with [14:01] Excellent (rebuild of mir will be finished shortly) [14:02] alan_g: in the CI Dashboard, your silo21 is for "vivid primary" - I didn't think we could land there any more [14:02] tho I see plenty of other silos with the same [14:03] my qtmir landing was in vivid+stable-overlay [14:03] I don't know why not. So long as we don't break ABI [14:04] things are unclear [14:05] They certainly are [14:06] I thought "overlay" was a temporary substitute until wily was usable. But it got hijacked [14:28] Planning to rework the event representation today (mostly to line up to input_event.cpp/the C API) [14:28] starting to realize there may be some advantage to [14:28] deunionizing the event... [14:29] I was thinking about the playground shell and the big if statement for handling [14:29] keybindings there and realized what you want is probably some sort of [14:29] I feel like I've never had the genuine thought 'awesome, its a union' [14:29] kdub: not since I was 12 or so here :p [14:30] haha uh but you want [14:30] some sort of Keybinder interface [14:30] but then I realized keybinding description is [14:30] the same signature as "MirKeyboardEvent" - "MirInputEvent" [14:30] (Minus MirInputEvent that is) [14:30] so if you could construct a MirKeyboardEvent without constructing the enclosing [14:30] MirInputEvent [14:30] MirKeyboardEvent could be the [14:30] authorative uh [14:30] key type [14:30] lol [14:31] and avoid this android input mess of [14:31] MotionEvent v. NotifyMotionArgs (partially constructed MOtionEvent basically) [14:33] in other news I literally forgot to drink coffee [14:33] this morning [14:33] this is unprecedented [14:41] Hmm [14:42] I've been thinking of promoting (Keyboard/Touch/Pointer)Event::Modifiers to InputEvent [14:42] but the above thought suggests otherwise === dandrader is now known as dandrader|afk [14:47] and then do things like comparing events.. [14:47] but does it matter that there is a union? [14:48] anpok_: Well the thing is if [14:48] its a union then they all need to contain [14:48] timestamp [14:48] which ISNT part [14:48] of a keybinding [14:48] description [14:48] and [14:48] device_id [14:48] which...could be [14:48] lol [14:48] ugh [14:49] I guess thats suggesting the time is the unique member [14:49] yeah because its like [14:49] a Keyboard state [14:49] + a time [14:49] = an event [14:50] or + occurence [14:50] what do you mean? [14:50] if you leave the device id out of the keyboard stae [14:50] *state [14:50] ah, yes. [14:50] where and when [14:53] hmm [14:53] so if not a union...C++ inheritance? [14:53] Rust traits + FFI [14:54] ...focus focus [15:01] how did we end up with so much 'required' in protobuf :/ [15:05] kdub, standup [15:05] ah, coming === dandrader|afk is now known as dandrader [15:38] I run mir_proving_server on my laptop. run a client in from another ssh terminal. then in the client's terminal I do ctrl+c. mir_proving_server frezes for good, getting defunct and impossible to kill. is that a know issue? [15:41] dandrader: I'm not aware of that happening. [15:41] alf_: silo 021 has your fix and is working for me on mako. Wanna try it? [15:43] greyback_: are we there yet? === chihchun is now known as chihchun_afk [16:07] some how building mir_proving_server myself, with debug config, and running it under gdb made it behave.... [16:14] alan_g: all good on krillin [16:15] \o/ === alan_g is now known as alan_g|EOD === dandrader is now known as dandrader|lunch === mibofra is now known as Guest93220 [18:33] Does anyone know how to GDB mir_unit_tests/ [18:34] if I run gdb on mir_unit_tests GDB silently detaches [18:34] (no kidding...) [18:34] if I run it on .uninstalled [18:34] Bus error [18:34] its been happening for about 2 weeks now... [18:35] also has anyone experienced problems with system headers getting mixed in to local compilation... [18:38] hm that did not happen for me [18:40] anpok_: Ok I guess ill just quit programming and get a job in the farm. [18:40] ...printf debugging and dist upgrade it s [18:40] is [18:42] ahaha [18:42] I mismatched an int32_t and an int64_t in a union [18:42] making it look as if another enum value (preceeeding it in the union) [18:42] was overwritten with the value which it would have had if [18:42] parts were compiled with system headers instead of the modified local headers [18:42] WHEEEE === dandrader|lunch is now known as dandrader === mibofra is now known as Guest85839 [19:29] * kdub has gotten that gdb error [19:29] on the unit tests [19:42] Mir and Unity8 on BayTrail: http://sturmflut.github.io/ubuntu/baytrail/2015/05/12/ubuntu-15-10-and-desktop-next-on-a-baytrail-tablet/ [19:42] The external HDMI port even works in theory [20:05] kdub: I have a question on android multimonitor. I know how there is a DisplaySyncGroup, which is a collection of DisplayBuffers which are all swapped at once [20:05] greyback_, right [20:05] kdub: say only 1 DisplayBuffer needs a redraw. Does the android MM stuff require the other one to also be redrawn too? [20:06] i.e. we get fresh DisplayBuffers back for all displays after a swap [20:07] greyback_, so, the updated DisplayBuffer will get a swap, and the not-updated one won't [20:07] and both will be 'reposted' [20:07] ahh [20:07] swap != post [20:08] right, I had to tease that out because hwc doesn't give me a way to just update one [20:09] so the DisplayBuffer is back to the original idea of just being the content on screen (2d stuff or overlays), and the DisplaySyncGroup does the posting [20:09] kdub: that's ok. The above scenario had me confused, but as swap != post, it's ok === Benno-0071 is now known as Benno-007 === Benno-007 is now known as lgd