[00:03] <bschaefer> tvoss, robotfuel openarena working on ati as well
[00:03] <tvoss> bschaefer, ack and thx
[00:03]  * bschaefer checks the lightdm logs
[00:03] <bschaefer> np
[00:04] <bschaefer> robotfuel, I don
[00:04] <bschaefer> dont see any problems in any logs :(
[00:04] <bschaefer> things seem to have started correctly
[00:04] <robotfuel> https://bugs.launchpad.net/xmir/+bug/1206732 has logs
[00:05] <bschaefer> robotfuel, actually: http://paste.ubuntu.com/5930923/
[00:05] <bschaefer> so you are not getting any input device set correctly?
[00:05]  * bschaefer checks his own logs
[00:05] <bschaefer> it sounds like a permission issue possibly....
[00:06] <robotfuel> bschaefer: it's the same preseed and files that worked for intel and ati
[00:06] <robotfuel> bschaefer: I think it's the compiz crash
[00:06] <bschaefer> robotfuel, yeah, there use to be a permissions problem when running mir from the tty but that wouldn't make sense there...
[00:06] <bschaefer> robotfuel, that would make sense :)
[00:06] <bschaefer> but you should still be able to run open areana even if its crashed
[00:06] <bschaefer> as long as it didn't bring X down
[00:08] <bschaefer> robotfuel, o dammit, sorry, i missed this line: <robotfuel> tvoss: it ran ok on intel and radeon, on nvidia I get: ret = 0 for buffer 26
[00:08] <bschaefer> I read it as all 3 were failing!
[00:08] <tvoss> ah okay
[00:08] <tvoss> falling asleep now :) grab you guys later
[00:09] <bschaefer> tvoss, have a good night!
[00:09] <tvoss> bschaefer, thx and bye
[00:13] <robotfuel> bschaefer: I am re-running the test to see if it's reproducible
[00:13] <bschaefer> robotfuel, thanks!
[00:13] <robotfuel> I just needed to grab all the logs first ;)
[00:14] <robotfuel> I'll check back after I commute home
[00:14] <bschaefer> alright, are you a bit past your EOD?
[01:14] <robotfuel> bschaefer: I got the same result, but without the compiz crash
[01:14] <robotfuel> bschaefer: have you seen the ret = 0 for buffer 26 ret = 0 for buffer 18 before in the xorg.0.log?
[01:14] <bschaefer> robotfuel, :(, whats strange is i just ran pts/gaming-free
[01:14] <bschaefer> and I get sent back to lightdm
[01:14]  * bschaefer double checks
[01:15] <robotfuel> bschaefer: with the s-c-t ppa?
[01:16] <bschaefer> s-c-t?
[01:16] <bschaefer> u-s-c?
[01:16]  * bschaefer is using the u-s-c tesitng ppa
[01:16] <bschaefer> testing*
[01:17] <bschaefer> and I don't see anything in my xorg.0.log about buffers ret = 0
[01:18] <bschaefer> robotfuel, where did you see the greeter crash info at?
[01:19] <robotfuel> bschaefer: it was this bug https://bugs.launchpad.net/xmir/+bug/1206508
[01:20]  * bschaefer looks
[01:21] <robotfuel> bschaefer: it looks like that bug covers 2 different scenarios
[01:21] <robotfuel> bschaefer: if you read the last comment
[01:21] <bschaefer> robotfuel, well im getting kicked to the greeter when trying to run this pts/gaming-free test
[01:21] <bschaefer> for the phoronics test suite
[01:21] <robotfuel> bschaefer: what happens when you run glxinfo?
[01:22]  * bschaefer install it
[01:22] <robotfuel> bschaefer: maybe with export DISPLAY=:0 or export DISPLAY=:0.0
[01:22] <robotfuel> bschaefer: install mesa tools to run it
[01:22] <bschaefer> yeah, hmm just a bunch of info :)
[01:23] <bschaefer> robotfuel, it doesn't crash if thats what you're wondering :)
[01:24] <bschaefer> and glxgears works as well, and openarena works
[01:24] <robotfuel> bschaefer: that would be good to add to a bug
[01:24] <bschaefer> im just not sure why gaming-free causes me pain
[01:24] <robotfuel> I haven't tried games
[01:25] <bschaefer> robotfuel, could you run this on a machine: run pts/gaming-free?
[01:25] <bschaefer> err, it adds a lot of games though...
[01:25] <robotfuel> bschaefer: I can't openbenchmarking.org is blocked from the lab. that's where it downloads from
[01:26] <robotfuel> bschaefer: I'll download it now and try when I get in work tomorrow
[01:26] <bschaefer> i see, hmm well Ill have to look at this tomorrow!
[01:26] <bschaefer> robotfuel, well that could work, i should go eat some dinner ..
[01:26] <bschaefer> robotfuel, thanks for the help today!
[01:28] <chjunior> what's this new package? xserver-xorg-xmir ?
[01:33] <chjunior> also, seem like the arrow at the top-left corner is gone, right?
[01:51] <TheDrums> I think the testing instructions need to be modified, had to manually pull in unity-system-compositor.
[01:55] <duflu> RAOF: Are you familiar with undefined symbol xorgMir? (https://bugs.launchpad.net/bugs/1205822)
[02:21] <chjunior> it seem like Mir or XMir has some memory leak. I might be wrong, but it feels like it starts up super fast, but gets slower as times goes by.
[03:00] <RAOF> duflu: That's failure to run against an XMir-enabled server.
[03:02] <duflu> RAOF: I feel you're just restating the problem. I'm still confused. But so long as you're aware of it...
[03:03] <RAOF> duflu: Specifically, it's failure to follow the instructions to pin the PPA ☺
[03:03] <RAOF> But I can make that failure more obvious, so shall.
[03:06] <chjunior> RAOF, is the arrow at the top-left corner gone?
[03:06] <RAOF> chjunior: Yes
[03:06] <RAOF> Now the only way to tell is (a) by checking logs, or (b) hitting Ctrl-C :)
[03:07] <chjunior> haha, that's the reason for the question
[03:07] <chjunior> RAOF, what ctrl-c should do? Nothing happened here
[03:07] <RAOF> Oh, has that fix propagated? Yay!
[03:08] <RAOF> chjunior: It would have killed mir
[03:08] <chjunior> I guess it's fixed then :P
[03:08] <chjunior> which logs should I look at? R
[03:08] <chjunior> RAOF,
[03:09] <RAOF> chjunior: /var/log/Xorg.0.log, or you can run ‘xrandr -q’ and check for XMir Mode Of Death!
[03:10] <RAOF> I'm going to be sad when we have actual xrandr support and I can no longer call it the Mode Of Death.
[03:10] <chjunior> :) That's a good name
[03:10] <duflu> There is always something new that you can declare "of death!"
[03:12] <RAOF> But probably not in a user-visible string
[03:12] <RAOF> ☺
[03:14] <chjunior> RAOF, is stuff still going to the output buffer? like password and everything I type
[03:14] <RAOF> I'm not sure. I think the fix for ctrl-C should have also fixed that, but I've not tested it.
[03:15] <RAOF> You still can't user-switch, though.
[03:15] <RAOF> Which reminds me - racarr!
[03:15] <RAOF> racarr: How goes notify-on-focus? ☺
[03:17] <RAOF> Sweet! I win the ‘able to get dma-buf size out of the kernel’ award!
[03:22] <chjunior> RAOF, and I win the "Trying things someone waned were buggy just to see the world burn"
[03:23] <chjunior> had to restart after user-switch
[03:23] <chjunior> do you think XMir will be ready for 13.04 performance-wise ?
[03:27]  * duflu wonders how long is too long for stress testing to run on armhf
[03:45] <RAOF> chjunior: 13.04? A bit late for that :)
[03:45] <chjunior> wow, sorry, messed up with numbers
[03:46] <RAOF> chjunior: 13.10? Yes; there's some subtlety in GLX bypass that needs to be worked out, but we should be able to get approximately 0% performance penalty on composited desktops.
[03:46]  * duflu cancels all real-life for the next few weeks to make that happen :/
[03:47] <chjunior> I thank you all duflu, RAOF and others for that
[03:51] <RAOF> duflu: Indeed, got some time to talk composite-bypass?
[03:52] <duflu> RAOF: Depends how far down the rabbit hole you want to go :)
[03:52] <RAOF> Just a high-level discussion of how composite bypass interacts with nested compositors
[03:52] <RAOF> (Of which XMir is one)
[03:53] <RAOF> Because currently the answer to that appears to be ‘badly’
[03:53] <duflu> RAOF: I will need to refresh my memory of the bypass work done so far
[03:54] <RAOF> Because for nested compositors, composite bypass means “hand out the buffer we received from our server to a client”, and that has a bunch of failure modes.
[03:54] <duflu> RAOF: No, that's the "old" method I'm not using any more
[03:55] <RAOF> duflu: Right - but you're not doing a nested compositor.
[03:55] <duflu> RAOF: You're right. That issue needs to be solved/avoided in the nesting logic. I found it problematic so didn't do that
[03:55] <RAOF> duflu: Since you're running on the hardware you *can* choose to allocate scanout-ready buffers.
[03:56] <duflu> RAOF: Yes, the conditional-ness of that is TODO :)
[03:56] <duflu> Presently everything can be scan-out
[03:57] <RAOF> So, do you have any thoughts about solutions for nestedness?
[03:58] <duflu> RAOF: It actually makes very little sense to pass any buffers from the Display classes down to the client. Because the buffer allocator can of course make a scanout capable buffer without Display* getting involved
[03:58] <duflu> Not to mention you can't trust clients...
[03:59] <duflu> RAOF: My present approach accepts *any* scanout capable buffer, which can come from the client or can come from the Display (default compositing)
[03:59] <RAOF> But, on the other hand, nested bypass *requires* that you send the buffer you receive to the client.
[04:00] <duflu> RAOF: Why? that's got high risk of the client misbehaving and breaking the server, surely?
[04:00] <RAOF> How do you bypass if the client isn't rendering to a buffer acquired by the nested server?
[04:01] <RAOF> ie: The nested server needs to call mir_surface_swap_buffers() on something. What is that something?
[04:02] <duflu> RAOF: Bypass doesn't care which server created the buffer. It still works
[04:02] <duflu> With obvious memory management trickery
[04:02] <RAOF> How does the buffer get from the nested compositor to the display?
[04:03] <RAOF> It *sounds* like you're talking about client-allocated buffers, which would indeed work fabulously for this.
[04:03] <duflu> RAOF: Yes I was thinking that
[04:03] <duflu> Just doesn't work with mirserver's memory management yet
[04:04] <duflu> Because the client (which is a server) is the one allocating the buffer
[04:04] <RAOF> Indeed.
[04:05] <RAOF> If we can do *that* then bypass is easy, and xmir is easier.
[04:05] <RAOF> It was my understanding that this was not on the table.
[04:05] <RAOF> Sounds like a job for Afternoon Team Meeting™!
[04:06] <RAOF> Oh. Is that going to occur with everyone in IOM?
[04:10] <duflu> Maybe... ?
[05:20] <racarr> Are we having the weekly this weeting?
[05:20] <racarr> Oh that's what was just being discussed :) Hi
[05:20] <racarr> RAOF: client-focus-notifications...I dunno
[05:20] <racarr> I feel as if the branch is unpopular in a profound way :p it needs more review
[05:21] <racarr> and maybe better ideas
[05:21] <racarr> I kind of feel like it's done
[05:50] <duflu> RAOF: I kept thinking about it over lunch...
[05:50] <RAOF> duflu: Oh, and?
[05:50] <duflu> and I don't think there are any fundamental conflicts between nesting and bypass...
[05:50] <duflu> ... just that both at once will require more work so as to not negate bypass benefits
[05:51] <duflu> ... which should be a simple matter of implementing my DisplayBuffer changes
[05:51] <duflu> I mean, any "NestedDisplayBuffer" should be enhanced to implement bypass like GBM does now
[05:52] <duflu> It should all just work so long as both servers use the same logic and enable bypass at the same time
[05:52] <RAOF> I still don't see how?
[05:53] <RAOF> I mean, you can *certainly* handle bypass on the outer compositor; that works regardless of the client.
[05:54] <duflu> RAOF: And once implemented in the inner compositor (implemented for NestedDisplayBuffer or whatever), then why wouldn't it work?
[05:54] <RAOF> What do you mean by "implemented" in this case?
[05:55] <duflu> RAOF: It's a new function I've added to the DisplayBuffer interface. You can safely stub it or implement for bypass support
[05:55]  * RAOF looks at the DisplayBuffer interface
[05:55] <duflu> Though I may be relying on memory too much
[05:56] <RAOF> I think the fundamental problem is that for bypass the inner compositor *is not* allocating a DisplayBuffer
[05:56] <duflu> RAOF: It has to... for N-buffering and to ensure you're not trusting clients
[05:57] <RAOF> Which turns around our buffer allocation strategy.
[05:57] <RAOF> You are asserting that server-allocated buffers are incompatible with bypass.
[05:57] <robert_ancell> RAOF, duflu, kdub, racarr, hikiko, alf__, thomi, meeting..
[05:58] <duflu> RAOF: Only what you're proposing nesting should do turns things around. And in an unsafe way
[05:58] <robert_ancell> Not sure how the WiFi will hold up here though
[05:58] <RAOF> duflu: Actually, I think with triple buffering *and* 2 buffers available client-side it can be safe.
[05:59] <RAOF> Hm, maybe.
[05:59] <duflu> RAOF: On the other hand, I will be free to fully discuss bypass in about 24 hours :)
[06:00] <mlankhorst> morning
[06:00] <robert_ancell> RAOF, kdub, racarr...
[06:00] <RAOF> robert_ancell: Logging in to a session with webcam.
[06:00] <robert_ancell> RAOF, ack
[06:09] <RAOF> Am I appearing in the hangout?
[06:09] <RAOF> I see a bunch of people, but no audio or video.
[06:10] <robert_ancell> RAOF, you show a photo
[06:48] <racarr> abnormally interested in buffers today
[06:48] <racarr> still thinking about bypass
[06:48] <RAOF> Please do.
[06:49] <RAOF> There's also the extra special case of XMir DRI2 bypass to consider, which has the extra frission of not allowing protocol changes!
[06:50] <racarr> There is? -.-
[06:50] <RAOF> (Although the DRI2Invalidate event will be useful there)
[06:50] <RAOF> racarr: Well, the case we're aiming for with XMir is to have Unity fullscreen, drawing directly on the framebuffer, for ~0% XMir overhead. Same for fullscreen GL games.
[06:52] <duflu> RAOF: Actually, I think we can afford to enforce the extra restrictions on clients when the client is a nested server (hence very few of them, and controlled by us)
[06:52] <duflu> But generalized bypass does not have that luxury
[06:52] <RAOF> duflu: With the unfortunate DRI2 case above :)
[06:53]  * duflu has no idea what the DRI2 issue is still
[06:53] <RAOF> If we want ~0 performance regression on fullscreen games, which we obviously do, then we need to give the DRI2 client (ie: the fullscreen game) a framebuffer to render on.
[06:54] <racarr> RAOF: Ok yes
[06:54] <racarr> I was thinking of that
[06:55] <racarr> as the case
[06:55] <RAOF> This means we need to hand out something that will become the framebuffer in response to DRI2BufferBackLeft
[06:55] <duflu> I cannot comment further outside of pure speculation :)
[06:55]  * duflu goes to find coffee
[07:07] <duflu> Hmm, at what point does the stack depth affect performance?... I keep seeing large stacks in mirserver up to 72 frames deep...
[07:08] <dholbach> good morning
[07:08] <duflu> Morning dholbach
[07:08] <dholbach> hey duflu
[07:12] <duflu> racarr: Careful with asking community contributors to "fill in testing". Sometimes that can scare people off, or at least make them lost interest to the point of never completing the work. It's a fine line.
[07:12] <duflu> -lost +lose
[07:14] <duflu> ... but it's good and right to ask at least once, I guess. The question then becomes "is the work important enough to us that we fill in the testing ourselves?"
[07:38] <tvoss_> good morning :)
[07:39] <RAOF> Eeeloe,
[07:43] <tvoss_> duflu, ping
[07:43] <duflu> tvoss_, pong
[07:45] <tvoss__> RAOF, ping
[07:45] <duflu> tvoss__, pong?
[07:45] <RAOF> tvoss__: pong
[07:45] <RAOF> tvoss__: 17:43 <RAOF> Got a kernel patch to work, fixing up some xserver packaging, the ppa doesn't seem to have caught fire...
[07:46] <tvoss__> RAOF, ah cool, what does the kernel patch do?
[07:47] <RAOF> Add enough llseek support to dma-buf to let us get the size of one
[07:47] <tvoss__> ack
[07:48] <RAOF> Which was blocking radeon support for egl-platform-mir upstream\
[07:48] <tvoss__> RAOF, awesome
[07:54] <tvoss__> RAOF, want me to give the intel driver update a spin?
[07:55] <RAOF> The shiny shiny ickle one? I haven't pushed that anywhere yet.
[07:56] <RAOF> I need to go and make dinner; I'll be on later.
[07:56] <tvoss__> RAOF, yup
[07:56] <tvoss__> RAOF, I was talking about http://bazaar.launchpad.net/~mir-team/mir/xf86-video-ati-vladmir/revision/2539
[07:56] <tvoss__> RAOF, can I just compile it against the testing ppa?
[08:11] <tvoss_> duflu, so when using the switch branch with system-comp-testing, the usc just crashes
[08:12] <tvoss_> RAOF, ^ could you quickly verify?
[08:12] <duflu> That's different
[08:12] <duflu> tvoss_: Oh, I noticed yesterday I had changed the ABI without bumping the soname. Make sure *everything* is rebuilt
[08:12] <duflu> ... of libmirserver that is
[08:14] <duflu> tvoss_: Me forgetting to bump the soname means it's possible to accidentally forget to rebuild everything that uses libmirserver
[08:18] <tvoss_> duflu, that is, I need to rebuild usc, right?
[08:19] <duflu> tvoss_: Yes anything that uses libmirserver. It should have given you a runtime error (missing library) but won't because I forgot to bump the soname/ABI
[08:20] <duflu> tvoss_: I wasted hours last night for the same reason. tests crashing inexplicably
[08:20] <duflu> I'll fix it today...
[08:20] <tvoss_> duflu, cool, let me know when I can take a look
[08:21] <duflu> tvoss_: No need to wait for me. You can rebuild everything now
[08:21] <tvoss_> duflu, ack
[08:21]  * duflu is waiting on cross-compiles
[08:24] <duflu> robert_ancell: At what point can we not bump the server ABI any more? Seems like we have several activities in progress that will do so
[08:24] <duflu> -will +should
[08:25] <robert_ancell> duflu, we'll need to be ABI stable at release, but I think long term we'll just bump the soname every time we make a non-additive change and recompile u-s-c and unity-mir each time that happens
[08:25] <duflu> robert_ancell: Cool
[08:25] <robert_ancell> I don't think we need to worry too much about changing the ABI as long as we bump soname given the small number of libmirserver consumers
[08:26] <duflu> robert_ancell: Yes I forgot to bump and it's caused several people to forget to rebuild
[08:26] <robert_ancell> duflu, right now, we don't need to bump it - the system-compositor-testing PPA is manually kept in a safe state
[08:27] <robert_ancell> once u-s-c hits universe then we're solving that in jenkins with a dependency done by didrocks
[08:27] <robert_ancell> Long term, we'll rely on sonmae
[08:27] <duflu> robert_ancell: PPA rules don't help me while people keep playing with pre-release branches :)
[08:27] <robert_ancell> Just don't want to slow things down too much requiring the soname bumps and associated changes in debian/*
[08:28] <robert_ancell> duflu, who's doing that / what?
[08:28] <duflu> robert_ancell: I mean WIP branches (switch)
[08:28] <robert_ancell> i.e. running u-s-c from the PPA with a locally built version on Mir?
[08:29] <didrocks> robert_ancell: kgunn: btw, the ppa worked on ati and intel
[08:29] <didrocks> let me retry another run in a few
[08:30] <kgunn> didrocks: \o/ hells yeah
[08:30] <didrocks> let's cross fingers ;)
[08:30] <didrocks> and retry
[08:30] <kgunn> sure
[08:31]  * duflu suspects people are messaging each other from within the same physical room
[08:31]  * duflu thinks that's strange
[08:48] <didrocks> duflu: we don't want to interrupt the meeting
[08:48] <didrocks> duflu: but you are not that far from truth :)
[08:55] <mlankhorst> http://paste.debian.net/hidden/f5f6260b/ does this look ok? untested though
[08:57] <mlankhorst> oops, looks like it's wrong :p
[09:01] <mlankhorst> oh correct after all, weee
[09:16] <hikiko> alan_g, ping
[09:16] <alan_g> hikiko: hi
[09:16] <hikiko> hi :)
[09:16] <alan_g> How is it going?
[09:16] <hikiko> mmm fine in general but I have a question
[09:17] <hikiko> I tried to replace the create_nested_platform with the NestedPlatform constructor
[09:17] <hikiko> in the_graphics_platform()
[09:17] <alan_g> Yes
[09:18] <hikiko> but it seems that the lambda cannot return a deduced type
[09:19] <alan_g> You need to specify the return type explicitly
[09:20] <alan_g> See mir::DefaultServerConfiguration::the_input_report() for an example
[09:20] <hikiko> let me check it :)
[09:21] <hikiko> oh so you use []()->Type
[09:22] <hikiko> but this will cause a problem when I call create_platform isn't it?
[09:22] <hikiko> because I have a condition
[09:22] <hikiko> in non nested mode I return mg::Platform in nested mgn::NestedPlatform
[09:23] <hikiko> or I can use []()->mg::Platform
[09:23] <alan_g> hikiko: you must return shared_ptr<Platform>
[09:23] <hikiko> ah the abstract type
[09:23] <hikiko> ok :)
[09:23] <alan_g> And NestedPlatform must extend Platform
[09:24] <hikiko> (sorry I am not so familiar with lambdas)
[09:24] <alan_g> See mir::DefaultServerConfiguration::the_input_report() for an example
[09:24] <hikiko> yes that's done :)
[09:24] <hikiko> ok
[09:24] <hikiko> thanks a lot
[09:32] <mlankhorst> kgunn: been working on it, but tests were failing since they didn't handle the extra ops :P
[09:33] <kgunn> mlankhorst: thanks!
[09:45] <mlankhorst> http://paste.debian.net/hidden/2d845546/ can you test that one? :P
[09:55] <robert_ancell> alf__, alan_g, tvoss_, can you add some info to bug 1203590 if you know what we need from lttng/systemtap
[10:01] <Saviq> duflu, re: bug #1206633
[10:01] <Saviq> duflu, I was running as root
[10:02] <duflu> Saviq: OK. Just means it's not a trivial mistake :)
[10:04] <mlankhorst> bah one unfortunate side effect is that VT switching no longer seems to work..
[10:06] <Saviq> duflu, yeah, I had robert_ancell next to me for immediate help, but we didn't get anywhere, hence the bug
[10:07] <hikiko> alf__,
[10:07] <alan_g> alf__: in multimonitor-gbm-cursor should I be seeing any difference in behaviour? Or  does that need other changes?
[10:08] <hikiko> ^ that was my question :D
[10:08] <duflu> alan_g: What's the recommended way to ignore uninteresting calls, in tests which really should have no expectation of them?
[10:09] <alan_g> duflu: to stub the calls, not mock them
[10:09] <duflu> alan_g: Mixed stub methods in a mock class?
[10:10] <duflu> Problem is I have two test cases which needs it mocked. The rest of the tests shouldn't care ("not interested")
[10:10] <duflu> -needs +need
[10:11] <alan_g> duflu: you could, e.g. derive a mock class for the test from a shared stub class.
[10:12] <duflu> Sounds like overkill but would work I guess
[10:12] <alan_g> duflu: there's also NiceMock (which IMO is overused in our code)
[10:12] <mlankhorst> meh w/e, this fixes control-C at least..
[10:13] <duflu> alan_g: Wait, no. I need the mock class in every test. Just one method I wish to ignore in most (it's called during destruction)
[10:14] <alan_g> duflu: Then it's probably easier to have the one class and set expect AnyNumber in the constructor
[10:15] <duflu> alan_g: I thought I similar in SetUp and got bogus failures. Maybe the constructor is indeed a better idea
[10:15] <duflu> I thought I *tried*
[10:16] <alan_g> That should work too
[10:24] <alan_g> hikiko: you have review comments - mir.nested-platform-constructor
[10:26] <hikiko> thanks alan_g let me see :)
[10:28] <mlankhorst> does mir disable xserver vt switches?
[10:30] <kgunn> mlankhorst: w/o you proposed change in http://paste.debian.net/hidden/2d845546/
[10:30] <kgunn> i had the vt problem already
[10:31] <mlankhorst> looks like strictly speaking xserver should be spawned with -sharevts -keeptty  :P
[10:34] <mlankhorst> considering at this point xserver no longer controls the server
[10:39] <duflu> So close to finishing, but out of time
[10:50] <mlankhorst> https://code.launchpad.net/~mlankhorst/mir/setsid/+merge/177800 try 2
[10:57] <didrocks> kgunn: do you know on which part of boost you build-dep on?
[10:57] <didrocks> kgunn: because right now the package deps on libboost-all-dev which is now in universe
[10:57] <didrocks> and there is a discussion on #ubuntu-devel to only deps on what it's needed
[10:58] <xnox> i see that from linking it's: libboost-program-options-dev libboost-system-dev but there might be other header/template only portions of boost used.
[10:59] <xnox> -lboost_chrono -lboost_date_time -lboost_filesystem -lboost_system -lboost_thread -lboost_program_options -lboost_regex
[11:03] <didrocks> robert_ancell: hey
[11:03] <robert_ancell> didrocks, hello
[11:04] <didrocks> robert_ancell: so I don't see libboost-all-dev in the MIR
[11:04] <didrocks> https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1203207
[11:04] <didrocks> and Mir depends on it
[11:04] <didrocks> the discussion we just had on #ubuntu-devel is that we should of course only build-dep on what we rely on
[11:04] <didrocks> 11:58:43          xnox | i see that from linking it's: libboost-program-options-dev libboost-system-dev but there might be
[11:04] <didrocks>                        | other header/template only portions of boost used.
[11:04] <didrocks> 11:59:06          xnox | -lboost_chrono -lboost_date_time -lboost_filesystem -lboost_system -lboost_thread
[11:04] <didrocks>                        | -lboost_program_options -lboost_regex
[11:04] <robert_ancell> didrocks, ok, we can switch to that
[11:04]  * xnox is doing a test build with ^
[11:05] <didrocks> xnox: thanks man :)
[11:05] <sil2100> \o/
[11:05] <didrocks> robert_ancell: if so, we'll probably have to update the MIR as well (eventually)
[11:05] <didrocks> IIRC filesystem wasn't in main last time I checked
[11:06] <sil2100> hm, interesting though - libboost-all-dev had to be in universe like, since longer?
[11:08] <xnox> a long time ago mpi was not wanted in main, so because of that -mpi- portion is split into universe, the rest source packages are in main (if there are rdepends) some of the binary packages might be in universe if there are no rdepends.
[11:08] <xnox> if archive reorg ever happens, this mess with two source packages for default boost will go away.
[11:09] <xnox> so build passes & all unit tests pass (build-time tests) \o/
[11:11] <sil2100> Yeaaa
[11:12] <sil2100> robert_ancell: anyway, strange thing that it wasn't noticed earlier that libboost-all-dev is in universe - I didn't see it mentioned in the MIR too!
[11:12] <robert_ancell> sil2100, yeah, I think it was missed because the source package is in main, but not all the binaries
[11:15] <kgunn> mlankhorst: i was going to try your mp...but now we got an issue with the boost version in main :-/
[11:18] <xnox> robert_ancell: https://code.launchpad.net/~xnox/mir/boost-split/+merge/177804
[11:19] <robert_ancell> xnox, awesome, thanks!
[11:19] <xnox> sil2100: robert_ancell: so chrono & regex will be "rescued" from universe -> main. but that's ok, cause the source package they are build from is in main already. All others are in main already. No M.I.R. is needed for those
[11:19] <robert_ancell> xnox, just added the note how we don't need the debian/changelog entry. Otherwise looks good
[11:23] <xnox> robert_ancell: well the daily landing should be able to use it correctly..... unless you are not using daily landing =)
[11:30] <xnox> robert_ancell: dropped changelog entry.
[11:37] <robert_ancell> mlankhorst, I fixed that MP you made - it is rebuilding
[11:46] <mlankhorst> ok
[11:47] <hikiko> for some reason I cant trigger a jenkins rebuild
[11:48] <hikiko> did anyone else have the same problem?
[11:52] <alan_g> hikiko: Not logged in over VPN?
[11:52] <hikiko> no
[11:52] <hikiko> I tried from the web interface
[11:52] <hikiko> do I need a Canonical's IP for this?
[11:53] <alan_g> You need to log into the web interface via the VPN
[11:54] <hikiko> I see
[13:19] <alan_g> hikiko: Do you have a plan for what to do next?
[13:20] <hikiko> alan_g, I was about to push the fix and ask you
[13:20] <hikiko> shall I continue the nested platform or do the native one first?
[13:22] <alan_g> hikiko: I'd imagine that writing the nested one would identify the functions needed from the native one.
[13:25] <hikiko> alan_g, alf__ suggested that the nested platform will keep a pointer to the underlying native platform (mg::Platform => either GBM or Android) and call the native funct when necessary, I guess your idea is that I will add a fill_ipc, get_ipc, create_buffer_alloc... etc in the NativePlatform class and call these?
[13:26] <hikiko> sorry :s/NativePlatform class/native platform interface
[13:26] <alan_g> hikiko: Yes. (If we end up with NativePlatform being identical to Platform we can merge them.)
[13:26] <hikiko> the native platform interface will end up to call the GBM/Android functions?
[13:27] <hikiko> oh, ok :)
[13:27] <alf__> hikiko: alan_g: I think that the NativePlatform interface will turn out to be very close to mg::Platform, since we mostly want to relay requests
[13:27] <alf__> hikiko: alan_g: but we can decide later, as Alan suggests
[13:28] <hikiko> yes, maybe I could just keep the create_native_platform and create a 2nd constructor for each platform
[13:28] <hikiko> ok we ll see
[13:30] <alan_g> hikiko: I'm assuming your earlier spike gives you enough to write a first draft of the nested code.
[13:31] <hikiko> yes, although in the previous branch I used to keep a ptr to the native mg::Platform
[13:31] <hikiko> there was no NativePlatform interface
[13:31] <hikiko> but it's not a big deal to add the methods to the native platform class
[14:26] <alf__> mlankhorst: @setsid, does the change also affect vt switching combinations (Alt+F*) or only Ctrl-*?
[14:35] <mlankhorst> it ignores all keyboard input in mir, would need to actually handle input for it to be useful
[14:35] <mlankhorst> I don't know what the previous behavior was, though..
[14:39] <mlankhorst> xorg seems to generate XF86Switch_VT_1 etc, but I have no idea why it does, and not simply change to the appropriate vt
[14:43] <alf__> mlankhorst: ok, so we need to be able to handle at least VT switching key combinations ourselves before this lands, and also add a kill Mir key combination, otherwise development will become painful
[14:48] <mlankhorst> ... while you still run with --disable-input ?
[14:49] <robotfuel> with openarena benchmarks xmir is faster than x on intel now
[14:58] <mlankhorst> yeah but getting 400 fps on glxgears, so dno how reliable that is :p
[16:11] <racarr> MORNING
[16:11] <kdub_> too early for shouting :)
[18:57] <racarr> Lunch break :) will be a little long (~1 hour) little sister is off exploring down town SF and got a little spooked so I am going to go meet up with her :)
[20:49] <racarr>  Back
[21:02] <crippledmonk> just installed daily and added ppa for mir. did apt-get update, reboot etc. Is there anything I should do in order to verify it's using mir?
[21:05] <bschaefer> crippledmonk, if you want to verify tou are using xmir do: ps aux | grep mir
[21:05] <bschaefer> s/tou/you
[21:10] <bregma> ps -ef | grep unity-system-compositor
[21:13] <crippledmonk> bschaefer: I got this   todd      4166  0.0  0.0   4444   824 pts/0    S+   14:11   0:00 grep --color=auto mir
[21:14] <bschaefer> crippledmonk, nothing else?
[21:14] <bschaefer> crippledmonk, make sure you have unity-system-compositor installed
[21:14] <crippledmonk> just a sudo apt-get unity-system...... in term
[21:15] <bschaefer> yup!
[21:15] <bschaefer> you can also check by doing apt-cache policy unity-system-compositor
[21:16] <crippledmonk> it gave me errors...unity-system-compositor : Depends: libmirserver0 (= 0.0.8+13.10.20130730bzr898saucy0) but 0.0.8+13.10.20130731.2-0ubuntu1 is to be installed
[21:16] <crippledmonk> E: Unable to correct problems, you have held broken packages.
[21:16] <bschaefer> :(, hmm unmet dependency
[21:16] <bschaefer> bregma, is that a better way to look for mir?
[21:17] <bregma> if unity-system-compositor is not running, xmir is not running on mir
[21:17] <bschaefer> crippledmonk, can you do an apt-cache policy libmirserver0?
[21:17] <bregma> does xmir actually run with proprietary drivers?
[21:17] <bschaefer> and, pastebin it here: paste.ubuntu.com
[21:18] <bschaefer> bregma, not that I know of, but if u-s-c is running, you'll have the mir server running as well
[21:18] <bregma> exactly, but if you;re running the proprietary nVidia or AMD drivers, you're not going to see that
[21:18] <bschaefer> bregma, but you wont see u-s-c either though will you?
[21:19] <bregma> no, exactly
[21:19] <bschaefer> o yeah, well he has a broken package soo hes going to have to downgrade the libmirserver :)
[21:19] <bregma> so, if crippledmonk is running a proprietary video driver he may be disappointed
[21:19] <bschaefer> right
[21:19] <bregma> he should make sure he's using the right ppa
[21:19] <crippledmonk> done.
[21:19] <bschaefer> he really should be using u-s-c testing ppa and not daily
[21:20] <bregma> because daily is always broken
[21:20] <bschaefer> yeah
[21:20] <crippledmonk> I wiped my HDD  did install and that's it
[21:20] <crippledmonk> well not quite I followed this guide. http://www.ubuntukiller.com/2013/07/install-and-test-new-mir-in-ubuntu-1013.html
[21:21] <bschaefer> crippledmonk, soo, you should purge the daily build ppa and use this one
[21:21] <bschaefer> https://launchpad.net/~mir-team/+archive/system-compositor-testing
[21:21] <crippledmonk> accept I did fresh install not upgrade
[21:21] <bschaefer> crippledmonk, o so you are using this ppa? mir-team/system-compositor-testing
[21:21] <bschaefer> that wont hurt you :)
[21:23] <crippledmonk> already deleted working on change
[21:24] <bschaefer> crippledmonk, alright, use purge-ppa
[21:24] <bschaefer> it cleans things up nicely
[21:24] <bschaefer> err ppa-purge :)
[21:25] <crippledmonk> it's not working...
[21:26] <bschaefer> crippledmonk, hmm whats not?
[21:26] <seb128> bschaefer, bregma: hey, just checking, how are the ibus 1.5 fixes going? got merged in?
[21:26] <crippledmonk> sudo ppa-purge :mir-team/system-compositor-testing
[21:26] <bschaefer> seb128, approved and waiting to be merged!
[21:27] <bschaefer> sudo ppa-purge ppa:mir-team/system-compositor-testing
[21:27] <bschaefer> try that
[21:27] <bschaefer> crippledmonk, ^
[21:27] <seb128> bschaefer, great, thanks ;-) (sorry for the ping on -mir, I though that was -unity)
[21:27] <bschaefer> seb128, no worries :)
[21:27] <crippledmonk> command not found ppa-purge
[21:28] <bschaefer> crippledmonk, right, you should install it :)
[21:28] <bschaefer> sudo apt-get install ppa-purge
[21:28] <bschaefer> crippledmonk, but... umm you want that ppa
[21:29] <bschaefer> crippledmonk, so you have this ppa right? ppa:mir-team/system-compositor-testing
[21:29] <crippledmonk> now it's purging
[21:29] <bschaefer> crippledmonk, I thought you had installed a different ppa...to many! sorry
[21:30] <bschaefer> crippledmonk, sooo once you purge, you'll want to install it again :)
[21:30] <bschaefer> http://www.olli-ries.com/running-mir/
[21:30] <bschaefer> these are the same instructions, but a bit neater
[21:35] <crippledmonk> Well, Getting ready to restart lightdm according to guide...Will see.