[05:22] <DBO> ping humphreybc
[05:22] <humphreybc> hi DBO
[05:22] <humphreybc> how's it?
[05:22] <DBO> so I am trying out volley brawl
[05:22] <DBO> (finally)
[05:22] <DBO> is there any way to up the initial speed? its god awfully slow
[05:23] <humphreybc> I think you can hack the code, there are some really simple variables
[05:23] <humphreybc> BUT the good news is
[05:23] <DBO> it's python?
[05:23] <humphreybc> Bart and Tommy are pushing out an update next week I think with hopefully an option to increase ball speed
[05:23] <humphreybc> It's lua I think
[05:23] <humphreybc> I didn't write it
[05:23] <humphreybc> But you can just find the .love file (opt/volleybrawl or something)
[05:23] <humphreybc> and then extract it
[05:24] <DBO> if I can modify it I can show you guys how to make it match in unity :)
[05:24] <humphreybc> I need to talk to Tommy/Bart but yeah we'd like an update out next week with "official" faster ball speed option, more characters, all that jazz
[05:24] <humphreybc> aha!
[05:24] <humphreybc> yes, do that
[05:24] <humphreybc> you can email Bart and Tommy - sigmoid@ohso.co
[05:25] <humphreybc> I'll be on IRC each day for the next week anyway
[05:25] <DBO> basically the wm-class is set to "love-0.7"
[05:25] <DBO> you need to set it to "volleybrawl"
[05:26] <humphreybc> ah
[05:26] <humphreybc> I'll tell bart now so he gets it when he wakes up
[05:27] <humphreybc> DBO: Thanks. You should play around with the code, you can do some pretty funny stuff by messing with gravity
[05:27] <DBO> still not sure how to extract a .love file
[05:30] <RAOF> With flowers, surely?
[05:30] <RAOF> Or perhaps a nice dinner? :)
[05:30] <DBO> you have to romance it first
[05:32] <DBO> oh I see
[05:32] <DBO> its just a zip file
[05:39] <DBO> oh hmmm
[05:39] <DBO> Love may not let them do that
[05:39] <DBO> nor does it seem to export any identifying information on the window
[05:40] <DBO> how brutally evil
[05:42] <humphreybc> lol
[05:42] <humphreybc> Bart is the lead developer for love too
[05:42] <humphreybc> So.. maybe he can actually fix the engine :P
[05:42] <humphreybc> DBO: are you working on that windows-spawning-in-the-dead-zone bug?
[05:43] <DBO> what bug?
[05:43] <humphreybc> clearly not then :D
[05:43] <DBO> yeah your easiest fix is to make love export the PID on teh window
[05:43] <DBO> and then have your wrapper script use exec
[05:43] <DBO> (thus preserving the launch pid)
[05:44] <humphreybc> kk
[05:44] <humphreybc> I need to talk to Bart anyway so I'll mention it to him
[05:44] <DBO> _NET_WM_PID is what you are after
[05:45] <humphreybc> brb
[05:50] <DBO> what a tease
[06:10] <DBO> wow
[06:10] <DBO> the register *hates* us
[06:13] <RAOF> People read that rag?
[07:25] <didrocks> good morning
[07:26] <DBO> morning didrocks
[07:29] <DBO> didrocks, any bamf changes I make now are Oneiric, right?
[07:30] <didrocks> hey DBO
[07:31] <didrocks> DBO: well, if you want to maintain an "Natty" branchc in //, it's fine:)
[07:31] <didrocks> DBO: if we still have important things, we can deal in a SRU
[07:31] <DBO> okay i want to make sweeping changes
[07:31] <DBO> its going to massively improve accuracy
[07:31] <didrocks> oneiric then, branch an natty one :)
[07:31] <DBO> but I dont know if you will be happy to ship it
[07:32] <didrocks> DBO: no sweeping change in natty, in oneiric, we have the time to fix them then ;)
[07:32] <didrocks> DBO: that's basically why I added a lot of fixme or TODO: in unity (for instance, removing unused variable
[07:33] <DBO> maybe I can make a couple changes small enough to consider...
[07:34] <didrocks> DBO: if you can do that to improve the accuracy, in can be shipped as a 0day SRU
[07:35] <DBO> sweeping accuracy improvements on the way!
[07:35] <DBO> I dont know why I never thought of this before
[07:49] <didrocks> DBO: heh, a new matching way?
[07:49] <DBO> yeah
[07:49] <DBO> if I can remember how to turn a file full of null characters into a strv
[07:57] <didrocks> DBO: you have a bamf merge proposal btw
[07:57] <didrocks> in case you didn't see :)
[07:57] <DBO> looking
[07:57] <didrocks> not sure I like the workaround though :/
[07:58] <didrocks> DBO: don't you receive the branch merge proposal btw in your inbox?
[07:58] <DBO> didrocks, the one from asac?
[07:58] <didrocks> DBO: from chrisccoulson
[07:58]  * DBO checks
[07:58] <DBO> i dont see it
[07:59] <didrocks> DBO: sorry, it's in unity
[07:59] <didrocks> DBO: https://code.launchpad.net/~chrisccoulson/unity/lp767642/+merge/58569
[07:59] <DBO> O_o
[08:02] <didrocks> DBO: if you want, at UDS, I can show you how to automatically triage merge proposal to be in a special email folder :)
[08:02] <DBO> that would be handy
[08:02] <DBO> actually
[08:02] <DBO> I get them
[08:03] <DBO> in a special folder
[08:03] <DBO> which I seem to mentally ignore
[08:03] <DBO> go me
[08:05] <didrocks> DBO: I'll upgrade you so that you don't ignore them anymore :p
[08:05] <didrocks> DBO2.0
[08:06] <MacSlow> good morning folks
[08:06] <MacSlow> salut didrocks
[08:06] <didrocks> hey MacSlow ;)
[08:14] <zniavre> good morning
[08:14] <zniavre> im still stuck with nvidia 173 (legacy) driver , are they blacklisted ?
[08:27] <didrocks> zniavre: you can run /usr/lib/nux/unity_support_test -p to see why unity isn't starting
[08:35] <\sh> hmmm...strange...when I use ctrl+alt+numpad 1/3/etc. the window is moved to the screen edges, but when I move it from the position to another one, the window has not the same size as it was , it's grown automagically
[08:36] <\sh> moins btw
[08:39] <zniavre>  Unity supported:          yes
[08:40] <zniavre> !paste
[08:40] <zniavre> http://paste.ubuntu.com/596828/
[08:41] <zniavre> https://bugs.launchpad.net/bugs/767613
[08:42] <zniavre> after gdm loggin unity can't start it blinks until i came back to gdm to choose gnome-classic
[08:46] <zniavre> didrocks,  i know you are french so to be technical, ça clignote ad-vitam sans demarer unity et sans crasher... (sorry for french i do not know to tell it in english)
[08:47] <didrocks> zniavre: is this a recent regression?
[08:47] <zniavre> from yesterday and the new nvidia 173.14.30 driver
[08:48] <zniavre> with nouveau it works quite well (at least unity, the rest is a pain due to poor performances of nouveau )
[08:48] <didrocks> RAOF: around ? ^^
[08:49] <zniavre> to be polite i m not against nouveau but nvidia173 is a bit better at least for my old hardware
[08:49] <didrocks> zniavre: ok, will track that with RAOF and tseliot
[08:49] <didrocks> zniavre: agreed, and we only support nvidia right now, nouveau has some mem leaks
[08:49] <zniavre> thats true
[08:50] <didrocks> zniavre: ok, will ping the xorg people in charge of those, it's more a nvidia issue than unity
[08:50] <didrocks> zniavre: oh for the record, does the ubuntu classic session work,
 well i think you shuld report a unity bug
[08:50] <didrocks> zniavre: the one using compiz (with nvidia)
[08:51] <zniavre> yes gnome-classic works (with compiz )
[08:51] <didrocks> ok, but seems something regressed for unity (maybe FBO support)
[08:51] <zniavre> all opengl softs works too
[08:52] <didrocks> zniavre: can you post those info and link your pastebin content as well, please?
[08:52] <zniavre> where ?
[08:52] <didrocks> zniavre: in your bug report
[08:54] <zniavre> heu ? (sorry french again) il n'y a pas tout deja ? unity test etc...?
[08:55] <didrocks> zniavre: argh, t'as raison, c'est moi qui l'ai ajouté en plus dans le hook apport. fin de cycle, fatigue… ;)
[08:55] <zniavre> je comprend ...
[08:55] <didrocks> zniavre: j'ai souscris les bonnes personnes et je vais les pinguer aujourd'hui, merci pour l'info :)
[08:56] <zniavre> im sorry to report stuf like that...
[08:56] <didrocks> zniavre: don't be sorry, sorry for the regression :-)
[08:56] <zniavre> :o)
[08:57] <zniavre> i need to go (baby sitting) but im often around if one of you will  needs more infos
[08:57] <zniavre> thank you
[08:57] <didrocks> zniavre: yeah, I think we will need a stacktrace
[08:58] <didrocks> but let's see with the xorg guys first :)
[09:12] <janimo> I started using unity yesterday and I sometimes encounter a strange behaviour on alt-tab. Instead of bringing the new window to the top, the sidebar scrolls in and the icon corresponding to the selected app wiggles
[09:12] <janimo> pressing alt-tab again makes an other icon start moving as well, and  I can only select the apps by clicking them
[09:13] <janimo> I'd be inclined to think this is not a feature but this being Unity I may be so wrong :D
[09:49] <davidcalle> Kamstrup, you around?
[10:02] <didrocks> zniavr: when you are back, can you make compiz crashing please and report a stacktrace?
[10:07] <zniavre>  didrocks how can i do that please?
[10:08] <didrocks> zniavre: so, sudo rm /var/crash/*crash (to clean the current crashes)
[10:08] <didrocks> zniavre: then follow https://wiki.ubuntu.com/Apport#How to enable apport
[10:08] <didrocks> installing nvidia
[10:08] <didrocks> and reboot/try to log in the unity session
[10:09] <didrocks> zniavre: once it's "blinking" (meaning it crashes but try to respawn)
[10:09] <didrocks> you can logout
[10:09] <didrocks> then, you should have a file /var/crash/*compiz*
[10:09] <didrocks> zniavre: ubuntu-bug -c /var/crash/*compiz* to report this bug (choose "full version")
[10:11] <zniavre> ok let me try (already with nvidia driver i need hav to crash compiz so)
[10:15] <zniavre> didrocks,  129mo is ok ?
[10:15] <didrocks> zniavre: seems correct :)
[10:15] <zniavre> im sending it
[10:17] <didrocks> zniavre: ping me back with the bug # then, please
[10:18] <zniavre> didrocks,  https://bugs.launchpad.net/ubuntu/+source/nux/+bug/768178
[10:18] <zniavre> ho ?
[10:18] <didrocks> zniavre: can you subscribe me to it? (it's private)
[10:19] <zniavre> as 'didrocks' ?
[10:19] <didrocks> zniavre: right :)
[10:19] <zniavre> it looks ok
[10:19] <didrocks> zniavre: can access to it, thanks!
[10:20] <didrocks> retracing to get all needed info is on the way
[10:21] <zniavre> im not sure to understand the last sentence but im trusting you    :o)
[10:21] <didrocks> zniavre: what arch is it?
[10:22] <didrocks> zniavre: don't mind, it's i386 :)
[10:28] <zniavr> didrocks, yes 32bits
[11:20] <RAOF> didrocks: A new nvidia binary driver was uploaded recently; I think it's the first 173 driver that we've had which actually works against our X server.
[11:20] <didrocks> RAOF: loicm is on it, nux is failing
[11:22] <RAOF> Hurray for getting a driver a week before release!
[11:22] <zniavre> for maverick it was 4 days before ...   :o)
[11:25] <ogra_> RAOF, s/a week before release/on final freeze day/
[11:25] <ogra_> :)
[11:39] <RAOF> DBO: Oh, I think I've got a lead on the hang-on-vblank kernel problem.  We'll see once these kernels build.  Just a FYI.
[13:12] <sladen> tedg: can I introduce you to <evaluate> who's just choiced the channel and is the author of clipit, a Clipboard manager
[13:12] <sladen> tedg: from bug #702316  it appears that there are some problems with the libindicate->notifcation area fallback
[13:13] <sladen> tedg: from running applications under a WM/Desktop Environment with libindicate support
[13:14] <sladen> evaluate: I think tedg is on US-time, we may have to wait a couple of hours
[13:14] <sladen> evalutate: in the mean-time would be able to put add/update your long explanation from #ubuntu-devel and add it to the bug report itself;  this would stop it getting lost
[13:40] <evaluate> sladen, will do so in a couple of minutes.
[13:46] <davidcalle> Hey stefano-palazzo
[13:54] <stefano-palazzo> hi davidcalle :)
[13:56] <davidcalle> stefano-palazzo, https://code.launchpad.net/~davidc3/unity-books-lens/trunk # zeitgeist stuff in trunk : )
[13:56] <stefano-palazzo> nice! I'll check it out right now
[13:57] <davidcalle> I'm pushing right now some comments to the code.
[14:17] <evaluate> sladen, I looked at the bugreport again and from what I can tell you added all the relevant information already.
[14:18] <evaluate> What exactly would you want me to add to it?
[14:20] <sladen> morning tedg
[14:20] <sladen> < sladen> tedg: can I introduce you to <evaluate> who's just choiced the channel and is the author of clipit, a Clipboard manager
[14:21] <sladen> < sladen> tedg: from bug #702316  it appears that there are some problems with the libindicate->notifcation area fallback
[14:21] <sladen> < sladen> tedg: from running applications under a WM/Desktop Environment with libindicate support
[14:23] <evaluate> sladen, tedg, I'm sorry, but I have to go now. Could you please mail me or send me a message through launchpad (if that's possible) if there is any more information that I should provide?
[14:23] <tedg> sladen, evaluate, I put instructions on getting a backtrace
[14:24] <evaluate> tedg, ok, I will update the bug with that info when I'm back. Thanks for now!
[15:21] <lamalex> cdbs, om26er are you guys working on the new queue at all? it really hasn't seemed to be going down. i've been otherwise occupied with some qa stuff and it's at 212 bugs. that's way higher than i should be
[15:21] <cdbs> lamalex: I did a lot of squashing today
[15:22] <cdbs> and yesterday as well
[15:22] <lamalex> in the new queue?
[15:22] <cdbs> lamalex: I'll speed up more tomorrow
[15:22] <cdbs> lamalex: yes
[15:22] <om26er> lamalex, I did not, I just woke and was looking in there
[15:22] <lamalex> and you set the statuses?
[15:22] <lamalex> like, the source package and the upstream package?
[15:22] <cdbs> lamalex: I was focusing more on Incomplete bugs and dups
[15:22] <lamalex> ok
[15:23] <lamalex> i'll try and get the new in order today
[15:23] <lamalex> keep going on the incompletes and dups
[15:23] <lamalex> om26er, can you work on the new queue with me?
[15:23] <lamalex> between the two of us we should be able to knock it down quite a bit before the weekend
[15:23] <cdbs> lamalex: As for the statuses, I didn't set the status to Incomplete or Confirmed on most of them because
[15:24] <cdbs> lamalex: I commented on old NEW bugs whether he could reproduce in the latest versions
[15:24] <om26er> lamalex, yes defintely
[15:24] <lamalex> om26er, cdbs so when you touch a bug, basically it should always leave the new queue
[15:24] <cdbs> lamalex: and many of them, such as bug #765447 apart from tons others were marked by the reporter themselves to be fixed
[15:24] <lamalex> i want that number to always be going down
[15:25] <lamalex> so if you ask someone if it's stilll valid, mark it incomplete until they answer
[15:25] <didrocks> om26er: hey, btw, do you want today's mismatch report?
[15:25] <cdbs> lamalex: okay, I'll take more care about that
[15:25] <om26er> didrocks, that too ;)
[15:25] <lamalex> thanks
[15:25] <didrocks> om26er: here it is :) http://paste.ubuntu.com/596975/
[15:25] <cdbs> My day ends in a few minutes, so more up tomorrow
[15:25] <lamalex> didrocks, we should get your script to just shoot of an email to the unity-bugs team ;)
[15:26] <didrocks> lamalex: hum, are you following this bugmail ML? I've the feeling that NEW bugs aren't handled
[15:26] <lamalex> didrocks, that's what we're talking about right now
[15:26] <didrocks> (especially important ones, that's why I'm scanning this quickly every morning)
[15:26] <didrocks> and seb128 too
[15:27] <lamalex> om26er and i are going to devastate the new queue backlog that's formed today
[15:27] <lamalex> and tomorrow
[15:27] <lamalex> we got it
[15:27] <didrocks> nice! :-)
[15:27] <didrocks> lamalex: where is your hammer?
[15:28]  * lamalex shows didrocks thorr's hammer
[15:28] <didrocks> heh :-)
[15:29] <didrocks> 16:25:03         lamalex | so if you ask someone if it's stilll valid, mark it incomplete until they answer
[15:30] <didrocks> lamalex: ensure then you are looking at those bugs again, because some people went upset on bugs you set as incomplete and they provided the info. Then no feedback :(
[15:31] <seb128> lamalex, oh, and also don't just ask if they still happen or bugs you could easily test on your install, that tend to annoy users as well
[15:32] <cdbs> lamalex: not me?
[15:32] <cdbs> :)
[15:41] <Omega> I think that we could use a 4th window button that when hovered over, makes the menu appear in the window decoration, that way people that want more screen-estate stay happy and those that want a menu in the window do too.
[15:44] <didrocks> cdbs: I'm certain https://bugs.launchpad.net/bugs/761267 is a dup
[15:44] <didrocks> even a seb128's bug IIRC :)
[15:45] <cdbs> didrocks: I didn't find a master bug after searching for it
[15:45]  * cdbs searches again, this time with lesser keywords
[15:48] <didrocks> cdbs: ahah bug #747323 !
[15:49] <cdbs> :o
[15:49]  * cdbs marks
[15:49] <didrocks> cdbs: edited the title :)
[15:49] <didrocks> bug #747323
[15:49] <didrocks> ubot5: ?
[15:50] <didrocks> "should not wait the key unpress to display lenses / super wait to be released to show dash/places "
[15:50]  * vish tickles ubot5  and  bug #747323
[15:50] <didrocks> should be easier to find now :)
[15:50] <didrocks> vish: not fair! :p
[15:50] <cdbs> didrocks: I'm also sure bug #766127 is a dupe of something, can't find that bug now :( blame laptop changeover
[15:50] <vish> :D
[15:50] <cdbs> seb should fix his connection :)
[15:51] <didrocks> cdbs: oh really? didn't see a dup for that one
[15:51] <cdbs> didrocks: About clicking on the area where the dash formerly existed before resizing.. remember?
[15:51] <cdbs> I'll ask the reporter on whether he meant in that area or not
[15:52] <didrocks> cdbs: oh, you're right!
[15:55] <om26er> lamalex, crashers related to nouveau experimental are invalid(if they specifically look live driver issues)?
[15:55] <om26er> bug 767322
[15:55] <apw> what does one file bugs against when the global menu isn't showing up menus for a specific application??
[15:57] <om26er> apw, indicator-appmenu might be a good place, I believe
[15:57] <apw> om26er, ok thanks
[16:02] <apw> bug #768392
[16:03] <om26er> apw, you could be seeing bug 754581
[16:03] <apw> is anyone else seeing windows un-minimise the wrong height, such that the input areas are in the right place, but the app is rendered about the height of the menu bar too low
[16:03] <apw> such that to click on something yopu have to miss high
[16:04] <didrocks> apw: we were looking for reproducible testcase of this.
[16:05] <didrocks> smspillaz: you remember that I mentionned it? ^^
[16:05] <om26er> apw, something like this https://launchpadlibrarian.net/69486382/Capture.png maybe?
[16:05] <apw> om26er, yeah exactly like that.
[16:05] <Omega> Hmm, the maximize and minimize animations aren't each other's inverse, this kinda bugs me.
[16:05] <Omega> What should I file the bug against?
[16:05] <apw> didrocks, for me i seem to occur most often to chromium, when it is unminimised by something other than me
[16:05] <didrocks> apw: talk about it to smspillaz once he's around :)
[16:06] <apw> ubuntu-bug for example, or opening a link in something like xchat
[16:06] <didrocks> apw: I got it a lot, but we had a patch in compiz which was supposed to fix it (and it did for me at least). I only saw that once since
[16:06]  * apw suspects we need to be issued with aspestos shorts for uds
[16:07] <didrocks> apw: tried that 10 times with chromium, of course, didn't happen :/
[16:07] <om26er> didrocks, did you write unity-preferences?
[16:07] <didrocks> om26er: I patched it, njpatel wrote it, why?
[16:07] <apw> didrocks, funny happend opening the link to show the issue!
[16:07] <apw> om26er, which bug is that screen shot from
[16:08] <om26er> apw bug 760436
[16:08] <didrocks> om26er: don't tell me there is bug in the 50 lines :p
[16:08] <om26er> didrocks, there is a crash ;)
[16:08] <didrocks> noooooooooooooooooooooo
[16:08] <didrocks> :-)
[16:08] <didrocks> om26er: link? ;)
[16:09] <om26er> didrocks, bug 767140
[16:12] <smspillaz> didrocks: yeah, I've got this one on the radar
[16:12] <smspillaz> didrocks: I know how to reproduce it, just not sure why it happens yet
[16:12] <didrocks> smspillaz: oh ok, is there a bug milestone for the SRU?
[16:12] <didrocks> smspillaz: unity 3.10.12?
[16:12] <didrocks> 3.8.12*
[16:13] <smspillaz> didrocks: don't know
[16:13] <didrocks> smspillaz: can you ensure it's the case please?
[16:13] <smspillaz> ok, I'll do that asap
[16:15] <cdbs> lamalex, om26er: My day ends today, will be back tomorrow, bye!
[16:15] <cdbs> my day begins much before it begins for you both :)
[16:15] <om26er> cdbs, bye ;)
[16:15] <Omega> bye
[16:15] <lamalex> bye cdbs
[16:15] <lamalex> goodnight
[16:16] <lamalex> have a good weekend
[16:16] <om26er> didrocks, what do you think about my question on if the crash caused by experimental nouveau(libgl1-mesa-dri-experiment) should be invalid? bug 767322
[16:16] <cdbs> lamalex: I'm working on weekends
[16:16] <cdbs> :)
[16:17] <cdbs> lamalex: non-stop since I came back from that trip
[16:18] <didrocks> om26er: one sec (just looked at the unity-preferences crash, seems a glib/gvariant crash, but will give a deeper look later)
[16:19] <didrocks> om26er: ok, on nouveau, I would say "we don't support nouveau as the testing and developping effort is really limited right now. However, we welcome all contribution to debug and fix this issue. Marking as triaged but prority low"
[16:19] <didrocks> om26er: does it sound good to you?
[16:19] <didrocks> (basically the same seem than the "no icon over launcher" with nouveau)
[16:20] <om26er> didrocks, wfm, should I add 'mesa' to affects?
[16:20] <lamalex> cdbs, oh ok
[16:20] <lamalex> well cool
[16:20] <didrocks> om26er: yes please ;)
[16:21] <om26er> didrocks, thx
[16:21] <didrocks> yw
[16:23] <stefano-palazzo> davidcalle, are you around?
[16:23] <davidcalle> stefano-palazzo, yes
[16:23] <stefano-palazzo> davidcalle, so, I've written a little function that suggest tags you might be interested in, even without a search query (based on running apps)
[16:23] <stefano-palazzo> Now, when do I run that function?
[16:24] <stefano-palazzo> Is there a callback that runs when you open up the lens?
[16:24] <tedg> kenvandine, Is there a way to recover gwibber posts that gwibber didn't actually post?
[16:24] <kenvandine> no
[16:24] <tedg> kenvandine, Like a log file or something?
[16:25] <stefano-palazzo> I saw in your video that results are displayed immediately; in what method do you add this stuff to the model?
[16:25] <tedg> kenvandine, :-(
[16:25] <kenvandine> tedg, i hope to be able to do that next cycle
[16:25] <kenvandine> if i get the time for the refactoring
[16:25] <kenvandine> :)
[16:25] <davidcalle> It's the "active" signal (kenvandine uses it too) look at "on_active_change".
[16:25]  * tedg will do no releases to help kenvandine
[16:25] <stefano-palazzo> davidcalle, thanks, I'll look into it :)
[16:25] <kenvandine> hehe... come to the session at UDS :)
[16:26] <davidcalle> stefano-palazzo, but it's buggy. I've seen in sent during slow or long searches.
[16:27] <davidcalle> stefano-palazzo, that's why I add a lot of conditions for it to send the call. Still some bugs though.
[16:28] <didrocks> kenvandine: about the python lenses not autostarted, where did your debugging stopped?
[16:32] <kenvandine> added some g_debug lines in unity
[16:32] <kenvandine> to make sure those assertions are really coming from the sections model
[16:32] <kenvandine> and to see when they get called
[16:33] <didrocks> hum…
[16:33] <didrocks> kenvandine: so, just to ensure
[16:33] <didrocks> kenvandine: fresh login
[16:33] <didrocks> you hover the place icon, click on it
[16:33] <didrocks> there is no search result coming, right?
[16:33] <kenvandine> right
[16:33] <didrocks> if you then, closing it and click on it again
[16:33] <kenvandine> no sections populate
[16:33] <didrocks> do they come?
[16:33] <kenvandine> and no sections in the quicklist
[16:33] <kenvandine> no
[16:33] <kenvandine> never any results
[16:33] <kenvandine> but
[16:33] <didrocks> ok, so not a race while connecting then
[16:34] <kenvandine> logging from my lens shows that it is calling all the right functions
[16:34] <kenvandine> and getting results
[16:34] <didrocks> hum…
[16:34] <kenvandine> it's just unity isn't rendering them
[16:34] <didrocks> ok, can you try something?
[16:34] <kenvandine> sure
[16:34] <didrocks> like, fresh login
[16:34] <didrocks> hover the icon
[16:34] <didrocks> (not click on it)
[16:34] <didrocks> wait for several seconds
[16:34] <didrocks> then, click on it and look if the content is there
[16:35] <kenvandine> i did that
[16:35] <kenvandine> didn't work
[16:35] <didrocks> ok, so not a race at all
[16:35] <kenvandine> i think it is a race
[16:35] <didrocks> weird that reverting the commit for lazy load worked for you
[16:35] <kenvandine> it tries to get the sections
[16:35] <kenvandine> and it gets something that isn't a dee model
[16:35] <kenvandine> and it never tries again
[16:35] <didrocks> that shouldn't happen if you hover, wait, cick
[16:36] <didrocks> click*
[16:36] <didrocks> as basically, the code is equivalent to "connect at startup"
[16:36] <didrocks> I don't see the difference with the vala lense either :/
[16:36] <didrocks> really puzzling, we need kamstrup for sure then :(
[16:37] <kenvandine> the hover produces that assertion too
[16:37] <kenvandine> not just clicking it
[16:37] <didrocks> why we didn't get that race when connecting at startup then? :/
[16:38] <didrocks> hum hum, this reminds me my french fix which was refrenched fixed…
[16:38] <didrocks> hum no in fact
[16:38] <didrocks> kenvandine: the daemon are started, isn't it?
[16:38] <didrocks> daemons*
[16:38] <kenvandine> yes
[16:38] <kenvandine> they all start just fine
[16:38] <didrocks> so yeah, not the same…
[16:39] <kenvandine> that's the thing, if the daemon is running
[16:39] <kenvandine> and you reload unity
[16:39] <kenvandine> it works fine
[16:39] <kenvandine> because it gets the sections model properly
[16:39] <kenvandine> oh... one more note
[16:39] <kenvandine> one sec
[16:39] <didrocks> yeah, I really don't see the difference with that and "connect later"
[16:39] <kenvandine> ** (<unknown>:1706): WARNING **: Unable to call GetEntries() on: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such interface `com.canonical.Unity.Place' on object at path /net/launchpad/unityplacepython
[16:39] <kenvandine> that happens the first time you hove
[16:39] <kenvandine> hover
[16:39] <didrocks> ahah
[16:40] <didrocks> so if it can't get the entries
[16:40] <didrocks> I think it discares the sections
[16:40]  * popey queues up to speak to kenvandine 
[16:40] <kenvandine> i had forgotten i saw that last night
[16:40] <kenvandine> yeah, i think so
[16:40] <kenvandine> popey, sure :)
[16:40] <didrocks> I think that's the start :)
[16:40] <kenvandine> didrocks, and it never calls GetEntries again for that lens
[16:40] <kenvandine> so when that fails, it needs to retry when it is needed again
[16:41] <didrocks> let me see the merge request again
[16:41] <kenvandine> popey, what's up?
[16:41] <popey> you know that scrolling error in gwibber?
[16:42] <popey> where it flickers up and down the timeline
[16:42] <kenvandine> popey, yeah... :(
[16:42] <popey> that
[16:42] <popey> :)
[16:42] <popey> is it something you just don't see?
[16:42] <kenvandine> i rarely see it on my laptop
[16:42] <kenvandine> the flicker that is
[16:43] <kenvandine> but i can pretty reliably reproduce it on my netbook
[16:43] <popey> wonder why that is
[16:43] <kenvandine> we just can't fix it without a huge overhaul of the UI
[16:43] <popey> oh ok
[16:43] <kenvandine> the rendering
[16:43] <kenvandine> or dropping the code that remembers your location
[16:43] <popey> it makes gwibber pretty much unusable for me.
[16:43] <kenvandine> which that bug had like a thousand dupes
[16:44] <popey> i generally never scroll it anymore
[16:44] <kenvandine> it never seems very bad for me, even on the netbook
[16:44] <kenvandine> i have to look for it to notice
[16:44] <popey> in dont understand how that can be
[16:44] <popey> mine is a dual core 2.8GHz chip with 8GB RAM and a 7900 nvidia graphics card
[16:44] <kenvandine> the suck of it is it has reposition itself with javascript
[16:44] <kenvandine> every time
[16:45] <kenvandine> weird
[16:45] <popey> so its not like its a slouch
[16:45] <kenvandine> i can usually not even see it on my laptop when i look for it
[16:45] <didrocks> kenvandine: look at https://code.launchpad.net/~unity-team/unity/lazy-places/+merge/57525, line 328. We try to get the entries there (where we did that later previously)
[16:45] <popey> ok. I'll stop nagging you about it kenvandine :) until O
[16:46] <kenvandine> popey, this should completely go away if we can get the new client done :)
[16:46] <didrocks> kenvandine: i would remove that part
[16:47] <kenvandine> yeah, man i hate c++ syntax :)
[16:47] <kenvandine> didrocks, probably better to just try to get the entries again if it fails
[16:47] <kenvandine> when they are needed that is
[16:48] <kenvandine> just moving it later might not really fix it, just mask it
[16:48] <kenvandine> i am assuming the python lenses just take longer to get on the bus
[16:54] <apw> is the stacking of the window thingy which appears on pressing super behind everything else a known bug ?
[16:55] <om26er> invisible window?
[16:55] <apw> no the one the dash produces on pressing and releasing super (win0
[16:55] <apw> (win)
[16:56] <apw> with the search box in the top,
[16:57] <apw> bah can't get a print screen of it, cause the stuupid window is up
[16:59] <apw> i'll assume its just a new bug
[17:00] <Saamm> how can i find my wine apps in unity? they are no where :(
[17:01] <om26er> Saamm, sam i thought wine apps showned up in search results
[17:01] <seiflotfy> hey ted
[17:01] <Saamm> om26er, oh I have to use search?
[17:02] <om26er> Saamm, might also be visible in 'all applications' if I am not mistaken (but they are not categorised, for now :/)
[17:02] <Saamm> om26er, oh too bad i dont remeber what things i installed :(
[17:05] <davidcalle> Saamm, what happens when searching "wine"?
[17:06] <davidcalle> hmm
[17:06] <seiflotfy> tedg, i am working on the https://bugs.launchpad.net/bugs/738555 looking good
[17:06] <seiflotfy> :)
[17:06] <tedg> seiflotfy, Yeah, why can't you just connect to gnome-session?
[17:06] <Saamm_> davidcalle, it shows wine apps but the problem is there 10-12 app shortcuts for wine and i don remember them...for searching to work you need to know what things you have installed
[17:06] <tedg> seiflotfy, It seems like catching the error is only removing the symptom
[17:08] <Saamm_> davidcalle, typing wine does not show all installed wine apps but a few
[17:09] <seiflotfy> tedg, connecting to the gnome-sesstion is not the job of zeitgeist
[17:09] <seiflotfy> because it will make it gnome dependant
[17:09] <seiflotfy> tedg, also there is no dataloss happening
[17:10] <davidcalle> Saamm_, https://bugs.launchpad.net/unity/+bug/753276
[17:10] <tedg> seiflotfy, Okay, connect to XSMP.  Something that is in the user's session should connect to session manager.
[17:10] <seiflotfy> tedg, this issue will happen with other applciations too
[17:11] <doctormo> hey seiflotfy
[17:11] <seiflotfy> tedg, will it guarantee that home directory is not re-encrypted before the session ends
[17:11] <Saamm_> davidcalle, uhm wil it be solved before release?
[17:12] <tedg> seiflotfy, Yes, you can inhibit until you're done saving.  I'd use gnome-session as an optional dep (it's dbus, so you can detect it) because the interface is WAY easier.
[17:12] <seiflotfy> tedg, i can do it as an extension
[17:12] <seiflotfy> making it an optional dependency
[17:12] <seiflotfy> or better yet
[17:12] <seiflotfy> implement it in the datahub
[17:12] <seiflotfy> since the datahub is a gnome specific implementation
[17:13] <davidcalle> Saamm_, I don't think so.
[17:13] <seiflotfy> tedg, the problem is i think the last unloading is anyhow unnecessary
[17:13] <seiflotfy> but let me check again
[17:13] <tedg> seiflotfy, It also may make sense to log session closing as an event in the DB.  For instance why I closed all those files.
[17:14] <Saamm_> davidcalle, oh :(
[17:14] <seiflotfy> tedg, tyeah
[17:14] <seiflotfy> tedg, ok i am on it
[17:14] <seiflotfy> :)
[17:15] <seiflotfy> tedg, can u link me with XSMP docu?
[17:15] <nerochiaro> smspillaz: quick x11 question, for when you have a spare minute: is it always safe to call XCompositeRedirectSubwindows on the root window with CompositeRedirectAutomatic ? or are there cases when doing it can cause issues if the WM or other clients already requested redirection ?
[17:15] <tedg> seiflotfy, I can, but it may prove cruel :-)  I'd really suggest using gnome-session here....
[17:16] <tedg> seiflotfy, http://www.x.org/releases/X11R7.6/doc/libSM/xsmp.html
[17:16] <seiflotfy> tedg,  the problem i dont think writing an extension will make it into natty
[17:16] <seiflotfy> but fixing this over a try catch could make the natty fix
[17:17] <tedg> seiflotfy, Eh, well at this point not much will make it into Natty.  I think we're talking SRU anyway.
[17:17] <seiflotfy> since really all we are doing is updating when the last time an application sent us a notification
[17:17] <seiflotfy> tedg, true
[17:17] <seiflotfy> ok so i am on it
[17:17] <tedg> seiflotfy, The catch should probably go in irregardless -- just incase the home directory is full for instance.
[17:17] <seiflotfy> tedg, ok
[17:17] <seiflotfy> so i am writing an extension to log the start and the end of the session
[17:17] <seiflotfy> :)
[17:18] <seiflotfy> if we do it using XSMP i can make it as part of the engine
[17:18] <seiflotfy> using gnome-session will make it land as an extension
[17:18] <seiflotfy> so i need to figure that out
[17:18] <seiflotfy> tedg, can u open a bug abotu having to log the start and the end of a session
[17:18] <seiflotfy> ?
[17:18] <tedg> seiflotfy, Yeah, just FYI, the GNOME guys *hate* XSMP and want to not support it anymore.  I think that they'll never be able to ditch it, but eh, they might anyway.
[17:19] <tedg> seiflotfy, Sure
[17:21] <tedg> seiflotfy, bug 768437
[17:21] <seiflotfy> tedg, awesome
[17:21] <seiflotfy> so this should make it with our next release
[17:21] <seiflotfy> tedg, i am working on reducing the memory footprint
[17:22] <tedg> seiflotfy, Ah, always a good thing :-)
[17:22] <tedg> seiflotfy, Ditching Python? ;-)
[17:23] <seiflotfy> tedg, no way
[17:23] <seiflotfy> tedg, problem is ditching python wont make zeitgeist any faster
[17:23] <seiflotfy> tedg, we spend most of our time in dbus and sqlite
[17:23] <seiflotfy> :)
[17:24] <tedg> seiflotfy, Would probably reduce memory though.
[17:24] <seiflotfy> tedg, true
[17:24] <seiflotfy> but memory is cheap now adays
[17:24] <seiflotfy> :P
[17:24] <seiflotfy> maybe if i use couchdb zeitgeist will be faster
[17:24] <tedg> Probably not :-)
[17:26] <seiflotfy> i was kidding
[17:26] <seiflotfy> :P
[17:26] <seiflotfy> but i just discovered __slots__ in python
[17:27] <seiflotfy> which is 6x more memory effciant than __dict__
[17:42] <davidcalle> stefano-palazzo, I really like how you "ps aux" for your lens, this is clever!
[17:42] <stefano-palazzo> davidcalle, thanks :)
[17:42] <stefano-palazzo> I just pushed it in rev. 41
[17:43] <stefano-palazzo> I'm not at all sure it that it'll work perfectly, but I'm going to push it to the PPA still - while that is still acceptable
[17:43] <stefano-palazzo> It won't be in a few days time :)
[17:43] <stefano-palazzo> davidcalle, I take it you saw the video?
[17:44] <davidcalle> stefano-palazzo, nope, just looking at your commit.
[17:44] <stefano-palazzo> you need to get into the Ask Ubuntu chat ;-)
[17:44] <stefano-palazzo> http://www.youtube.com/watch?v=qgWKcVzFuVI ← here it is
[17:45] <davidcalle> stefano-palazzo, this is really cool
[17:48] <davidcalle> stefano-palazzo, you should order the tags based on what's taking the most mem: when an app breaks or freezes it ususally does.
[17:48] <stefano-palazzo> I'm going to request a build and cross my fingers it doesn't break
[17:48] <davidcalle> :)
[17:49] <stefano-palazzo> davidcalle, that's a good call, I'll do that!
[17:51] <davidcalle> I'm trying to break evolution to see how it appears when broken in ps aux... and I can't! Usually, a click is enough :P
[19:13] <evaluate> Hello.
[19:14] <evaluate> tedg, ping?
[19:14] <evaluate> tedg, I have attached the requested debug output to https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/702316
[19:15]  * tedg click
[19:15] <evaluate> If you have the time to take a quick look at it and just tell me if I've done it correctly I'd be very thankful.
[19:20] <om26er> my workspace switcher just changed to the old icon, bug or bling bling ?
[19:20] <tedg> evaluate, Hmm, is there any chance you could grab the libappindicator debug package?
[19:21] <evaluate> tedg, sure. How exactly do I do that? Just install the libappindicator-dbg ?
[19:21] <tedg> evaluate, I'd be libappindicator1-dbgsym
[19:22] <tedg> evaluate, https://wiki.ubuntu.com/DebuggingProgramCrash
[19:23] <zniavre> https://bugs.launchpad.net/ubuntu/+source/nux/+bug/768178  > thank you for the "workaround" at least i know i hav to wait
[19:23] <zniavre> what is SRU please?
[19:23] <om26er> zniavre, stable release update
[19:23] <zniavre> ho i see thank you
[19:25] <evaluate> tedg, and after install the debug package, recompile my app and rerun that command?
[19:26] <tedg> evaluate, You shouldn't need to recompile
[19:26] <evaluate> ok
[19:28] <evaluate> tedg, http://dl.dropbox.com/u/9596802/indicator-debug2.txt
[19:28] <evaluate> There aren't any major differences between the two from what I can tell though...
[19:28] <tedg> evaluate, The big difference is the function name in #5
[19:30] <tedg> evaluate, You said that this happens after opening the menu a few times?
[19:30] <evaluate> It's not really opening. To reproduce the problem I just double/triple click the systray icon...
[19:31] <tedg> evaluate, What happens if you single click?
[19:32] <evaluate> I have done it slowly now. First click -> menu pops up, second click -> menu disappears, third click -> freeze
[19:33] <tedg> evaluate, Does this happen on Natty?
[19:34] <evaluate> From what the bug report says, yes. I couldn't test it on natty yet, because I don't have one installed with a DE that doesn't support indicators (if the icon is run in indicator 'mode', the problem doesn't exist, it only appears if the DE doesn't support indicators and thus the fallback gets applied).
[19:35] <tedg> evaluate, Okay, so I think this is the result of a patch that we've applied in Natty that I don't think has been backported yet.  It's basically that we're referencing the menu wrong, so the first time it's fine, but then when it gets unref'd on close it gets destroyed.
[19:36] <tedg> evaluate, So my thought is that it's fixed in Natty and we're waiting on a backport to Maverick.  But, I'd prefer if we *knew* that.
[19:36] <evaluate> ok, let me see if I can run awn without indicator in maverick and reproduce that.
[19:37] <evaluate> s/maverick/natty/
[19:37] <tedg> evaluate, Great, thanks.  I'm looking for the bug so we can bitch about the no-backport thing :-)
[19:41] <tedg> evaluate, bug 569273
[19:44] <tedg> kenvandine, So it seems on bug 569273 the gpm patch was backported to Maverick instead of the libappindicator one...
[19:44] <tedg> kenvandine, Which seems... backwards.
[19:44]  * kenvandine doesn't understand
[19:44] <tedg> kenvandine, I'm a bit confused on where to go from here.
[19:44] <evaluate> tedg, do you want me to request a backport to maverick/lucid? I'd think it would have a higher change of getting backported fast if the request comes from *you*... :-p
[19:45] <kenvandine> evaluate, requests from tedg go to /dev/null
[19:45] <kenvandine> :)
[19:45] <tedg> kenvandine, mterry found a bug in libappindicator, but worked around it in gpm.  So then the gpm patch was put into Maverick instead of the libappindicator fix.
[19:45] <evaluate> kenvandine, lol
[19:45] <tedg> kenvandine, So, I think that evaluate's bug is because the libappindicator patch is needed.
[19:46] <kenvandine> tedg, you mean only one part of the patch...
[19:46] <tedg> kenvandine, Well, no.  The problem is that if libappindicator is fixed I think the gpm patch needs to be reverted...
[19:47] <kenvandine> oh
[19:48] <kenvandine> but maverick doesn't have libappindicator does it?
[19:48] <tedg> I really don't even know *how* to write that SRU :-)
[19:48] <kenvandine> so was the fix uploaded to i-a for maverick?
[19:48] <tedg> Well it's a binary package that's built from indicator-application source.
[19:49] <kenvandine> right
[19:49] <kenvandine> but was the fix SRU'd for maverick?
[19:49] <evaluate> tedg, although, if this is supposedly fixed in natty, I wonder what the bug is about...
[19:49] <kenvandine> if not the work around in gpm is the best we have still
[19:49] <tedg> kenvandine, The gpm, yes.
[19:49] <evaluate> I mean, the bug is submitted against natty+fluxbox...
[19:49] <kenvandine> tedg, it seems we just need to have one or the other in maverick
[19:50] <evaluate> and it seems to be the same error...
[19:50] <tedg> kenvandine, Correct, either one or the other.  But the libappindicator one is better IMO.
[19:50] <kenvandine> tedg, worth a SRU?
[19:50] <tedg> evaluate, Hmm, so we should make sure they're the same.
[19:50] <kenvandine> tedg, if that is the case, we create an SRU for that and also affects gpm package with a note that the patch needs to be reverted
[19:51] <tedg> kenvandine, I think that if evaluate's bug is the same, yes.  If not, perhaps not.
[19:51]  * kenvandine thinks tedg is creating to much work
[19:51] <evaluate> tedg, sure, I'm downlading the latest natty nightly right now and will test against that
[19:51] <tedg> kenvandine, if all the fallbacks for any libappindicator using program are broken :-)
[19:52] <kenvandine> tedg, sure :)
[19:54] <evaluate> I've also had the same report for lucid (I think that's where the indicator was first introduced). If this is indeed the problem, shouldn't it also be backported to lucid, since that is a LTS?
[19:56] <tedg> evaluate, That'd be my thought -- but let's get Maverick first :-)
[20:09] <seiflotfy> tedg, http://imgur.com/a/huEIc#FnpAa
[20:09] <seiflotfy> what do u think
[20:15] <akshatj> seiflotfy, GTK3 please :P
[20:17] <seiflotfy> akshatj, yeah
[20:20] <lamalex> seiflotfy, can you have it only not log for chrome in private mode or is it all or nothing
[20:21] <evaluate> tedg, installing the nightly, will take a couple more minutes.
[20:21] <tedg> seiflotfy, Will it go into gnome control center?
[20:23] <seiflotfy> lamalex, the chrome plugin respect the chrome private mode
[20:23] <seiflotfy> lamalex, look at all the pictues
[20:23] <seiflotfy> u can add applciations not to be logged
[20:23] <seiflotfy> and u can go into incognito mode
[20:28] <lamalex> cool
[20:38] <seiflotfy> :)
[21:59] <evaluate> tedg, kenvandine, https://bugs.launchpad.net/ubuntu/+source/clipit/+bug/702316 -- updated with the log output from natty. The problem still exists in natty, so I guess this isn't the patch that tedg was talking about.
[21:59] <kenvandine> evaluate, thx
[22:01] <evaluate> kenvandine, sure. I hope you guys can identify the problem...
[22:01] <kenvandine> me too :)
[22:01] <kenvandine> thx for verifying that
[22:07] <evaluate> kenvandine, I have to go to sleep now. If tedg shows up in the meantime, could you please let him know?
[22:31] <m4n1sh> tedg: ping
[22:32] <m4n1sh> tedg: whenever you have time please, look at this https://bugs.launchpad.net/zeitgeist/+bug/768437
[22:32] <tedg> Hey m4n1sh what's up?
[22:32] <m4n1sh> tedg: I saw you reported a bug about zeitgeist
[22:33] <tedg> m4n1sh, https://bugs.launchpad.net/zeitgeist/+bug/768437/comments/2
[22:34] <m4n1sh> tedg: thanks. That can be done
[22:35] <m4n1sh> wrt to file open & close logging, it is already there