[04:29] <bschaefer> e
[09:42] <MCR1> didrocks: Hi :) Is it okay to add bug reports here: https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-unity-polish ?
[09:43] <MCR1> om26er: Hi :) Do you have a minute to reproduce and confirm a Compiz bug (easy to reproduce) ?
[09:43] <didrocks> MCR1: do you want to fix them?
[09:43] <om26er> MCR1, sure
[09:44] <om26er> hope it doesn't involve any compiling ;)
[09:44] <MCR1> didrocks: Sure, but I might fail with some of them - but it is also because of the papercuts project, which needs targets...
[09:44] <didrocks> mmrazik: can you please review https://code.launchpad.net/~didrocks/xpathselect/copyright/+merge/136883
[09:44] <didrocks> MCR1: so please don't add them
[09:44] <MCR1> om26er: Nope.
[09:44] <didrocks> MCR1: maybe youneed another blueprint
[09:44] <didrocks> MCR1: but those are the ones we commit to fix in the cycle
[09:45] <mmrazik> didrocks: so canonical prefers gpl3?
[09:45] <MCR1> didrocks: But important ones are really missing in this list
[09:45] <om26er> if a person has teeth outwards and triages bugs one could call him Bugs Bunny ^^ :D
[09:46] <didrocks> mmrazik: gpl3 or gpl2, but there is no sense to have 2 stenzas, one for upstream, one for the packaging
[09:46] <didrocks> mmrazik: and it should be copyright canonical anyway, not one any one's name
[09:46] <MCR1> om26er: It is this one: bug 1082001
[09:46] <mmrazik> didrocks: understood
[09:46] <didrocks> MCR1: well, important are relative :)
[09:47] <MCR1> didrocks: Windows jumping around from workspace to workspace ?
[09:47] <mmrazik> lets see if the autolanding works :)
[09:47] <MCR1> bug 1082001
[09:47] <MCR1> grmpf, what is wrong - no bot ?
[09:47] <MCR1> https://bugs.launchpad.net/compiz/+bug/1082001
[09:47] <MCR1> om26er: ^^
[09:48] <om26er> MCR1, what could one do if they don't have numpad ?
[09:48] <didrocks> mmrazik: I had a double stenza, just pushed rev 25 and reapproved
[09:48] <MCR1> om26er: Then you might have to change the grid keyconfig in CCSM
[09:49] <didrocks> MCR1: this is an opportunity, but if you look at the list, we have way more important bugs to tackle first :)
[09:50] <mmrazik> didrocks: FYI (still in progress): http://10.97.0.1:8080/job/ps-unity-autopilot-raring/35/
[09:50] <mmrazik> didrocks: I'll just need few more runs as build #34 had quite a bit of failures on nvidia (~10%)
[09:50] <mmrazik> #35 seems to be ok
[09:50] <didrocks> mmrazik: ok, great! :)
[09:51] <mmrazik> didrocks: the failures from yesterday were a bug in our preseed (coming with the binary nvidia driver changes)
[09:51] <mmrazik> dist-upgrade failed so the stuff from staging ppa wasn't installed
[09:51] <didrocks> ah great ;)
[09:51] <didrocks> so, let's cross fingers now
[09:52] <om26er> MCR1, yeah, the window hides from the spread for me
[09:52] <MCR1> didrocks: Do not misunderstand me, I just was asked by notgary to help with identifying valid Compiz/Unity bugs...
[09:52] <om26er> MCR1, but when i get back to the workspace the window reappears
[09:52] <didrocks> MCR1: no worry ;)
[09:54] <MCR1> om26er: The "keyboard-gridded" window should stay on the workspace it is, but it will follow the second window if you move it on another workspace ?
[09:54] <MCR1> which is quite nasty behavior isn't it ?
[09:55] <om26er> MCR1, yes, confirmed that as well
[09:55] <om26er> MCR1, i am marking bug as confirmed
[09:56] <MCR1> I think we should eliminate bugs like this, which move windows around without the user wanting it as those make Compiz feel really buggy
[09:56] <MCR1> om26er: Thanks 4 testing.
[09:57] <om26er> MCR1, i would rather love to see spread re-written, its full of all kinds of troubles ;)
[09:58] <MCR1> om26er: A lot of trouble comes from wrong grid behavior...
[09:59] <MCR1> om26er: For example this one is also tightly related: https://bugs.launchpad.net/compiz/+bug/1081601
[10:00] <om26er> MCR1, I fully agree grid is broken as well :/
[10:00] <MCR1> here Grid holds the window in its place and does not let it leave...
[10:00] <MCR1> om26er: What are the spread troubles ?
[10:03] <om26er> MCR1, there is a list, first the overall look of it, doesn't match well with unity's overall design, then there are a few features from different shells that would make it usable (tm)
[10:08] <MCR1> om26er: If you are on it, please confirm this one also: https://bugs.launchpad.net/compiz/+bug/1081601
[10:08]  * om26er looks
[10:08] <MCR1> thx
[10:14] <MCR1> om26er: You are running Unity from the staging PPA ?
[10:14] <om26er> MCR1, yes I am and i have still not tested the above bug, got sidetracked, now testing
[10:15] <MCR1> :)
[10:17] <om26er> MCR1, compiz-plugins-extras not installable in staging ppa ?
[10:18] <MCR1> om26er: you do not need them, we now just have compiz-plugins
[10:18] <MCR1> showdesktop should be there
[10:19] <om26er> compiz-plugins-extras depends compiz-plugins which is not installable :p
[10:19] <MCR1> one moment
[10:20] <MCR1> you just need compiz-plugins and compiz-plugins-default
[10:20] <MCR1> simply remove all the old metapackages
[10:21] <MCR1> aehm "transitional dummy packages"
[10:21] <MCR1> om26er: Got it ?
[10:22] <om26er> MCR1, there are a few updates installing, let me try after that. (almost one)
[10:22] <om26er> *done
[10:23] <om26er> MCR1, i am just purging the ppa
[10:23] <MCR1> ouch
[10:31] <om26er> MCR1, just so that i am sure, enabling show desktop asks me to disable unity plugin
[10:32] <om26er> is that fine?
[10:32] <MCR1> no, just fadedesktop should tell you that - I think didrocks removed my patch from Quantal - so you need the staging PPA
[10:33] <didrocks> yep :)
[10:34] <MCR1> it is just another manifestation of the same Grid bug we tested before...
[10:35] <MCR1> namely keyboard-shortcut resized Grid windows acting crazy... :(
[11:51] <MCR1> didrocks: So if I understand you correctly, I can add those to the Compiz/Unity blueprint I am able to fix in this cycle ?
[11:51] <didrocks> MCR1: right, with your launchpad name in front, like [yourname]
[11:51] <didrocks> MCR1: or assigned to the bug if you link a bug
[11:51] <MCR1> ok
[12:22] <mmrazik> didrocks: interesting... build #36 is clean-ish even on intel:
[12:22] <mmrazik> https://jenkins.qa.ubuntu.com/job/ps-unity-autopilot-raring/36/
[12:25] <didrocks> mmrazik: weird, we good an issue with appmenu-gtk, but I don't think it's what impacted you
[12:25] <didrocks> mmrazik: so, thumper landed a big branch in trunk
[12:26] <didrocks> mmrazik: is it with that one?
[12:26] <didrocks> he basically removed a lot of bamf relationship
[12:26] <mmrazik> didrocks: do you know which revision is the thumper's merge?
[12:26] <mmrazik> wel... I can find out myself..
[12:27] <mmrazik> didrocks: build #36 is with 6.12.0bzr2936pkg0raring0  which is prior thumper's changes
[12:28] <didrocks> ok, so it's not that one
[12:28] <didrocks> mmrazik: seeing how big this merge is, I would prefer that we rerun with it btw
[12:29] <didrocks> btw i386?
[12:29] <mmrazik> didrocks: running already
[12:29] <mmrazik> didrocks: yes
[12:30] <didrocks> mmrazik: great!
[12:30] <didrocks> let's see how it goes :)
[14:10] <mmrazik> didrocks, fginther: Run including Tim's changes: https://jenkins.qa.ubuntu.com/job/ps-unity-autopilot-raring/37/
[14:10] <mmrazik> I wonder where the nvidia failures disappear
[14:10] <mmrazik> ed
[14:12] <didrocks> mmrazik: proprieratery driver, right?
[14:12] <didrocks> isn't what the failure was about without them?
[14:13] <didrocks> sil2100: how is it going on the armhf front? Seems it's the latest blocker
[14:13] <mmrazik> didrocks: yes... but #34 also had  a binary driver and for some reason there were about ~50 failures
[14:13] <mmrazik> its really hard to figure out stuff if there are so many variables :-/
[14:13] <mmrazik> the joy of system level testing
[14:13]  * mmrazik would never say he will be worried when a fail rate drops
[14:14] <didrocks> mmrazik: right, I guess at least, we don't jump from 20 to 100
[14:15] <didrocks> mmrazik: so, once the armhf thing is fixed, I guess we can try to do the whole stack for trying, without uploading
[14:15] <didrocks> mmrazik: with all the jobs chained
[14:15] <didrocks> wdyt?
[14:15] <mmrazik> didrocks: +1
[14:15] <didrocks> sweetness ;) let's wait for sil2100's status
[14:16] <mmrazik> didrocks: we will need to change the staging ppa to something else, right?
[14:16] <didrocks> mmrazik: right ~ubuntu-unity/daily-build
[14:16] <didrocks> mmrazik: and you can consider I only launch the job when i386 is published
[14:16] <didrocks> let's see if jibel is available
[14:33] <sil2100> didrocks: almost done, testing the modifications on my pandaboard, and this sadly takes some time to compile on this platform ;/
[14:34] <didrocks> sil2100: good to know that you have good progress! :)
[14:40] <mmrazik> sil2100: out of curiosity... how much time do you need to compile unity on panda?
[14:40] <mmrazik> do you have numbers for compiz too?
[14:43] <sil2100> mmrazik: don't have the numbers, but I can count the build time right now
[14:43] <sil2100> mmrazik: for unity
[14:43] <mmrazik> sil2100: thx
[14:43] <sil2100> mmrazik: but it takes rather a lot
[14:44] <mmrazik> sil2100: like 1h or more like 6h?
[14:56] <sil2100> mmrazik: I think more like around 2 hours
[16:35] <didrocks> sil2100: how is it going? good news?
[18:31] <didrocks> bregma: hey, if you have access to the oif daily recipe, maybe it's time to kill them? (and remove the spam ;))
[18:31] <bregma>  sure thing
[18:32] <didrocks> thanks!
[20:45] <bobweaver> reading log ^^ when will this change in stagging happen ?
[20:46] <bobweaver> mmrazik,  it took me like 15 minutes on panda board
[20:46] <bobweaver> friends board ^^
[20:47] <bobweaver> maybe 20
[20:49] <bobweaver> compiz was like 35 too 50  min  all together I was at house for about 6 hours
[21:46] <sil2100> bobweaver: 20 minutes building on a pandaboard?
[21:46] <sil2100> Maybe my USB disk is the problem
[21:47] <sil2100> But here it takes around 1 hour
[21:48] <bobweaver> sil2100,  just for unity ?
[21:49] <sil2100> Yes o_O
[21:49] <sil2100> It's REALLY slow here
[21:51] <bobweaver> huh yeah maybe 30 min it was not sure but it wwas def not hour
[21:52] <sil2100> What storage did you use?
[21:53] <bobweaver> just a SDHC card I think was 20 or 30 gigs
[21:53] <bobweaver> Is yourrs EC ?
[21:53] <bobweaver> ES*
[21:56] <sil2100> bobweaver: no, it's the pre-ES version
[21:56] <bobweaver> also you have put make shift heatsink and leogos case with fan ?
[21:57] <bobweaver> I used coper and heatsink from loacal place (had to cut it up )
[21:57] <sil2100> hm, negative as well
[21:57] <sil2100> Is that a known issue?
[21:57] <bobweaver> I wasent going to chance it
[21:57]  * bobweaver is crazy and thinks all cpus should have heat sink 
[21:57] <bobweaver> gpu anything that gets hot
[21:58] <bobweaver> legos case was fun to build
[21:58] <bobweaver> 9volt batt for fan
[21:59] <bobweaver> I need to get one for the Ubuntu TV project but $$ is low at this time. But my friend is happy with his. But it is still  not super fast due to only gig of ram
[22:00] <bobweaver> sil2100,  I will try to grab some pics of it and send to you
[22:00] <sil2100> bobweaver: thanks!
[22:00] <bobweaver> next time I am over at house (lives hour from me )
[22:02] <bobweaver> sil2100,  I would like to set up a fund for Ubuntu TV to get us some more panda boards to hack on like 2 or three one for me one for thomas and one for whoever else happens to be in line of fire. But I am unsure as to how to go about that
[22:31] <bregma> bobweaver, an ARM shouldn't need a heatsink
[22:32] <bregma> I used run a snapdragon doing compiles and rending 1080p video and it was putting out about 0.25 watts
[22:32] <bregma> not hot enough to feel warm
[22:33] <bobweaver> Oo
[22:33] <bobweaver> Like I said I was not going to chance it
[22:33] <bobweaver> that is it Just trying to think of different things that I may have done that sil2100 is not doing TBH