[00:44] RAOF, hey, how would one force mir to do double buffering? Seeing interesting issues/flashing (looks like the third buffer might be to much?) [00:45] bschaefer: I think you need to twiddle with the code to do that. [00:45] RAOF, cool, ill dig into that :). Thanks! [00:46] bschaefer: Also, on desktop, bypass *requires* triple buffering. But you don't necessarily care about that if you're just debugging. [00:46] RAOF, yeah, im just checking if its my code, or the apps code [00:47] bschaefer: You could also check the age on the buffer, client side, to detect if it's being triple buffered. [00:47] as this is the only time i've seen the need for a frame damage using opengles + sdl [00:47] thats a good idea as well [00:47] RAOF, testing qemu out [00:48] the current image i see: http://i.imgur.com/RZg6uhx.jpg (it only updates the textures on whats changed) [00:50] Whee! [00:50] :), it'll be nice to get working haha [00:50] Also, maybe tiling? [00:51] Hm [00:51] hmm, i think that image is after its freaking out [00:51] when i throw a clear in [00:52] i can see the textures updating only where somethings changed + width of the window [00:52] so each frame, it updates a chunk of the window, but adding in buffers it seems to be flashing [00:53] possibly an alpha issue? [00:53] as i was running into an alpha issue with the pixel format before... [00:54] (as with RGBA8888 selected for the texture + surface, i was getting an empty/grey window) [00:54] forcing RGBX8888 let me see the textures [01:00] Hm. [01:00] RAOF, ill show you two pictures of one clearing each frame, and one doing it how it normal is [01:01] RAOF, otherwise ill debug what i can, and show you in malta [01:01] Yeah. Yay Malta! [01:01] its going to be to warm :( [01:01] but yay! [01:02] RAOF, glClear before each from being drawn: http://i.imgur.com/MYUcRda.jpg [01:03] RAOF, no Clear: http://i.imgur.com/J4IiccE.jpg [01:03] but yeah, ill see what i can find out :) [01:03] * bschaefer should have use mir screen cast [01:03] :) [01:37] bschaefer: I see nice screenshots. The gaps could well be Qemu's fault. But also check you're not relying on buffer-age. Just in case... [01:43] duflu, sounds good [01:43] duflu, im not 100% the issue, but ill dig around some more :) [01:43] bschaefer: Also see if SDL2 on X11 has the same bugs ;) [01:44] Qemu's SDL2 is new and possibly buggy in damage tracking [01:45] duflu, works fine on X11 :( [01:45] well actually [01:45] i cant get the ubuntu iso install to come up [01:45] possibly a bug there yeah [01:45] bschaefer: OK then any simple SDL2 demos have similar issues? [01:45] duflu, nope [01:45] only sdl1.2 [01:45] with software rendering [01:46] which i fixed with frame damage [01:47] duflu, i also dont know qemu very well or how to use haha [01:47] bschaefer: BTW if the mouse doesn't interact properly try: qemu -usbdevice tablet [01:47] o nice, i've not even gotten to try the mouse out [01:47] as the keyboard works [01:47] so thats what i've been tessting [01:47] Running Qemu in tablet mode will avoid it wanting grabs (which Mir lacks) [01:49] yeah, thats something racarr__ brought up :), my main goal was to make pixels look good [01:49] duflu, the only way to get sdl2 running as well is disable gtk and set sdl to 2.0 [01:49] * bschaefer hopes its in their damage code [01:55] bschaefer: You mentioned 1.2... I thought you didn't support 1.2? [01:55] If you do then Qemu's SDL1.2 support is much more mature [01:55] duflu, i have a branch for it, but they aren't accepting patches :( [01:55] bschaefer: Oh, fair point [01:55] duflu, another reason, is they are creating a layer to turn 1.2 SDL API to 2,.0 [01:55] 2.0 [01:56] soo onces that layers there, we'll get all of 1.2 for free :) [01:56] but yeah, i should test it out on 1.2 [02:34] To the luncheon wagon! === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [06:20] ping anpok [06:24] pong [06:25] i have the same gdb issue you had [06:25] or still have? [06:26] anpok: Yeah, it's annoying but in other news... [06:27] anpok: Can you check this out? Seems to have only regressed last night: https://bugs.launchpad.net/bugs/1321077 [06:27] Ubuntu bug 1321077 in Mir "[regression] [input] Scroll events are now always zero: event.motion.pointer_coordinates[0].vscroll" [High,Triaged] [06:27] oh [10:03] anpok: alan_g: Have you seen https://bugs.launchpad.net/mir/+bug/1321215 locally? [10:03] Ubuntu bug 1321215 in Mir "CI failures in CustomInputDispatcherFixture.custom_input_dispatcher_gets_started_and_stopped" [High,New] [10:05] alf_: no. But I've not been looking for it. [10:06] alan_g: I wasn't looking for it either, it came looking for me :) [10:06] * alan_g thinks CustomInputDispatcherFixture.custom_input_dispatcher_gets_started_and_stopped is a redundant name [10:06] alf_: let me grab latest updates and try it === jono is now known as Guest73754 [10:13] alf_: this is just running on the phone? Or do you see it on desktop too? [10:13] alan_g: I can reproduce it locally on the desktop 100% [10:13] alf_: me neither [10:14] alf_: I hit it after 232 iterations on desktop [10:14] alan_g: anpok: thanks, I have started investigating it, stay tuned [10:15] anpok: when/where is InputDispatcher.start()/stop() supposed to be called ? [10:16] alf_: while you're there: CustomInputDispatcher.gets_started_and_stopped would be a better name. [10:16] alf_: as part of the DisplayServer start and stop proces.. [10:16] alan_g: ack [10:16] oh it seems to not wait for completion [10:44] alf_: when I terminate the server process manually it did not fail within 2000 tries (which it did before) but I thougt the text fixture tear down does that already.. [10:44] anpok: I am almost done with an alternative solution, I will ping you [10:44] oh it still fails [10:45] just need to have more load [10:45] ok [11:23] hey guys, we seem to have an issue on android with the new Qt 5.3: https://bugs.launchpad.net/unity8/+bug/1321189 [11:23] Ubuntu bug 1321189 in Unity 8 "Launcher is black on Qt 5.3" [High,Triaged] [11:24] for some reason ShaderEffectSource, which is a component in QML that is, in essence, creating a texture from a QML element, for consumption in a shader [11:24] stopped working [11:25] everywhere it's used, it goes black [11:25] it's fine on X and on Mir on desktop, but affects all our three android devices [11:26] and we're out of our depth on this now [11:26] Saviq: are any shader errors reported on the console? [11:27] greyback, no [11:28] Saviq: and even a simple qml file using a ShaderEffectSource has this problem? [11:28] greyback, yeah http://paste.ubuntu.com/7492386/ [11:28] greyback, is black instead of red, see https://bugs.launchpad.net/unity8/+bug/1321189/+attachment/4116145/+files/mako.png vs. https://bugs.launchpad.net/unity8/+bug/1321189/+attachment/4116146/+files/mako_good.png [11:28] Ubuntu bug 1321189 in Unity 8 "Launcher is black on Qt 5.3" [High,Triaged] [11:28] fooking barrier [11:32] Saviq: first step I'd take: capture an API trace - https://github.com/apitrace/apitrace [11:32] is available in the repos [11:35] anpok: https://code.launchpad.net/~afrantzis/mir/fix-1321215/+merge/220228 [11:44] alan_g: Yo! Are you available to talk about 1hz-rendering? [11:45] RAOF: If you want me to [11:46] I've written a follow-up comment. After you've read that, what would you like to see done? [11:47] * alan_g goes to look [11:51] greyback: There'll be a shiny new apitrace 5.0 in the repos soon, too :) [11:51] RAOF: good, because 4.0 chokes on eglBindAPI :) [11:51] greyback: That might be awkward [11:51] * greyback wants to try vogl too [12:07] RAOF: I'm not convinced by the abstraction or the naming. But I do like the overall solution. I could just abstain. [12:08] alan_g: I'll need to fix the merge conflict anyway (tomorrow); perhaps alf_ could weigh in, also. [12:09] alan_g: Adding the last bits of frame dropping policy to FrameDroppingPolicy seems sensible to me, at least. [12:19] Maybe SwapStateObserver <- FrameDroppingPolicy <- TimeoutFrameDroppingPolicy? [12:21] That would make sense. BufferQueue would still construct a FrameDroppingPolicy from a FrameDroppingPolicyFactory, though. It'd just store it in a std::unique_ptr rather than std::unique_ptr === alan_g is now known as alan_g|lunch [12:31] * RAOF → sleep [13:02] greyback, so yeah, it choked here on eglBindAPI [13:02] greyback, pointers? [13:02] Saviq: recompile qtubuntu without that call. Frankly, that call should not be happening on arm [13:03] oh ya [13:03] y [13:03] RAOF, anywhere I could get the 5.0 of apitrace already? [13:03] Saviq: tried it, chokes there too [13:03] grr [13:03] sorry [13:04] ok me builds [13:08] alf_: alan_g|lunch AlbertA ... so do i understand it correct on 1hz-rendering-always MP, we seem ok with the approach for putting policy in bufferqueue, but we would want a follow up second effort for shell to be able to override policy ? [13:09] sorry if i missed any irc chat on this...but i've been keeping an eye on this one, hoping we'll land it soon (as to put some road mileaage on it before promoting) === alan_g|lunch is now known as alan_g [13:22] kgunn: There's no real objection to separating a "policy" out - just a lack of clarity about what's separated out and how best to name it. (Although IMO separating out a configurable "policy" is premature until we can see what (if anything) needs separating out.) [13:25] alan_g: ack [13:30] You could have missed some IRC between RAOF and me about 90mins ago: There'll be a new version his "tomorrow". He's got some conflicts to address before it can land, and I'm happy enough with the general approach not to block. [13:33] alan_g: thanks [13:33] greyback: so when you overrride displaybuffercompositor [13:33] will you auto-magically also use hwc ? [13:33] or i'm guessing you'll need to "do some effort" there [13:34] (which is hopefully a copy paste) [13:34] kgunn: no, effort needed. bypass might work tho [13:34] ah...cool [13:34] so we architected it right :) [13:59] greyback, btw, I filed https://code.launchpad.net/~mterry/unity-mir/dont-hide-focused-apps/+merge/220130 yesterday [13:59] About the hiding of suspended apps we talked about === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [14:31] kgunn: not so much sheller but other parts of the system should AUGMENT the policy [14:31] kgunn: meaning the policy should only be activated on display off/occlusion events === alan_g is now known as alan_g|tea === alan_g|tea is now known as alan_g [15:01] mterry: I added comment on your MR === seb128_ is now known as seb128 [15:53] greyback, (kgunn) with that convo about getting bypass or hwc to work about 3h ago... would something like this (which works with hwc) get hwc to work for you? [15:53] http://bazaar.launchpad.net/~kdub/mir/future-default-display-buffer-compositor/view/head:/src/server/compositor/default_display_buffer_compositor.cpp [15:54] thats my integrated hwc-working branch (stuck behind some other branches at the moment) [15:54] I also want to rip out that weird lines 60-62 and lines 82-86 [15:57] kdub_: almost, main issue I see is that your use of HWC is an if/else. I'll probably have to render, but also call post_renderables_if_optimizable(renderable_list) - because the scenegraph contains things that are not Renderables [15:58] e.g. a non-fullscreen app, for iteration one, the panel is not in its own surface, but drawn explicitly with GL calls [16:00] greyback, ack, that's the key, is to condense things into renderables where its simple to do so, and use gl where it can't be represented by a RenderableList === chihchun is now known as chihchun_afk [16:00] kdub_: agreed, but this is iteration 1 [16:00] because that abstracts the hwc stuff away, and the compositor writer just thinks in terms of 'can this be a RenderableList' [16:00] kdub_: so in time, we can move to using RenderableList as much as possible [16:00] but we're not going to be there for a while yet [16:01] greyback, cool, just checking that its still pulling in a sensible direction [16:01] kdub_: yep, no objections so far === dandrader is now known as dandrader|lunch === alan_g is now known as alan_g|EOD === dandrader|lunch is now known as dandrader === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === beidl_ is now known as beidl [23:08] Saviq, greyback: If you want it, http://anonscm.debian.org/gitweb/?p=pkg-xorg/app/apitrace.git;a=shortlog;h=refs/heads/master is where you can find apitrace 5.0; git buildpackage will know what to do with it.