[00:40] RAOF, o looks like cookie factory inst installing correctly? [00:41] Hah! Indeed. [00:41] more protobuf issues for amd64 [00:41] sad face until that gets fixes [00:41] fixed* [00:41] We haven't added a libmircookie package to debian/control :) [00:41] RAOF, o duh, i added the nettle-dev to control [00:42] bschaefer: more? like what? [00:42] bschaefer: it's compiling and passing here with GCC (lp:mir) [00:42] AlbertA, more? [00:42] oo [00:42] AlbertA, umm in jenkins [00:42] lp:mir compiles fine for me locally [00:42] though its failing in clang [00:43] * bschaefer should try that [00:44] Yeah, clang is known-broken with gcc-5 built stuff. [00:44] well at lease its not my fault haha [00:45] RAOF, so we need to create a cookie factory package? [00:45] ie library? [00:45] Yup. [00:45] libmircookie1 [00:45] + libmircookie-dev [00:46] * bschaefer attempts [00:46] * RAOF originally had this as an external project called libspoofless, but that was just soooooo much annoying overhead. [00:46] haha [00:54] RAOF, might need to be worded a bit better :) [00:54] http://paste.ubuntu.com/12121500/ [00:55] I can probably update the description in the branch if you like :) [00:55] RAOF, pushed if you want to change it [00:55] haha yeah [00:55] install files there === chihchun_afk is now known as chihchun [05:16] RAOF: are you still about? can I get a core dev ack on Mir https://ci-train.ubuntu.com/job/ubuntu-landing-028-2-publish/lastSuccessfulBuild/artifact/mir_packaging_changes.diff ? (the debian/ files, the rest are just for information) [05:16] seems ok changes and cleanups for me [05:33] Mirv: Yeah, seems sensible to me. [05:34] RAOF: thanks! I still need archive admin preNEW review though to ack the adding of binary packages, but 1/2 completed. [05:56] tvoss: Hey I found Jolla are to blame for our smoothness issues, kind of :) https://bugs.launchpad.net/qtmir/+bug/1486341 [05:56] Ubuntu bug 1486341 in unity8 (Ubuntu) "Touch scrolling is stuttery under Unity8 (but only while you're touching it)" [Undecided,New] [07:14] Oh, goody. That kernel panic corrupted my bzr working tree. [07:55] duflu: it'd look to me that at least the MP linked to from QTBUG is only found in Qt 5.5 while the 5.4 branch has a crash fix that mentions it but apparently not the touch compression feature itself (looking at git logs at git://code.qt.io/qt/qtdeclarative.git) [07:56] Mirv: Yeah the QTBUG might not be related. But the introduction of the feature occurred in 5.4 AFAIK [07:57] ok [07:57] I know because Gerry told me about it early last year [07:57] And it was about to be released then [07:58] yeah I also think I remember some earlier discussions, it's probably an earlier feature that has been later refined [07:59] Mirv: Even if it worked properly, it would be redundant with what Mir already does [08:03] Not quite; it can align event processing with Qt's renderloop, which Mir doesn't do. [08:05] RAOF: Nice in theory. In practice it's broken and everything works better without it :) [08:17] duflu: interesting findings on the touch scrolling, could it be the combination of the 2 input resampling engines being the problem, more than Qt's one alone? [08:18] greyback: Thought of that and apparently no. Turning off Mir's and just leaving Qt's the problem remains [08:18] duflu: ok [08:18] greyback: But please do try for yourself [08:19] will do [08:19] alf: OK, remind me who to ask to fix up the CI scripts? [08:24] greyback: Where in the architecture is it? Would apps have run though the compression twice or just once? [08:28] duflu: touch compression happens in each QQuickWindow. So the unty8 window will do compression before dispatching events to the qml scene. [08:28] greyback: I mean full stack. Just once then? [08:28] apps also have a QQuickWindow, and will use same compression logic [08:28] so no, multiple times [08:28] Hmm [08:29] That's great news. We might be able to go one better still [09:00] duflu: it's usually fginther [09:00] duflu: that fixes things for us [09:00] alf: OK, thanks [09:01] greyback: Is there a way to use desktop_file_hint without having a valid file? [09:01] duflu: having a valid file is the point :) [09:02] just point it to any existing file [09:02] greyback: Hmm, doesn't work. I might be using an incompatible Mir version or something [09:02] is unity8.log printing anything? [09:03] if client connection rejected, unity8 prints a REJECTED notice [09:03] just use something like /usr/share/applications/gedit.desktop [09:03] greyback: I get the app starting animation indefinitely [09:04] duflu: something else wrong so, that means the client has connected, but not drawn its first frame [09:04] greyback: Arg. We might have broken protocol compatibility [09:04] I think we've a bug where actually a couple of frames need to be drawn [09:15] alf: How do you feel about it landing (by hand) and then CI getting fixed? [09:15] It would have to be in that order [09:16] alf: Oh umm, or I could just hack the script to work [09:16] I might do that [09:21] duflu: I wouldn't mind landing it first as long as CI gets fixed soon after (and CI is broken anyway so...) [09:21] alf: Never mind. I have a solution that won't need CI changes now [09:23] greyback: Confirmed, we broke protocol compatibility in lp:mir (clients don't talk to existing servers any more) [09:23] Need to bisect that [09:23] duflu: uh oh [09:24] recent? [09:24] greyback: Yeah, it was working at least a week or two ago [09:38] duflu: seems like a good candidate for automated testing, something to consider for our new jenkins instance [09:45] alf: Kind of the reverse of what we have in glmark2. That tests the previous release client against the newer server (I think?) [09:50] duflu: only if there is an ABI bump, otherwise glmark2 just uses the update library of the same ABI [09:50] How very predictable === alan_g is now known as alan_g|lunch === vesar is now known as vesar_lunch [11:27] alf, with lp:~afrantzis/mir/buffer-bind-to-render-image how does a mgm/mga::Buffer switch between gl binding and another sort of binding? === vesar_lunch is now known as vesar === vesar is now known as vesar_ === vesar_ is now known as vesar__ [11:30] kdub: In a future MP, we will have a Platform::create_buffer_allocator(RendererType const& renderer_type), so the buffer allocator will know to create buffers supporting the renderer [11:32] and, just guessing, will have something like: mgm/mga::Buffer::Buffer(..., std::shared_ptr const&) ? [11:36] kdub: Each platform can handle this as it sees fit internally, but what you propose is a reasonable approach if a platform supports multiple renderers. For the first step it's not needed since the existing platforms will just support "gles2". === alan_g|lunch is now known as alan_g === tedg is now known as ted === dandrader_ is now known as dandrader === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === chihchun_afk is now known as chihchun === alan_g is now known as alan_g|EOD [18:07] kgunn, i don't know how to get debs of mir built that i can test on my device, how would you guys feel about adding my branch to silo 0 to so i can test it with my touchpad? [18:07] https://code.launchpad.net/~ken-vandine/mir/touchpad_pointer/+merge/268274 [18:07] sound only affect touchpads, if it doesn't work we can reconfigure it again :) [18:07] greyback_: ^ ? [18:07] kenvandine: in general i don't mind [18:08] i suppose we'd prefer to merge that into the silo0 branch for mir [18:08] sure, if it fixes it [18:08] but i haven't actually been able to test it :) === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader