[01:30] <thumper> bschaefer: ping
[01:32] <bschaefer> thumper, hey
[08:37] <medoc> Hi. I am writing a unity lens/scope for the recoll search engine. I know close to nothing about gtk/gnome/unity and I need a little help
[08:38] <medoc> My problem at the moment is that the recoll search (big disk-based index) is too slow for being started every time a character is typed
[08:39] <medoc> I'd like to time-out a little and only launch an actual search after, maybe a few hundred ms after the user stopped typing.
[08:39] <medoc> Could someone point me to a way to do this, some sample code, whatever ? Thanks
[08:40] <medoc> Ah and the lens is written in Python (which I don't know well either :) )
[10:07] <MCR> Dear Unity developers: Please read this and the comments as well ;) : http://www.webupd8.org/2012/03/unity-with-minimize-on-click-patch.html
[10:51] <mhr3> davidcalle, ping?
[10:51] <davidcalle> mhr3, pong
[10:51] <mhr3> davidcalle, is the video lens even supposed to search in the home view?
[10:51] <mhr3> the files lens should pick up videos as well, so i'm not really sure...
[10:52] <davidcalle> mhr3, It's supposed to act like the music lens.
[10:52] <mhr3> so no results for empty search, but searches work
[10:54] <davidcalle> Yeah, and search only for the local videos scope.
[10:55] <mhr3> right
[10:55] <davidcalle> And the files lens picks up Music results as well, with the locate stuff.
[10:55] <mhr3> true
[10:57] <davidcalle> Hopefully, when a Photo lens comes by default, we will be able to have something more clean on this side and propose lenses for almost each data type.
[10:58] <davidcalle> Or, right now, the files lens could avoid showing video and audio results in the home dash.
[10:59] <davidcalle> But the old results from the video lens is the priority, I'll take care of it.
[12:29] <apw> didrocks, i have another one for you: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/962119
[12:29] <apw> didrocks, i will also note i hit the thing which said "display oriented" which _said_ it would file the bug against compiz instead of unity ... it did not however do that
[12:29] <apw> (opr at least thats how i interpreted the text i read)
[12:30] <didrocks> om26er: can you look please? ^ I'm really busy right now with the release stuff
[12:30] <om26er> sure
[12:31] <om26er> didrocks, looking
[12:31] <didrocks> thanks
[12:33] <apw> didrocks, in fact "Thanks for reporting this bug on unity.  Is the issue you are reporting purely graphical (will report more information about your graphic configuration and will report the bug against compiz)?"
[12:33] <apw> it does say it'll file the bug against compiz, and doesn't work
[12:33] <didrocks> apw: doesn't work? what did you get?
[12:33] <didrocks> ah not genuine package?
[12:34] <apw> didrocks, no i filed against unity, it asks that dialog text above, i hit YES, and it didn't move it to compiz like it says it will
[12:34] <didrocks> apw: it won't file it to compiz, however, it adds all the compiz hooks info
[12:34] <didrocks> I guess, I need to check
[12:34] <didrocks> too old :)
[12:34] <apw> didrocks, hmm then the text is wrong i guess .,,
[12:35] <didrocks> will have a look
[12:35] <didrocks> just not… now :p
[12:35] <apw> no rush
[12:35] <didrocks> thanks for spotting it :)
[12:35]  * apw is starting to see stacking issues again ... mostly in menus now
[12:40] <om26er> uh i broke my unity
[12:48] <om26er> wow dash looks hot now. just wow
[12:48] <om26er> apw, seems I can't reproduce the issue  here. do you know when it started happening?
[12:50] <MCR> Is smspillaz still part of your team ?
[12:50] <om26er> MCR, yes
[12:50] <MCR> COOL, good to hear that !
[12:51] <MCR> om26er: Did you break MyUnity or your Unity ?
[12:51] <apw> om26er, its not an operation i use normally i only opened it to see if i had the new buttons in there
[12:52] <apw> om26er, it is easiest to reproduce by moving to focus follows mouse and moving the cursor in and out of the window.  happens about 1/4 of the time
[12:52] <mhall119> MCR: I can see how that can get confusing
[12:52] <MCR> How can I check out Unity from source ? - Is there a wiki somewhere ?
[12:53] <apw> didrocks, om26er, another stacking issue which might be compiz: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/962137
[12:53] <mhall119> MCR: bzr branch lp:unity
[12:53] <MCR> mhall119: thx a lot
[12:53] <mhall119> thomi: ping
[12:54] <MCR> mhall119: Compiling with cmake, standard ?
[12:55] <mhall119> MCR: I'm not the one to ask about that, I'm a Python guy
[12:55] <om26er> no test case again :p
[12:55] <MCR> mhall119: ok, thx - I will get it to work somehow ;)
[12:56] <MCR> mhall119: cmake seems to be it
[12:58] <MCR> ups, seems I need some more packages :)
[12:58] <mhall119> MCR: someone else in here will be able to help you
[12:58] <mhall119> they helped me
[13:03] <MCR> Could someone tell me how to best install all the build dependencies for unity ?
[13:46] <arges> dbarth_, hello
[13:49] <tsdgeos> MCR: apt-get builddep unity
[13:50] <tsdgeos> build-dep actually
[13:55] <dbarth_> arges: hi
[13:55] <MCR> tsdgeos: thx a lot :)
[13:56] <arges> dbarth_, hey I saw that you marked pad.lv/960532 incomplete. this bug pretty much makes my laptop unusable, so I'm highly motivated to help debug this
[13:56] <arges> dbarth_, is there a debug guide / wiki / advice on how to get a better test case for this so it can be fixed
[14:00] <MCR> cmake .. worked, but sudo make install failed
[14:01] <MCR> fatal error: Nux/Nux.h: No such file or directory
[14:01] <MCR> any idea what I am missing ^^ ?
[14:13] <dbarth_> arges: ok
[14:14] <dbarth_> arges: for this kind of bug, there's not really a standard process
[14:15] <dbarth_> arges: my suggestion is to do DISPLAY=:0 xwininfo  -root -all > ~/xwininfo-all-stuck.log from a VT
[14:15] <arges> dbarth_, ok, any words of wisdom or perhaps tests  you can suggest that might give a better reproducer ... i can pretty much get it in that state within a 10-30m of usage
[14:15] <arges> ok
[14:16] <arges> so do that when i can't click anymore
[14:16] <dbarth_> arges: right, when it's locked
[14:17] <dbarth_> arges: i've had the bug myself, and this is what i did to document the state
[14:17] <dbarth_> arges: also i think you can reproduce it more easily if you do ALT-F10 repeatadly (was trying to debug another issue and that happened to me again)
[14:17] <dbarth_> arges: https://bugs.launchpad.net/unity-distro-priority/+bug/948522
[14:18] <arges> ok let me fire it up, i'll check this out
[14:19] <arges> dbarth_, would unity 2d / unity make a difference? i've seen the lockup with both
[14:20] <arges> dbarth_, wow instant lockup hitting alt-f10 repeatably . but its different than the other lockup i've been experiencing
[14:21] <zgreg> I noticed the alt-f10 freeze, too
[14:46] <dbarth_> arges: hmm, you mean it does the same with unity-2d as well?
[14:46] <arges> dbarth_, yes
[14:46] <dbarth_> arges: that would be very interesting, because a few components could be exonerated
[14:46] <arges> dbarth_, i am reproducing now and getting some logs
[14:46] <dbarth_> great
[15:06] <elopio> ping greyback.
[15:06] <elopio> do you have some time for me?
[15:06] <greyback> elopio: what can I do for you?
[15:09] <elopio> greyback: it's just that testability can't find my application. I thought you might know how to debug this.
[15:09] <elopio> greyback: http://paste.ubuntu.com/895187/
[15:09] <elopio> if you have a precise, it will return Run failed. Failed to launch application. [...] ApplicationNotAvailableError
[15:10] <greyback> elopio: try supplyingabsolute path to the execurable
[15:10] <greyback> try supplying the absolute path to the executable (this time looking at what I type:) )
[15:11] <greyback> but if it is in $PATH, that shouldn't matter
[15:12] <elopio> greyback: just the same. The application is started, and I can see it from the visualizer. Still, it says that's not available.
[15:13] <greyback> elopio: hmm, have you the log file /logs/testability/qttasserver.log
[15:16] <elopio> greyback: there's nothing on /logs/testability/
[15:17] <elopio> oh wait
[15:17] <greyback> elopio: you should create that directory so, and try agai
[15:17] <greyback> +n
[15:18] <elopio> greyback: http://paste.ubuntu.com/895203/
[15:19] <elopio> that's the right pid.
[15:20] <greyback> elopio: you have /usr/lib/x86_64-linux-gnu/qt4/plugins/testability/libtestability.so ?
[15:20] <greyback> (that's for 64bit machine)
[15:21] <elopio> greyback: yes, it's there.
[15:23] <greyback> elopio: so strange. Could you supply ":sleep_time => 10" to the run function please
[15:23] <greyback> just in case the app hasn't loaded the plugin in time
[15:24] <elopio> greyback: same error, but 10 seconds later.
[15:25] <greyback> elopio: so the Visualizer sees the application, and you can inspect elements ok. But this fails
[15:26] <greyback> elopio: what code are you testing? I'd like to try this myself
[15:26] <elopio> greyback: yes. I see the application opened by the script.
[15:27] <elopio> greyback: it's just http://paste.ubuntu.com/895187/
[15:27] <elopio> for ubuntuone-control-panel-qt you have to be on precise.
[15:29] <greyback> ok let me try
[15:31] <elopio> thanks greyback.
[15:31] <greyback> elopio: yep reproduced anyway
[15:38] <elopio> greyback: greyep. If I'd know what the problem is, I could tell the u1 team to fix it. But I have no idea, and I still can't fully understand the ruby code for the run function.
[15:38] <greyback> elopio: I got it
[15:39] <greyback> elopio: http://paste.ubuntu.com/895228/
[15:39] <elopio> greyback: awesome!
[15:39]  * elopio trying...
[15:40] <greyback> elopio: testability checks the process name is running. But since you're app is in python, it's executable is named "python" - so testability never saw an app called "ubuntu-one.."
[15:40] <greyback> which confused it
[15:44] <greyback> elopio: https://projects.developer.nokia.com/dav/Testabilitydriver/doc/api/qt_linux/#GenericSut:run
[15:44] <greyback> elopio: the doc mentions a slight consequence, just fyi
[15:45] <elopio> now the problem seems to be my computer.
[15:45]  * elopio smacking...
[15:46] <elopio> I'll read it. Thanks a lot greyback.
[15:46] <greyback> elopio: yw
[15:46] <zgreg> I wonder if the workspace preview as it is currently implemented is useful (the small overview you get after ctrl-alt-up/down/left/right is pressed to move to another workspace)
[15:47] <zgreg> the live preview is prettyy useless, it's too small, the rendering is full of aliasing, and it needs considerable resources
[15:48] <zgreg> the current workspace is only highlighted, but it's too little contrast
[15:48] <zgreg> s/only//
[15:48] <zgreg> IMO the static preview of the compiz plugin is much more useful, and looks nicer
[15:49] <zgreg> what do you think about this?
[15:49] <bilal|web> When is 5.8 coming out?
[15:53] <zgreg> the internal version number is already 5.8.0 :)
[19:00] <thomi> mhall119: pong
[19:01] <mhall119> thomi: hey, was it you that helped me get unity compiled and run locally?
[19:01] <mhall119> if so, do yu have a written tutorial for that I can put on unity.u.c?
[19:02] <thomi> mhall119: I don't think it was me, but I have a rough-and-ready blog post witten about it (although it'd need to be fixed if you're going to re-post it anywhere where people might actually read it)
[19:02] <mhall119> thomi: I can clean up/edit whatever it needs
[19:03] <thomi> mhall119: http://tech-foo.blogspot.co.nz/2012/02/how-to-compile-unity-from-source.html
[19:03] <mhall119> I just don't remember all the steps
[19:03] <mhall119> ah, perfect, thanks
[19:03] <thomi> no worries
[19:03] <mhall119> thomi: I'll get everybody to review these docs before they're published
[19:04] <thomi> good ;)
[19:04] <thomi> I'm quite happy writing on my blog where no one reads it. :)
[19:04] <mhall119> well, I can change that
[19:29] <zgreg> apparently nux typically does 40 opengl calls and various small calculations just to draw a single texture quad onto the screen
[19:29] <zgreg> no wonder performance isn't that great...
[19:30] <thomi> zgreg: "apparently"?
[19:30] <zgreg> if I got everything
[19:30] <thomi> ok, you've measured this yourself?
[19:31] <zgreg> I've read the source code, and tracked everything down, starting from QRP_ASM_1Tex
[19:33] <zgreg> hmm the GLSL-based implementation is a little bit better, but not much
[19:33] <zgreg> that's not exactly helping either, typically slow machines need the ASM code path
[21:32] <bschaefer> thomi, ping
[21:32] <thomi> bschaefer: sup?
[21:33] <bschaefer> thomi, hey, so I need to write some new anthy autopilot test for a new commit key
[21:33] <bschaefer> thomi, and was wonder if I should just copy paste the one with Ctrl+J and replace it with Enter
[21:33] <thomi> bschaefer: does the old key still work?
[21:34] <bschaefer> yeah
[21:34] <thomi> bschaefer: then just extend the scenarios on the anthy test case
[21:34] <bschaefer> thomi its just that Enter is the "perfered" way to commit text for Japanese/anthy I guess
[21:35] <thomi> so for each input string there'll be a scenario for Ctrl+J and a scenario for Enter
[21:35] <bschaefer> alright
[21:36] <bschaefer> Well I think that is what I did, just made a different function and replaced Ctrl+J with Enter
[21:36] <thomi> bschaefer: you don't need to make a new function... just add a new scenario parameter
[21:36] <bschaefer> alright, was about to say that haha
[21:36] <thomi> so inside the one function we'll now do something like:
[21:36] <thomi> self.kb.press_and_release(self.commit_key)
[21:37] <thomi> and commit_key is a scenario parameter
[21:37] <bschaefer> thomi, ok!
[21:37] <bschaefer> thomi, also how was your fishing trip?
[21:37] <thomi> bschaefer: was good, ended up not fishing at all, but went luging, bungy jumping, and clay pidgeon shooting
[21:38] <thomi> good stress releif :)
[21:38] <bschaefer> thomi, awesome! I keep forgetting your in summer time. I finally saw the sun this week!
[21:38] <thomi> heh, well, technically we're in autumn now
[21:39] <bschaefer> thomi, yeah, that makes sense as we just hit spring :)
[21:39] <bschaefer> thomi, alright I should have some autopilot test for you to look at soon!
[21:40] <thomi> sweet!
[21:52] <bschaefer> thomi, https://code.launchpad.net/~brandontschaefer/unity/ibus-anthy-autopilot/+merge/98933
[21:52] <bschaefer> when you get a chance, diff still updating
[21:53] <thomi> ok. running unity in valgrind at the moment
[21:53] <bschaefer> also there is new code in nux that allows for 'Enter' to work, not sure if Jenkins will use the right nux right away
[21:53] <thomi> so everything is sloooooow
[21:54] <bschaefer> thomi, haha no worries, I keep forgetting how awesome python is. im actually fairly new to it haha
[21:54] <bschaefer> for some reason I didn't think it was an associative array
[21:55] <thomi> heh
[21:55]  * bschaefer gets slightly excited over languages 
[21:58] <mhall119> thumper: those bzr commit stats I was generating the other day?  I've incorporated them into http://reports.qa.ubuntu.com/reports/unity-stats/#commit_stats
[21:59] <thumper> nice
[21:59] <mhall119> it'll start showing something the next time there's a commit to one of the development focus branches
[21:59] <mhall119> it's grouping unity, unity-2d and nux
[22:00] <mhall119> I suppose I should add BAMF to the mix too
[22:01] <thomi> bschaefer: hmmm,
[22:02] <bschaefer> thomi, o noes, did I do something wrong again haha?
[22:09] <thomi> bschaefer: I found a much better way to do something.
[22:09] <thomi> mind if I hack your branch around?
[22:10] <bschaefer> thomi, nope, go ahead! Should have pushed it to ~unity-teamm
[22:10] <bschaefer> but the changes are small so go ahead :)
[22:10] <thomi> it turns out testscenarios provides a simple way to generate a dot-product of one or more parameters
[22:10] <thomi> so you can have every combination of param X and param Y
[22:10] <bschaefer> o nice
[22:11] <bschaefer> so we can use Enter on all of them as well as Ctrl+J?
[22:18] <thomi> exactly
[22:18] <thomi> ...but it's not available in the version of testscenarios in porecise :(
[22:19] <bschaefer> thomi, :(
[22:19] <thomi> I'll copy the code for now
[22:19] <thomi> it's pretty simple
[22:20] <bschaefer> thomi, yeah, I had to write something like that a while ago for school. permeations are fun haha
[22:26] <thomi> bschaefer: ok, this is looking a bit harder than I anticipted. I'll work something out and propose a new merge
[22:27] <thomi> probably this afternoon
[22:27] <thomi> this is something we need in a bunch of places, so it'll be good to get it in
[22:28] <bschaefer> thomi, awesome! Thanks :)
[22:31] <thomi> bschaefer: ok, as soon I wrote that I figured it out
[22:31] <thomi> the test currently launches apps though... I guess we need that nux branch
[22:31] <thumper> thomi: scenarios can be a python property
[22:31] <thumper> thomi: so it can generate the scenarios when called
[22:32] <thomi> thumper: yeah, but there's a better way :)
[22:32] <thumper> oh?
[22:32] <thomi> thumper: if you have two axis, generate a dot product of everything from axis 1 with everything from axis 2
[22:32] <thomi> We've been doing this manually so far, which requires a lot of finger work
[22:32] <bschaefer> thomi, double awesome :)
[22:33] <thomi> this way it looks really nice
[22:34] <bschaefer> thomi, that nux branch should be merged with nux
[22:34] <bschaefer> thomi, did that earlier this morning
[22:34] <thomi> ok, I guess I just don't have it locally then
[22:36] <bschaefer> thomi, also thats what Haskell does with list comprehension (the dot product)
[22:36] <bschaefer> thomi, not sure if you have dabbled there
[22:37] <thomi> bschaefer: thumper check it out: https://code.launchpad.net/~thomir/unity/ibus-anthy-autopilot/+merge/98939
[22:40] <bschaefer> thomi, nice!
[22:42] <bschaefer> thomi, do you know if jenkins will recompile nux with an abi change?
[22:42] <bschaefer> with out*
[22:43] <thomi> bschaefer: I don't understand
[22:43] <bschaefer> thomi, well if we merge this, and nux isn't recompiled while jenkins is running that test it will fail
[22:43] <thomi> bschaefer: ahh, yeah. That happens often
[22:43] <bschaefer> thomi, alright sweet :)
[22:44] <thomi> we see a little spike on the jenkins graph. I'm not sure we can do much about it at this stage
[22:44] <thomi> I gotta go to lunch. be back online later though
[22:44] <bschaefer> thomi, cool! Have a good lunch