[05:35] <anpok> RAOF: the keyboard modifier mp should do the right thing now..
[05:35] <RAOF> anpok: Yeah, I'm just looking at it.
[05:36] <RAOF> Thanks!
[07:14] <duflu> RAOF: Oh, my Xmir stability fix also corrects clipping enough that non-compositing WMs now work :)
[07:18] <duflu> All the WM things now work \o/
[07:19]  * duflu parties like it's 1990 for X11
[07:19] <duflu> Oh, that should be 1989
[07:19] <duflu> dix/window.c:    if (party_like_its_1989) {
[08:33] <anpok> duflu: https://code.launchpad.net/~andreas-pokorny/mir/bump-input-platform-abi-for-0.18/+merge/274410 this should be fine now..
[08:34] <duflu> anpok: OK, but I think I'm done with Mir reviews for the day
[08:34] <duflu> Tis the hour for Xmir
[10:23] <greyback_> alan_g: how dodgy does this look to you: https://code.launchpad.net/~gerboland/qtmir/fix-cmdline-args/+merge/274954
[10:24]  * alan_g thinks "if you have to ask..."
[10:28] <alan_g> @"+ // argv2 - Mir parses out arguments that it understands. It also removes argv[0], but we will put it back." sounds like there should be a Mir bug reported.
[10:28] <greyback_> alan_g: I wasn't sure if that was intentional tbh
[10:29] <alan_g> greyback_: IIRC there's no guarantee that the strings passed to the callback remain valid after the call
[10:29] <alan_g> Reporting a bug is a good way to test the intention
[10:29] <greyback_> alan_g: ok
[10:31] <alan_g> It's a lokg time since I reworked the Mir code, but the boost.Options stuff didn't seem intended to "play nice" with other parsers.
[10:33] <zzarr> hello! are there any documentation for the MIR display server protocol?
[10:38] <alan_g> zzarr: Mir provides an API not a protocol. API documentation is here: https://unity.ubuntu.com/mir/index.html
[10:39] <Guest42341> glmark2 stopped working after OTA7 https://bugs.launchpad.net/canonical-devices-system-image/+bug/1507982
[10:40] <zzarr> alan_g, so what I'm looking for is a way to make a userland driver then
[10:43] <alan_g> I don't think that's fully supported yet. The Mir-on-X driver, for example, currently needs some yet-to-be-published-and-supported APIs
[10:47] <alf> zzarr: What do you mean exactly by userland driver?
[10:53] <zzarr> before I confuse any more (both you and me) could you explain how applications and the server communicate? (like an xclient connects to a xserver over the X protocol)
[10:56] <greyback_> alan_g: any progress on the usc multimonitor issue?
[10:56] <alan_g> greyback_: I've found enough bugs that its hard to know what to fix first.
[10:57] <alan_g> zzarr: the client call an API implemented by libmirclient. That does the rest
[10:57] <greyback_> alan_g: ok
[10:59] <zzarr> okey, I'm looking for a way to basically make a wrapper for mir to chrome os using qt
[11:02] <zzarr> I wish to be able to run a full Unity8 environment on a chrome os device
[11:06] <alan_g> Are you prepared for a couple of months work?
[11:19] <alf> Guest42341: thanks for the heads up, will investigate
[11:20] <Guest42341> alf, o/
[11:21] <Guest42341> tux racer and works fine though
[11:21] <Guest42341> and neverball
[11:24] <zzarr> alan_g, it might take a while yes
[11:46] <alan_g> zzarr: look at how the X11 support works for running Mir on X, you need to replicate that using APIs supported on ChromeOS. After that Mir will work. But not Unity8 - that uses other services too, so you'll also need to work out how to provide those.
[11:51] <zzarr> alan_g, do you have a link to the source for that mir implementation?
[11:51] <zzarr> alan_g, yes I think I would be able to run the other services in a chroot
[11:54] <alan_g> You can start from here https://bazaar.launchpad.net/~mir-team/mir/development-branch/files/head:/src/platforms/mesa/server/x11/
[11:55] <zzarr> alan_g, thanks :D
[12:03]  * alan_g decides the way that display configuration policy is applied (by the kms::Display constructor - but not X11, Nested or android) is weird.
[19:36] <kgunn> sturmflut2: ping
[19:40] <Stskeeps>    /g situ
[19:40] <Stskeeps> err.. ignore me