[01:59] <Nikonn> hi there
[11:33] <smspillaz> MCR1: hola, no problem
[11:33] <smspillaz> MCR1: were you able to grab my branch
[11:33] <smspillaz> ?
[11:34] <MCR1> smspillaz: Which one ?
[11:34] <smspillaz> I put it on the review
[11:34] <smspillaz> one of your reviews ... the wobbly optimizations I think
[11:35] <smspillaz> btw, I fixed --replace \o/ https://code.launchpad.net/~compiz-team/compiz/compiz.fix_1085591/+merge/137524
[11:36] <MCR1> smspillaz: That are great news :) It would be important to make Compiz shut down and restart properly...
[11:38] <MCR1> smspillaz: Now I got it. What about proposing your branch to merge instead of my wobbly-optimizations as it is already stacked on mine as far as I see...
[11:38] <MCR1> ?
[11:38] <smspillaz> MCR1: *shrug*, if you want.
[11:39] <smspillaz> or just merge it in directly
[11:39] <smspillaz> no need for a formal proposal
[11:39] <smspillaz> or - take the bits you want and get rid of the ones you dont
[11:40] <MCR1> ok, if you like that better, I can ofc do it also... No problem - I'll do it (just have to read through all the arguments ;))
[11:41] <MCR1> smspillaz: We have a big problem with keyboard resized Grid windows...
[11:41] <MCR1> See here: bug 1082001
[11:41] <smspillaz> MCR1: yah, saw
[14:29] <didrocks> bregma: hey can you please review https://code.launchpad.net/~sil2100/unity/more_arm_test_modifications/+merge/137558?
[14:29]  * bregma looks
[14:30] <didrocks> bregma: hopefully hopefully hopefully arm* will be building back!
[14:30] <bregma> it's been a long haul
[14:30] <sil2100> It was building! Sometimes!
[14:30] <sil2100> The worst thing, my pandaboard is free of these problems
[14:31] <sil2100> I was running check-headless in a loop today for about 30 minutes and no failures
[14:40] <didrocks> bregma: once this is checked, so, we are waiting on getting some autopilot tests results, but we already have that as a blocker: https://bugs.launchpad.net/compiz/+bug/1085581
[14:40] <didrocks> bregma: see also my comment for a screenshot of a (I guess) related issue
[14:49] <didrocks> seb128: if you have time can you install from the ~ubuntu-unity ppa please? So that we test the latest (there is this bug above already ^)
[14:49] <popey> didrocks, ppa:ubuntu-unity/ppa ?
[14:50] <didrocks> popey: ubuntu-unity/daily-build
[14:50] <popey> ta
[14:50] <didrocks> popey: thanks! :)
[14:50] <seb128> didrocks, dist-upgrade with the ppa (e.g whole stack) or specific component ?
[14:50] <didrocks> whole stack should be good
[14:50] <seb128> ok
[14:50] <seb128> is there anything special to test?
[14:50] <didrocks> the rest (non directly unity) has been released this morning
[14:50] <seb128> was that about the stacking bug?
[14:50] <seb128> or just general testing?
[14:51] <didrocks> seb128: general testing
[14:51] <seb128> didrocks, doing it
[14:51] <didrocks> it's not a stacking bug
[14:51] <didrocks> it's just the window doesn't open at the right place
[14:51] <seb128> ok
[14:51] <didrocks> + this dash weirdery
[14:51] <didrocks> thanks seb128 :)
[14:53] <popey> didrocks, still getting that, windows appear under the launcher
[14:53] <popey> under launcher and panel in fact
[14:54] <didrocks> popey: thanks for confirming. And if you move the window and open the dash
[14:54] <didrocks> do you have what I saw?
[14:54] <popey> hmm, i get a black dash didrocks
[14:54] <popey> (vm)
[14:54] <didrocks> ah ok :)
[15:00] <didrocks> bregma: can you put someone on to fix those? (the 2 issues that are signaled/maybe related here) ^
[15:02] <bregma> I've already asked dednick to look at the transparency problem (looks like a bug in unity), nobody who knows compiz is on right now so the window positioning may have to wait for a few hours
[15:03] <popey> sil2100, would you be able to look at the window positioning issue above ?
[15:03] <didrocks> bregma: thanks a lot (please communicate ;))
[15:03] <sil2100> popey: I shall as soon as I get upgraded
[15:50] <bregma> didrocks, dednick can't repro that transparency problem with trunk, can any one else?
[15:51] <popey> bregma, i get an odd transparency issue, yes
[15:52] <popey> not the same as didrocks, I get a black background wherever things should be transparent, but this is in a VM so not sure I trust it
[15:52] <bregma> popey, the same one didrocks described?
[15:52] <popey> no, let me get a screen grab
[15:52] <bregma> ah\
[15:52] <popey> it looks transparency related, but not the same
[15:53] <bregma> it could be related to depth buffer support in the VM
[15:53] <popey> it worked before I updated
[15:58] <popey> bregma, http://popey.com/~alan/transparency.png
[17:01] <didrocks> bregma: back, not sure what seb128 saw (or sil2100)
[17:01] <didrocks> bregma: I bet this transparency issue is due to the offset we are seeing
[17:01] <didrocks> bregma: like unity thinking that 0 0 is somewhere and compiz thinking something else
[17:02]  * seb128 shakes fist at didrocks
[17:03] <didrocks> seb128: hum? is the ppa that bad for you?
[17:05] <popey> we need btrfs so we can snapshot before adding crack-fuelled ppas :)
[17:06] <seb128> didrocks, having everything opening on the top left means I can't access the decoration to move windows without using alt-click
[17:06] <seb128> didrocks, it's a pain
[17:06] <seb128> the decorations and wm controls are under the panel/launcher
[17:06] <popey> yeah, i have to Alt+Space, M, to do "move"
[17:07] <popey> or alt+f7
[17:08] <didrocks> seb128: well, you were warned :p
[17:08] <didrocks> seb128: seems sil2100 doesn't reproduce it
[17:08] <didrocks> and nothing is moving because despite asking to try a ppa, people don't use exactly that one
[17:12] <seb128> didrocks, using that ppa the gwibber lens is broken otherwise
[17:12] <didrocks> shrugh :/
[17:12] <didrocks> how broken? kenvandine ^
[17:12] <seb128> unity_filter_get_filtering: assertion `self != NULL' failed
[17:12] <seb128> Erreur de segmentation (core dumped)
[17:12] <seb128>  
[17:13] <seb128> segfault on start
[17:13] <seb128> (gdb) bt
[17:13] <seb128> #0  0xb7eda463 in dee_serializable_parse ()
[17:13] <seb128>    from /usr/lib/i386-linux-gnu/libdee-1.0.so.4
[17:13] <seb128> could be the dee in the ppa...
[17:13] <seb128> mhr3, ^
[17:14] <kenvandine> ugh
[17:14] <seb128> didrocks, otherwise I confirm, launcher transparency is broken
[17:14] <mhr3> seb128, bug in dee, really? :P
[17:15] <seb128> mhr3, gdb is saying so!
[17:15] <mhr3> gdb likes to lie :P
[17:16] <seb128> we have no debug package in the ppa though
[17:16] <seb128> mhr3, kenvandine: do you guys want a debug stacktrace?
[17:16] <mhr3> seb128, then i can't help you
[17:16] <mhr3> yes
[17:16] <seb128> mhr3, alright, getting one
[17:17] <mhr3> seb128, meanwhile do you have non-debug one?
[17:18] <seb128> mhr3, http://paste.ubuntu.com/1408256/
[17:19] <seb128> mhr3, http://paste.ubuntu.com/1408260/
[17:19] <seb128> debug one
[17:19] <mhr3> hmm, that actually could be me :)
[17:19] <seb128> mhr3, http://paste.ubuntu.com/1408262/
[17:19] <seb128> the bt full version
[17:20] <seb128> mhr3, see, gdb is not lying, there is your name all over that stacktrace ;-)
[17:20] <didrocks> bregma: dednick is testing on raring, right?
[17:20] <seb128> mhr3, that's r390 if didrocks's changelog automagic is doing its maths correctly
[17:20] <mhr3> meh, ok, it's actually my improvement uncovering kamstrup's bugs :P
[17:20] <seb128> lol
[17:21] <bregma> didrocks, he's using trunk, which should match the PPA
[17:21] <didrocks> bregma: on raring?
[17:22] <mhr3> seb128, can you try with http://paste.ubuntu.com/1408266/ ?
[17:23] <seb128> mhr3, that fixes the segfault, still getting those warnings but that might be a different issue
[17:23] <seb128> unity_filter_get_filtering: assertion `self != NULL' failed
[17:24] <mhr3> seb128, do things work though?
[17:24] <seb128> mhr3, the lens work yes
[17:25] <mhr3> then let's say it's incorrect usage of the lens, but it works so meh... :)
[17:29] <seb128> mhr3, yeah ;-)
[17:30] <seb128> didrocks, kenvandine, mhr3: I've approved https://code.launchpad.net/~mhr3/dee/fix-slist-iteration/+merge/137638 since it looks correct and fix my gwibber lens segfault
[17:30] <bregma> didrocks, he's using quantal -- what makes you think that's important?
[17:31] <mhr3> seb128, thx
[17:32] <seb128> mhr3, thank you for the quick fix ;-)
[17:32] <kenvandine> cool
[17:32] <mhr3> seb128, that bug was in dee for a year, was about time :P
[17:32] <didrocks> bregma: see the discussion with sil2100 who can't reproduce it on quantal
[17:32] <kenvandine> thx seb128, mhr3
[17:33] <didrocks> bregma: did you give it a shot on your machine? I'm sure you are using raring :)
[17:33] <seb128> mhr3, hehe
[17:34] <bregma> didrocks, I've been reinstalling my raring machine for the last hour, so not yet
[18:06] <didrocks> sil2100: great to see that there is no more FTBFS on armfh! :)
[18:09] <sil2100> Phew!
[18:09] <sil2100> didrocks: \o/
[18:09] <sil2100> But I really really hated those TestAnimator tests
[18:09] <didrocks> sil2100: you can tell that you only needed one hand to fix this :p
[18:10] <sil2100> Well ;p I could have said 'screw you TestAnimator' last week from the start
[18:10] <sil2100> Since making them less strict didn't help completely ;p
[18:10] <didrocks> sil2100: yeah, well, it worthed a try at least
[20:03] <krabador> hi people, i installed nvidia offical 173 drivers, on ubuntu  12.10, with "direct rendering: Yes", but when i try to run unity, i've 2 second the wallpaper and later blank screen and mouse pointer
[20:03] <krabador> no problem with gnome without effects
[20:05] <krabador> someone can tell me if unity have some feature not supported by the driver or the card?