=== snadg3 is now known as snadge
[08:24] <mlankhorst> bleh, greyback/'s branch doesn't work for me :/
[08:32] <mlankhorst> greyback: I'm still getting compiling errors with your mir0.11 branch, what did you use as base?
[08:32] <greyback> mlankhorst: mir 0.11 from the PPA
[08:32] <greyback> silo12
[08:32] <mlankhorst> I have that one too
[08:33] <mlankhorst> 0.11.0+15.04.20150209.1-0ubuntu1
[08:33] <greyback> what errors are you getting
[08:33] <mlankhorst> did you even compile test it? I see tests failing to build :P
[08:33] <mlankhorst>     surfaceItem->processTouchEvent(QEvent::TouchBegin,
[08:33] <mlankhorst>         timestamp + 20, Qt::NoModifiertouchPoints, touchPoints[0].state());
[08:34] <mlankhorst> should be
[08:34] <mlankhorst>         timestamp + 20, Qt::NoModifier, touchPoints, touchPoints[0].state());
[08:34] <greyback> I didn't enable building tests, it was just a proof of concept
[08:34] <mlankhorst> oke
[08:35] <greyback> give "-DNO_TESTS=true" to cmake
[08:35] <mlankhorst> I probably had the wrong mir then, now it worksk (with that fix)
[08:40] <mlankhorst> greyback: ah I was just doing a deb build
[08:46] <mlankhorst> hm great, no session popping up at all..
[08:52] <mlankhorst> seems if I use the qtmir from the ppa unity8 won't run
[08:53] <greyback> lots of people have tested silo 12, and unity8 is working there
[08:55] <mlankhorst> yeah silo 12 works, just not when I use your qtmir with silo 12
[08:55] <greyback> let me see
[09:06] <mlankhorst> black screen + infinite loop somewhere
[09:15] <Mirv> I'm releasing Mir 0.11 but filed bug #1420175 as per archive admin comments
[09:15] <ubot5> bug 1420175 in mir (Ubuntu) "Add conflicts/replaces for the obsolete packages" [Undecided,New] https://launchpad.net/bugs/1420175
[09:19] <greyback> mlankhorst: so I pushed test fixes to the branch: lp:~gerboland/qtmir/port-to-event-2.0-with-mir0.11
[09:19] <greyback> I built the package & installed it. unity8 works fine. I'm getting mouse hover events too
[09:21] <mlankhorst> can you build the debs and install them?
[09:22] <mlankhorst> it's the same but with -
[09:22] <mlankhorst> -DQTMIR_USE_OPENGL
[09:28] <greyback> mlankhorst: that's what I did. works ok here
[09:28] <mlankhorst> weird
[09:34] <alan_g> alf_: anpok_ no duflu? no hangout?
[09:38] <mlankhorst> no matter what I try I don't get a u8 session
[09:39] <mlankhorst> as soon as I use the one from the ppa again it works as intended
[09:43] <anpok_> alan_g: sorry, notification did not work and I didnt notice how time passed by...
[09:44] <alan_g> anpok_: got anything you want to discuss now? Or will it wait for standup?
[09:46] <mlankhorst> meh I give up for now
=== chihchun is now known as chihchun_afk
[09:52] <anpok_> hm no real topics
=== chihchun_afk is now known as chihchun
[10:53] <mlankhorst> greyback: can I run unity8 in valgrind somehow?
[10:53] <greyback> mlankhorst: sure, but I've not done it
[10:54] <greyback> mlankhorst: are you getting errors anywhere? unity8.log should be very verbose
[10:55] <mlankhorst> where's that one kept?
[10:55] <greyback> ~/.cache/upstart
[11:09] <mlankhorst> ahh
[11:09] <mlankhorst> file:///usr/share/unity8/Shell.qml:21:1: plugin cannot be loaded for module "Unity.Application": Cannot load library /usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so: (/usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so: undefined symbol: _ZN19SurfaceConfigurator16staticMetaObjectE)
[11:09] <mlankhorst> SurfaceConfigurator::staticMetaObject
[11:13] <mlankhorst> needed qtmir-desktop too, why doesn't it have a proper depends on that?
[11:14] <mlankhorst> yeah now it works
[12:02] <mlankhorst> greyback: hmm still some silliness, autorepeat is handled wrongly..
[12:02] <greyback> mlankhorst: I didn't go into such specifics. Please log bugs for the issues you find
[12:03] <mlankhorst> ok
[12:04] <mlankhorst> I get repeated KeyUp events instead of KeyRepeat events..
[12:04] <greyback> if mir-demo-server doesn't give you that, then it's a qtmir issue
[12:06] <mlankhorst> definitely a qtmir issue
[12:08] <mlankhorst> only happens on your event 2.0 branch
=== dandrader is now known as dandrader|afk
[12:27] <mlankhorst> greyback: do I have to file bugs against branches too?
[12:28] <greyback> mlankhorst: would appreciate you mentioning in the bug which branch you're testing, but that's enough
[12:33] <mlankhorst> oke
=== dandrader|afk is now known as dandrader
[12:40] <mlankhorst> greyback: hm no support for mouse wheel either
[12:40] <greyback> mlankhorst: was told that's not working in mir
[12:40] <mlankhorst> oke
[12:41] <mlankhorst> I'm getting some motion events from mir_demo_server at least when using my scrollwheel
[12:42] <greyback> mlankhorst: talk to racarr, he knows more. But do log bug anyway
[12:46] <mlankhorst> https://bugs.launchpad.net/qtmir/+bug/1420271 good enough?
[12:46] <ubot5> Launchpad bug 1420271 in QtMir "Missing events in qtmir with the port-to-event-2.0 branch" [Undecided,New]
=== alan_g is now known as alan_g|lun
=== alan_g|lun is now known as alan_g
[14:26] <racarr> mlankhorst: greyback: Mouse wheel is more related to an implementation detail of qtmir making it difficult to pass the information...e.g. too much gets lost through the translation to QEvent though I can't remember
[14:26] <racarr> the exact details without looking
[14:26] <greyback> racarr: ok
=== chihchun is now known as chihchun_afk
[14:27] <racarr> it may have even just been modifiers lol I think there was something else though
[14:27] <racarr> but anyway someone just needs a utility to pass through
[14:27] <racarr> wrt to autorepeat events I can check that out
[14:27] <racarr> :)
=== chihchun_afk is now known as chihchun
=== dandrader_ is now known as dandrader
[14:50] <alan_g> racarr: with your knowledge of the input changes this should be easy for you to check: https://code.launchpad.net/~alan-griffiths/mir/port-window-management-example-to-current-input-API/+merge/249180
[14:52] <racarr> alan_g: :) Thanks. Will get to it right after I fix up this test...
[14:53] <racarr> (I think I've decided on /proc/thread-self/fd/)
[14:54] <racarr> Started reviewing the WM example framework yesterday too...it seemed appropriate but not done grokking all the policy members yet
[14:54] <racarr> I liked the templating of the info classes...:D
[15:16] <mlankhorst> alf_: at what point do you need the mesa 10.4.2-2ubuntu4 upload?
[15:19] <alf_> mlankhorst: Without the fix the Mesa package won't build against mir-0.11, so it would be good to land this relatively soon.
[15:20] <mlankhorst> will it still build against 0.10 with those changes?
[15:23] <alf_> mlankhorst: no
[15:23] <mlankhorst> can you get mesa through the landing ppa then? might be easier that way..
[15:23] <mlankhorst> or at least tell me when mir hits proposed
[15:23] <mlankhorst> for normal uploads
[15:24] <alan_g> Well yes, the content of the Info classes is driven by the window management policy
[15:26] <alf_> mlankhorst: mir 0.11 is already in the archive
[15:26] <mlankhorst> oh how did it get past proposed?
[15:26] <mlankhorst> hm right
[15:27] <alf_> mlankhorst: it's only a build-dep for Mesa that got changed, no ABI/API breaks
[15:27] <mlankhorst> yeah I guess it only checks installability, not buildability
[15:27] <mlankhorst> I'll upload mesa
[15:28] <alf_> mlankhorst: thanks
[15:35] <mlankhorst> uploaded
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
=== dandrader is now known as dandrader|lunch
=== dandrader|lunch is now known as dandrader
=== alan_g is now known as alan_g|EOD
[18:29] <mlankhorst> alf_: https://launchpadlibrarian.net/197217165/buildlog_ubuntu-vivid-amd64.mesa_10.4.2-2ubuntu4_FAILEDTOBUILD.txt.gz
[18:29] <mlankhorst> oddly enough local build succeeded, are you missing a dependency?
=== chihchun is now known as chihchun_afk
=== sturmflut_ is now known as sturmflut
[21:09] <DalekSec> Hrm, duflu is missing.
[21:24] <DalekSec> Well, if anyone else is interested, http://sigma.unit193.net/lightdm/unity-system-compositor.log
[21:27]  * racarr succumbs to the plague
[21:30] <DalekSec> Hmm, yes.  That link could kill you.
[21:30] <DalekSec> https://bugs.launchpad.net/mir/+bug/1212753
[21:30] <ubot5> Launchpad bug 1212753 in mir (Ubuntu) "[i865] unity-system-compositor fails to start: Failed to choose ARGB EGL config" [Medium,Fix released]
[23:33] <kgunn> DalekSec: wait, you saying that bug didn't really get fixed ?
[23:34] <DalekSec> kgunn: I would say that, yes.  I have the affected hardware, tested 0.11.0 that was uploaded today/yesterday, and it still crapped out with that log.
[23:35] <DalekSec> Though I wasn't going to touch your bug report, had talked to duflu a little back about it.
[23:35] <kgunn> DalekSec: thanks for being kind :)
[23:35] <kgunn> DalekSec: can i ask what hw ?
[23:36] <DalekSec> kgunn: He also said you guys couldn't obtain the hardware, so I figured I'd check and it'd be polite to report back.  Sure, what do you want to know exactly?  Some of the info is on the xubuntu mir wiki page, but 82845G/GL chip: 8086:2562.
[23:38] <kgunn> DalekSec: yeah, that....was mainly curious about gpu
[23:38] <kgunn> duflu will be on in a bit
[23:38] <DalekSec> "Total crap" :P
[23:39] <kgunn> ~1.5 hr
[23:39] <DalekSec> http://paste.openstack.org/show/MNMILlfNtuhgOpJYJA3x/
[23:41] <DalekSec> http://paste.openstack.org/show/ilFEYLp8qY75dkGm4Px5/ (or if you prefer lshw output)
[23:45] <tmpRAOF> Hm, 845 :)